I’ve recently added a Teletype to my 6u case and am loving it. Can’t wait to get a chance to take it out live! As others have mentioned it is ergonomically best suited to a skiff case laid flat because that makes it easier to see the screen without cables getting in the way. However, I have a deeper case with inbuilt power supply that really needs to be positioned vertically and I’m finding it a bit frustrating always peering through the cables to see the screen or rigging up cable ties etc.
It struck me suddenly that there’s an easy fix! I can mount the teletype upside down in the case, put it on the top row, and the screen would be free of all the cables (except the usb cable, which can snake round the back of the case). Only problem is that the text on the screen would be upside down!
So… I’m wondering how hard it would be to mod the firmware so the screen is rendered the other way up? Impossible? Easy? Somewhere inbetween? I think @scanner_darkly has a vertical case too…
That’s exciting! It has been many years since I did any C coding but I suspect the bigger hurdle will be putting together the toolchain for compiling it (and learning how to use git!)
But I really do think it would make a big difference for readability in vertical systems, so probably worthwhile. (Luckily the text on the monome modules is beautifully discrete so wouldn’t look too peculiar upside down!)
Would be nice if it also rearranged the I/O order too, so it’s still left to right.
On a related note, I always find myself thinking the inputs are 1234 top row, 5678 second row instead of 1357, 2468. Now I’m wondering about rearranging them in the firmware so they match my expectations
I like this idea a lot. I know I for one would do this if it found it’s way into the firmware. Cables are always in front of the screen in my 6u case. Not sure I’d want to hack/maintain a firmware version for myself though.
perhaps this could be an op and/or a key shortcut, so it wouldn’t require having a separate firmware version? seems like it might be useful enough to be considered for inclusion in the official firmware.
it’s possible but this is a pretty special case, so a custom firmware mod is the way to go… but it does make sense to also change how inputs/outputs are arranged for the upside down version.
Thanks for the encouragement! A button combo that flipped the screen would be lovely, although I expect that would be beyond my coding skills…
I’ll try and figure out how to get set up for compiling firmware on my mac and see if I can hack together a version with the screen flipped to get an idea how it feels in the rack that way up. Unless someone else wants to have a go of course!
Then I’ll take a couple of photos to give everyone a sense of whether it’s worthwhile or not.
I’d worry about someone triggering this by accident if it was a keyboard combo… (even worse if it happened during a performance!)
Maybe we can use a #define to build a firmware with a flipped screen (and jacks). It wouldn’t be that hard to fiddle the build scripts to spit out both firmwares.
The Eurorack has a sheet over it at the moment due to the baby (joyfully) eating lots of time. Experience with my first child taught me that it’s better to temporarily reducing the range of your hobbies than not have enough time for all of them.
this is a good point and i think a good enough reason to not add a keyboard combo.
i’m super reluctant to introduce something that would result in having 2 separate versions… would just make things that more confusing (and people buying a module second hand with reverted version installed etc). a dedicated op seems like a safe enough option and something that would allow you to switch things live easily.
yeah, executing the op would save the updated setting to flash.
put it under voltage control!
@tehn said he is okay with adding it to the official firmware, i should have something to test next week. for the op what should the name be? would we ever have any other screen related ops? if not something like REVERT maybe? or leaving the possibility to have more screen ops in the future, SCREEN.REV?
I would avoid ‘SCREEN.REV’ since it seems like it would mean reverse, and I’d expect that to change the screen colours to black on orange. I’d go with ‘SCREEN.ROT’ instead, or ‘SCREEN.FLIP’. I could imagine other screen ops in the future, for sure (e.g. screensaver timeout, cursor highlight etc.).
Actually, on further thought… maybe “DEVICE” might be a better prefix than “SCREEN”? That was it leaves open options for further changes to basic functionality, such as reordering inputs etc? Just a thought…