@laborcamp excellent. i’ve got the trinity, but was resisting the tt, but you’ve just tipped me over the edge.

1 Like

That sounded really cool in proper headphones, especially loved the first one.
Awesome!

1 Like

@polyoptics @laborcamp excellent stuff yall!

1 Like

I have not yet connected my trilogy to TT, and I think I will wait a couple more days before doing it.
I am enjoying the process of just focusing on what I can squeeze out of teletype alone. And the idea of working with just one other module, or very limited setup. In fact I think I might try to trim things down even further before deliving into the full on integration with trilogy.

AND
It is all super exciting. Mainly because it feels like opening up a different paradigm for handling the system.

Also super cool to see new videos and sounds coming up with teletype explorations!

Are all variables shared by all scripts (and live code) in a given scene? I thought so, from the evidence of earlier posts, but the scope of I in

L 1 4 : CV I 0

must (?) be local to the loop only. Ah, no it isn’t: I see that "I gets overwritten by the L (loop) PRE, but can be used as general purpose otherwise." In a case where X is used as a temp variable, as in

X RRAND 1 4
CV X 0

can other scripts change X?

1 Like

yes, variables can be set/altered from various scripts.
which is great

Thanks! Got it. I think I was having a little cognitive dissonance: I’m learning Scala, which is object-oriented (objects can have private state) and functional (where the idiom is to prefer immutable values to mutable variables, though this isn’t enforced in Scala). I love how different different kinds of “programming” can be.

i have just sent some money to Sweden. He said he would send me a Teletype as present.

random q

is there anything i should not plug into walk?

Walk is definitely not designed to accept triggers into the footswitch inputs (with adaptor cables). The circuit expects to be floating, then periodically grounded, so attaching CV from a module (or audio from another source) will likely just stay in the ‘HIGH’ state, and not respond to input. I don’t believe it will damage the unit, but don’t tempt fate as it won’t do anything.

The outputs should be able to plugged into anything in your system. The drivers struggle a touch with low impedance inputs (eg. some passive LPGs) but won’t be damaged by it.

1 Like

even a burst of voltage would be bad?

was gonna try it this weekend but didnt want to needlessly fry anything

… I just looked at the schematic and you know it’s probably fine. The response will likely be the opposite of what you expect though (in order to accommodate the normally-closed switch). A positive voltage will set the output low, while a zero (or negative) will set the out high.

I think…

Let me check this when I’m home tonight so you don’t blow up your new module unnecessarily.

awesome

i just got a second unit so it would be rad to split duties between my feet and gates

or perhaps
strangeloops w/ teletype outs plugged into walk ins

the same recursive patching can be done with code but i’m still keen to try that for some reason

I really like the idea of 4 foot pedals! Currently using Walk with 2 pedals plus one into the Aleph… Need to grab one more pedal and return to my guitar days…

All of the logic functions in Walk are super dumb and easily achievable within Teletype with a line or two. That being said, simply having the 6 outs of Walk available simultaneously opens up some really interesting possibilities.

1 Like

nice idea

the other day i was jokingly trying to wrap my head around whether teletype is an aleph expander or the other way around

once i get more time with TT i’ll def pair the beasts

I definitely see them entirely separately. At present all Aleph is used for is a fancy looping / dubbing / sos recorder for the modular. The only CV going on is a simple clock going from Aleph CV back to WW / MP / TT for rhythm generation in sync with the aleph’s looping.

I toyed with the idea of porting TT to the Aleph, but it didn’t really seem to make sense without a really deep synthesis engine to control on the DSP. Maybe in another lifetime I’d go there…

2 Likes

This is pretty much the same boat I’m in currently. aleph for looping/dsp w/trigger sync and TT for sequencing duties. A lot of the ‘sequencing’ ideas I was clumsily trying to do with the aleph (on top of the dsp) are so much more streamlined with the TT.

1 Like

PS I gigged with the Teletype last night and it was super smooth, no hiccups :sunglasses:

2 Likes

is the teletype designed to work only with specific keyboards (or only the one it ships with)? I tried plugging in a happy hacking last night, but the teletype didn’t recognize it.

@tehn could answer for sure but looking at the happy hacking keyboard I suspect the problem is that it is really a keyboard + usb hub (or said differently it is likely presenting itself as a usb hub that happens to have a keyboard attached). The aleph has a similar limitation in that its usb host driver doesn’t (yet) know how to handle multiple devices on a single usb bus.

1 Like