Hi!
Recently I’ve bought a Teletype module. It hasn’t arrived yet but I’m thinking in selling my Marbles module because I think it can do what Marbles does. Am I right? Or do you think that both modules could complement each other well and they aren’t redundant in a single and tiny system? Examples?
Cheers!

I think Marbles and Teletype complement each other nicely. I often have Marbles’ clock driving Teletype scripts, or Teletype driving Marbles with rhythmic patterns. I also sometimes will sample Marbles with Teletype for shift-register stuff, or sample Teletype CVs with Marbles :slight_smile:

3 Likes

Nice! I’m going to wait until I have both modules before taking a decision. Any other examples? Songs/patches with both modules?

I thought the same thing as you back when I bought a Teletype, and funded the cost of the Teletype in part by selling my μMarbles. I ended up buying a μMarbles again a couple months later. While you could technically design a patch that does similar-ish things to Marbles with controllable random trig and CV outputs, you probably wouldn’t be able to use your Teletype for anything else other than being a Marbles clone, and it’s capable of WAY more interesting applications than that. It also likely wouldn’t be as hands-on, flexible, and immediately musical as Marbles is right out of the box. The two modules also pair together very nicely. It’s very natural to use Marbles’ outs as trigger ins to fire off Teletype scripts, and clocking Teletype with Marbles is often more flexible and immediate than using Teletype’s internal metronome for everything. Both modules have the potential to be the modulation ‘brain’ of your setup, but the two of them together are like chocolate and peanut butter.

2 Likes

I like chocolate and peanut butter, yeah

2 Likes

I agree with everything said above (BOTH, not either!) but still feel driven to answer your initial question.

The answer is here. However, it does require a TXI as written here (which I recommend getting anyway!), but you could substitute a 16n for the TXI, or just modify values with the keyboard (store them in a pattern and use [ and ] to increment them quickly).

The big omission in this script, IIRC, is the red mode, but if you look to my posts toward the end of the thread (and get real cozy using TT!), you’d be able to hack together something that emulates that functionality (in fact, it’s a much simpler thing to do than the above-linked script – basically just moving start points and active patterns around in the tracker).

That thread is a gold mine, generally. There are some issues with things requiring additional hardware OR being written in older syntax (which should, I think, still work, but is not always the most efficient // can cause weirdness like if you reference TR A but have the variable A assigned to a value). I’ve found most of my TT questions are answered there, and would advise thumbing through it once you’ve completed the studies // starting any quest that doesn’t seem covered in studies / manual there.

TT is probably the most underrated module in euro. I recall someone in my (quite large, globally recognized) electronic scene mentioning that I was the only person in our area using one, and have since seen quite a few gathering dust at friends’ houses because, frankly, it’s not an easy module to learn when you’re stoned. Stick with it and you will save SO MUCH time and money in the long run.

Shit, just today I learned you can control the Ansible LFO app without an Arc using TT, and I’m two years in… really just never stops unfolding (also: I still don’t get bitwise ops, and am sure it’ll blow my mind when I get to it in a few months).

5 Likes

Woah, so much information to digest! I think I have to keep both modules…

2 Likes

My script is 2,5 years old and at that time I didn’t really understood all the module features. I think that there must be a better way to mimic the basics (thanks to all the wonderful updates), but marbles willl still remain the best marble if you intend to do marble stuff :slightly_smiling_face:

2 Likes

Great reminder! I wish there was a bot that automatically posted this sort of thing on any thread linking to a post about TT.

“This post is X years old, relevant as of firmware Y, please see manual. May still serve as a good starting point for executing whatever concept it was cited in relation to. YMMV.”

2 Likes

I think the developers have been pretty careful about breaking changes. There may have been a couple over the years. Other than assuming A,B,C,D are 1,2,3,4 (which was more of a convention than an actual change) I couldn’t even say what they are. I think breaking changes to ops are very few.

yeah, there weren’t too many breaking changes. you can always check the changelog to find them or to check when certain features were introduced: https://monome.org/docs/teletype/manual/#changelog

starting with 2.0:

  • BREAKING: remove II op. Ops that required it will now work with out it. (e.g. II MP.PRESET 1 will become just MP.PRESET 1)
  • BREAKING: merge the MUTE and UNMUTE ops. Now MUTE x will return the mute status for trigger x (0 is unmuted, 1 is muted), and MUTE x y will set the mute for trigger x (y = 0 to unmute, y = 1 to mute)
  • BREAKING: remove unused Meadowphysics ops: MP.SYNC, MP.MUTE, MP.UNMUTE, MP.FREEZE, MP.UNFREEZE
  • BREAKING: rename Ansible Meadowphysics ops to start with ME

starting with 2.1:

  • BREAKING: the I variable is now scoped to the L loop, and does not exist outside of an execution context. Scripts using I as a general-purpose variable will be broken.

this doesn’t include any breaking changes done to ops while they were still being developed but people are usually good at mentioning using anything that is still beta.

2 Likes

Got a question about the state of Q when a script is triggered - given a script such as

Q.N 4
Q IN
L 1 4: CV I N Q; TR.P I

On line 3 should I expect Q to output a new element from the queue for each iteration of the loop? Finding that I’m only getting one value for the 4 items in the loop. I’ve confirmed that with the following script:

Q.N 4
Q IN
L 0 3: P I Q

Feel like I’m missing something here, what could be a way to access multiple items programmatically from a Q within a script?

Hey people,
i would like to make a question about Teletype which is very naive and very precise at the same time and please consider that i don’t have a TT already and i don’t have any kind of real knowledge about it… so the question is:

“Would be easy/possible to write a script which let me create, let’s say, a 16 steps random trigger/cv sequence pattern, that wont never plays on certain steps, not in terms of values, but in terms of figure/position compared to the pattern structure”? (for instance, a random playing structure that’ll never plays/sounds on step 5 and 13 of the pattern)

I have always wanted to create this kind of scenario on a classic trigger/cv sequencer in random mode, but it was always impossible to do, although in some cases i made a pseudo trigger sequence using gate probability duties and deactivating the steps i don’t to play of course, but this is a case where are present only trigger/gate messages and not cv’s and it’s not the same thing.

I would like to know even if it’s “correct” to think about TT possibilities in this terms?
Thanks!

yes, it would be trivial to do with teletype. you could use a pattern bank to indicate which steps should be muted and then use a simple condition check before you generate a random gate/trigger.

2 Likes

The basic idea is to have a random pattern/structure where I can decide “when” not to play… something random that became linear when I want … :thinking::sweat_smile:

I don’t think there is a sequencer where you can decide basically the play mode x step?
Maybe the Vector Five12 has something like that idk… so I was asking myself if with TT this would be possible…

You’ve set the queue length to 4, but you are only pushing one value into the queue. Have you tried doing this in a loop?

L 1 4: Q IN

I can’t remember how often IN is sampled. It’s possible that loop could run faster than it is sampled. If so you might have to add some delay to get 4 unique values.

Yes this is totally possible with the teletype.

What’s more important (to me) would be the extreme flexibility you’ll have over when and which steps play and which doesn’t. Any combination of probability, input (physical or cv), interaction with what else is going on in the other scripts on the teletype, and any combination of the above you can dream up.

1 Like

Happy to hear this from you, I know what kind of rhythmical structures you accomplish with TT and your modular in general.
I’m satisfied with my sequencers right know, but I want something different in terms of interaction, language and possibilities.
I’m not already in possession of a TT, so I’m asking myself if it would be a nice choice for these type of things. Due to the nature of the module It seems so, but I wanted to be more precise with this question.
Thanks

1 Like

Is there a way to poll for a value while M.Act 0?

The use case I’m to solve is how to poll the values of 16n while being able use the metro for other things, like responding to manually triggered buttons on a grid.

The scripts will run with a corresponding trigger, unless you explicitly muted them…