all trilogy modules require an update for use with teletype.

i’m working on a clock sync system for ES. it’ll mean issuing a command to ES toggling “external” sync. and then individual clock message will trigger the pattern progression.

2 Likes

Any noticeable noise from that oled? You guys tried it in many different cases?

no noise at all. tested with cell 90 ps, row power 40, new intellijel busboard.

for the OLED, 12V is stepped down to 5v, and then further down to 3v3 with substantial conditioning at every stage. i wouldn’t expect noise even on a low quality power system.

Cool. Presume the doepfer linear supplies will be fine too then.

“ES_CLOCK” :+1:

That’s really, really great! Can’t wait to play with this. I’m already planning to reorganize my modular so that the monome stuff and TT will move to my skiff for some future live set!

Been having fun thinking whether a setup like this would be useful:

Having not played with an MP yet, I wonder if this would be practically useful or if it would defeat the purpose of MP’s cascading nature. Surely with linked rows there’d be some redundancy (and there might be a problem with overlapping ‘simultaneous’ triggers), but I can maybe think of some setups where it could be useful.

Then the thought occurred to me that MP could do this itself using the grid (with an added ‘page’) maybe? Manage which row events generate triggers on which outs, and just the default behavior is a one-to-one mapping.

Yes the thought also occurred to me that you could accomplish similar results downstream on the TT end by manipulating the input triggers (or even just patch cables/mults), but the thought of ‘playing’ TT by switching which rows and corresponding rhythms on MP activate which trigger input (with the added ability to stack them) on the fly using an 8 x 8 section on a grid seems possibly enticing?

Can’t decide if it’d be useful or pointless. Thoughts?

the price / rack space doesn’t justify it imho (speaking only within the context of intended use here, of course you could use it for great many things, especially in a bigger modular setup, and Hinton’s modules are top quality).

but to me the main thing would be - this is much easier done in firmware, and grid is pretty much the perfect controller for this. i would love to see a condensed version of SwitchMix though with only the inputs and outputs and a USB port for a grid, with the ability to store presets and ability to step through or mutate them in many different ways.

for those on the edge of their seats for syntax updates…

Q changed to S (because it really is a stack, for commands.)

added DRUNK variable. changes -1,0,1 from its previous value on each read. set to choose a new wandering location. easily fenced:

WRAP 10 20 DRUNK
LIM 10 20 DRUNK

first will wrap it, lim will just keep it in bounds.

added Q as a queue of numbers (shift register) not of commands. Q.N sets the queue length. Q reads from the output position. write to Q shifts the register forward. Q.AVG gives an average of the length of the queue. set Q.AVG to set the entire queue to the same value.

excellent for smoothing!

micro updates to the docs. tracker is looking super good. will try for a tiny update video on that within a few days.

5 Likes

Just wanted to say that I really love the idea of Teletype. Unapologetically digital, with a very novel interface that will surely break path dependencies, and a nice minimal aesthetic. (Also hello to all the familiar names that I recognize from the world’s best cat forum.)

1 Like

In one more week it’ll be mid-June. So excited… I hope everything is going well, according to plan.

assembled pcbs are here. the build starts today. i have to force myself to stop adding features to the code.

so we’ll be ahead of schedule. expecting retailer shipments by the end of the week.

8 Likes

this thread is so exciting. i am so ignorant regarding the code. i had bigbig fun with mptt on the computer side but in the end i didn’t have a deep enough relationship with it to keep on learning/trying/learning. i cannot wait to see more video and implementations from those smarter/quicker in this realm than myself. very very exciting even if i cannot see through the complexity myself.

3 Likes

Super exited but can you tell us if this baby will land anywhere in EU??? ( and where in order to contact them ) :heart_eyes:

Email Ulf at escapefromnoise.com :smile:

1 Like

I see that scenes have been added to the docs and I’m trying to understand the limits of the nested structure…I’m sure some of this will be revealed as the docs are fleshed out and units make their way into the wild but, how many commands can fit in a script? or scripts and patterns per scene?

From what I understand, there are four banks of 64 steps (which makes sense, if, like in a classic configuration, you want to have pitch info send to each output, but you don’t have to use them for pitch, you can use the data for many other things). There are 8 inputs, so you should be able to have at least 8 scripts, one per input, per scene. There is also an INIT script that runs as Teletype is powered up. They also mentioned that the screen can hold up to 6 commands or lines per script, no scrolling, so you cannot write long scripts, but that you can do a lot in one line, make it as dense as you like (though I assume certain operations wouldn’t work as expected when entered at the same time). Of course, they are the ones that really know, so they should be able to confirm or correct me. For now, I just don’t want you to distract them. They might be working on my order, to get it ready to sent it to me… :wink:

1 Like

lol yes, I will leave them to soldering

interesting concept to (mis)use the CV outs for other purposes…I have been mulling that idea but will wait till I have one to test it out

Yes, we’re building as fast as we can and working on the scenes that will ship with the device.

Each scene contains:

  • 8 input trigger scripts (linked to the input panel jacks)
  • 1 init script, called when a new scene is loaded
  • 1 metro script, called at each metro interval
    – nb: each script contains up to 6 commands (lines). lines are limited only by screen width
  • 4 patterns
    – each with 64 steps which can store any value
    – each has individual start & end range markers and current P.HERE value (where the playhead is)
  • the scene page has a text editor for documenting the purpose and usage of the scene.

There’s certainly no predetermined use for the CV outs, and while they are great at melody generation, you can do plenty of other interesting modulation too. I note that slew times can be up to 32 seconds for super long slopes.

7 Likes

So i’m asking myself is it possible to set random voltage within a certain number of selected ones ( in order to play random scaled notes?? )

yes, quite simply.

make your chosen scale notes in a pattern (with the tracker or manually). then:

P RAND P.L

P.L is the length of your pattern, so this command will return a random note within that scale. you can assign this to a CV:

CV 1 P RAND P.L
1 Like