Ah, thanks Joe, I haven’t watched all your TT videos, but remember now that grid seems to be center stage, thanks for the reminder, I’ll watch them front to back, I’m sure it will answer a lot of questions!
And, yeah, you’re spot on, I’m indeed looking to create “custom control surface for your Teletype scripts”. Have you encountered anything either awkward or even impossible in this regard?
Nothing comes to mind, really. The grid ops are smartly designed to do a lot with compact code. Like @SimonKirby mentioned, it probably encourages you to push the lines/scripts limit even more than you would already, so you might find you spend even more time trying to optimize scripts to eliminate a line or script. Personally I find that kind of fun and challenging.
I mean, there are limits of course, but I don’t think there’s anything that’s going to be a big surprise someone like you who already has extensive Teletype experience.
The 2>1 feels like essential gear if you’re going to be developing sophisticated grid ops scripts. The grid emulator is definitely helpful but I find I like to test on the hardware as I go pretty often.
The grid control mode Simon mentioned- it’s not that OR your custom controller. You can use them together, so that helps get more mileage out of it all.
the older revision of teletype (green PCB) might also be able to provide sufficient power as long as you don’t have too many LEDs on at the same time. and even if you do exceed what teletype can provide, it will just shut down, no damage to the module, you can just power cycle.
the 2nd aspect is making sure you have enough power in your eurorack case - you have to do this regardless of which version of teletype you use (or if you use 2 > 1 and power it from your euro power).
you need to have a 2 device to 1 host switch which are less common.
it’s also super simple to make a script that would let you use grid to control a variable. for instance:
G.FDR 0 0 0 16 1 0 4 1
this script will create a single row fader. as you can see, with grid scripts the difficult part is defining buttons and faders, but there are multiple ops that simplify using them after that - a script gets called when a grid button is pressed or a fader value changed, you do something in the script or read the fader value etc etc.
well, let’s count: for other units we have whitewhale, earthsea, meadowphysics, kria, orca, orca’s heart, polyearthsea, chrono sage, levels, cycles. for teletype we have: https://github.com/scanner-darkly/teletype/wiki/CODE-EXCHANGE - i didn’t count, but there are many great scripts there. granted, they might be not as complex as kria - but that’s why kria is a dedicated firmware. and the strength of using teletype scripts to create your own grid apps is that you don’t need to install a separate toolchain, you get all the other things teletype supports, you can have 32 different apps etc etc.
this is related to the question of complexity of creating a grid teletype script - i would say they are less suitable for experimentation (creating a script from scratch) and more fit for creating something you won’t change often, like your own custom controller. many scripts in the code exchange page i linked can be used as is (and i need to find the time to create a pack of best grid teletype scripts with proper descriptions etc - and the time to review/add more studies).
I’d be a bit cautious about usb switches. I’ve had a bit of a challenging time with them. You definitely need to ensure that they pass the power along properly. Also, I have struggled a bit in the past with electrical noise from the grid getting into the signal chain somehow (you can tell this is happening because it’s dependent on the number and brightness of lights showing.) There are ways round this if it affects you, but they are fiddly. Fwiw, I’ve not had any such problems using the grid with ansible, but I think it varies a lot with the specifics of your rack.
you’ll have to set O.MIN and O.MAX if you want to be able to store outside of 0-63 range (the default values for min and max), it’ll clamp to either side (depending on O.WRAP setting). which could be a useful side effect too.
One of my 2021 goals is to get a firm handle on Teletype. I am through study 4, but am already seeing how some accountability is going to be needed in order for me to reach a few specific goals that I have in mind.
Question for the group: would a “learning teletype” discord or PM thread be weird? As in, would that essentially just duplicate this thread unnecessarily? I ask because I feel like it would be cool to go deep with a small group of people. Am balancing the pros/cons of the closed nature of discord. I’d hate to clutter things here with updates like “hey I completed study #6, how are you guys and gals doing this week?”.
I know there have been a few norns studies discords, so I guess I just wanted to take the group’s pulse on a similar setup for teletype.
@Whatwetalkabout@ilikeorangethecolour would you lean toward discord or just a group PM here on lines? I actually don’t mind the idea of a PM, since the group would be small and time-bound (i.e., the study group might last six months or whatever). I’m not a huge discord user; are there benefits to that platform for our uses?
I’m a bit post-studies, but I’d suggest you guys just post any questions here in this thread, we’re all friendly and even seasoned teletypers might learn something
If it has any interest, I put pretty much all the tracks I made with the teletype up on github (in the hope it helps someone), complete with scenes, patch notes and direct links to a youtube video of a live performance of each track. It might be a bit overwhelming, but maybe pick a track that sounds interesting (if possible), look at the code and feel free to ask any questions here, I’d be more than happy to answer anything. Obviously if you don’t find anything interesting, feel free to completely ignore!
Link is further up the thread, but I hope it’s OK to repost it here for convenience