Monome Teletype and Walk

[tehn]

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).

this is correct. any keyboard will work, given it doesn’t have a hub built in.

some day we may get around to adding hub support, but it’s a large task and we’re already onto the next thing.

[tambouri]

This got posted last night, doesn’t look like it’s extensively teletype, still cool seeing it make a cameo.

from the control voltage instagram

@controlvoltage

[laborcamp]

A slightly more expansive arrangement with monome teletype at the center. Teletype is driven by meadowphysics triggers, further breaking up patterns, and controlling pitch variations derived form a single, internal sequence. Additional PO-12 drums are driven by teletype, and processed through CV-controlled Audio Damage Grainshift.

[glia]

this module is so weird
(i’m in love with it tho)

today my neice was cracking up when she noticed the keyboard attached to my skiff

also tt (or any trigger) into walk fed back into teletype works…tested it out this morning

[ether]

@laborcamp classy stuff again.

[kisielk]

After seeing one in person I am seriously considering picking one of these up. All racks are full so I’ll probably have to cut some lesser modules…

[glia]

another question for @tehn or @Galapagoose

yesterday i tried to setup one pedal as a momentary mute for a teletype trigger
it worked as a mute but was merely toggling rather than momentary

any hints how to tell teletype “only do x if gate is high…”? does tt accept gates or triggers?

rechecking the docs but i dont recall if something like that has been covered already

[Galapagoose]

If you need to know the state of a trigger, you’ll have to use the IN jack.

You could use a variable to store the state of the pedal:

X GT IN 100

Above, this checks if the IN jack’s value is greater than ‘100’ (as a threshold).

Then you would use a PRE to check if X is high like so:

IF X : //your conditional command//

You could add the above into 1 line, but then your command would have to be pretty short:

IF GT X 100 : //your short command//

Then just use an ELSE command afterward if you want to do something different when pedal isn’t depressed:

ELSE : //alternate command//

[glia]

excellent
thanks

this reminds me…I was going to ask about use of two PREs
looks like i’ll just need to experiment combining some as a test

[laborcamp]

I don’t think you can have two PREs in a single command. If that is what you are thinking.

[glia]

I thought not
thanks for confirmation

[Galapagoose]

If you use the above you could use the same IF twice, or do 2 IF/ELSE pairs in series. eg:

X GT IN 100 IF X : //when true// ELSE : //when false// IF X : //also when true// ELSE : //also when false//

or:

X GT IN 100 IF X : //when true// IF X : //also when true// ELSE : //not false//

This is the benefit of using the variable up top, as you can just keep checking each line against the same pre-calculated value.

[chrisharrisx]

I’ve just spent my first couple of hours with the Teletype and it’s fantastic. It’s really opened up a huge number of possibilities in my little system.

I have a question about the preloaded scenes though – I managed to accidentally overwrite the Meadowphysics scene and I’m wondering if a) it’s possible to restore or b) if the scripts and description are around somewhere so that I could reconstruct it.

[laborcamp]

PMd you the screen shots.
But you can also re-install the firmware, and it will rebuild the factory scenes. (of course you would then lose whatever you saved on your own…)

[chrisharrisx]

Problem solved courtesy of @laborcamp. Thanks! Off to read the docs again, with care this time

[Gilles_READYdot]

Got mine yesterday. Totally blown away by the screen, so old school and yet modern, might be a hipster thing. Only issue I had was one of the keys had fallen off the keyboard, but easily pushed in, and works as advertized.

Now I really am positive about getting into the TT, I have some prior coding knowledge through Processing, but my brain often struggles (blame it on my drug filled youth) with some of the more abstract aka mathematical aspects of coding. So I’d love to see or read some examples, look at some tutorials to force my brain into the “deeper” aspects that are possible.

[laborcamp]

Here is a little reference chart that might help some with N values for TRACKER mode or just general PATTERN wrangling:

TT_N_values.pdf (955.5 KB)

[glia]

Thanks!

So the tracker only works for CV 1-4?

[laborcamp]

Not necessarily.
You can for example use it to save a sequence of triggers as well, by punching in 1s and 0s in one of your patterns.
You can use a pattern to make a sequence of notes (hence the little chart I posted) or store specific CV values that you can use as modulators or envelopes or whatever.
Tracker just gives you a visual display of 4 patterns of potentially 64 steps each. How you use them is totally up to you.

[glia]

i’ll give it another shot based on that info

last time I tried linking a trigger to a pattern it didn’t work as planned and I tried another rhythm trick since I in the middle of recording