i have a complicated technical+design reason. it’s not impossible to have both (trent and i discussed this already) but it’d be inelegant.

Q is global. you can pop a command on the Q from anywhere (including live mode).

Q.POP will execute the most recent. Q.ALL will do them all, Q.CLR will clear them. if you want to see how many commands are there, read Q.L

i can imagine some fun trigger-frenzy Q manipulation for interesting results.

Thinking out loud: clearly with the 8 trig inputs this was designed for close use with MP. Does is make sense then to use this solo. Obviously yes… But is the systems full potential/design being wasted…

@tehn : thanks again for the amazing work, but also for the direct feedback and discussion in this thread. It’s great to be directly connected with the maker(s).

I’m sold if it’s possible to save “preset melodies” that are composed and saved before time, then quickly and easily recalled during live performances. I think this is possible, and not just for melodies, but for entire “patches”.

True words, and Teletype seems a very well defined and elegant system, which I hope to really take to. Having spent half a lifetime behind screens and keyboards of one kind or another I’m extremely fussy about what I put in my rack.

Sounds fine, but I think I’ve got the excuse I need to now get myself a complete overkill but badass Das Keyboard :wink:

Idea (v2?) : ability to actually play melodies via the keyboard, i.e. route direct keypresses through to a CV out. Maybe that’s already possible too. Time to reread the docs.

I hope you don’t take it as personal criticism @ether, but I just want to say that I hope the Teletype does not in the end use keyboard as an interface to play notes as (I think) you describe in the end of your post.
This is something that always botherd me in the laptop as musical instrument. And monome already created amazing physical interfaces: grids and arcs, so to revert here and have the computer keyboard be the instrument interface would be a huge step backwards.
Based on that, I would imagine that there is no way that would be the case.
Teletype seems to be about a very different approach to music making…

Would pair really nicely with two pressure points (which I’d guess lots of people have). I think it’d be fun to play with matrices driving the triggers. I don’t have a MP nor do I think I’ll miss much having the teletype without one - it seems deep enough in itself, like a mini-supercollider module.

As for another option, using a rene to drive teletype, would you need to use the cv in to select which trigger - or would you just set up the cv in to choose from different actions set up within one trigger (or could have two for x and y)? If this is possible and instead coordinated with something that has precise control of cv out (say from an expert sleepers out) could you really up the number of different triggerable actions, depending on how much memory the teletype has, by stacking actions within each trigger and selecting the specific action with the cv in value?

I don’t actually have a rene (yet), and I only have one pressure points. I do however have this planar - might be fun to send clocked triggers to the input and use the joystick to select where they go. Using different devices to trigger the first and second group of four input triggers might be fun to explore.

I really like the opportunities for feedback that the teletype creates: by bouncing output triggers through delays or end of cycles (add some matrix action?) back to the triggers in, you could create entire self-generating pieces that start with a single trigger or command input, without ever touching a grid or any other monome module.* this, at first glance to me anyway, makes teletype arguably the most solid contribution to the modular world to date for monome - mad props!

*Of course, I say this to make a point; not capitalizing on the behind the panel connectivity with other monome modules is just crazy talk.

One question @tehn - you addressed an earlier concern about the keyboard’s quality (which I now don’t doubt) but didn’t answer whether a wireless usb dongle keyboard could be substituted (that I saw). Can’t think of why not, I’m sure you put thought into the keyboard you chose, but sure would be nice to not be tethered.

In any case, I’ll start budgeting…

2 Likes

Yes, this seems to be a new way of approaching composition. One where it’s abstraction forces the user discover a new syntax for creation. Instead of relying on traditional metaphors of scales and keys, which are often hard to detach from premapped neural networks, here you are faced with code fragments that can be strung together to form webs of relationships. Compositional haikus whose brevity hides their infinite depth.

2 Likes

[quote=“sphiralstudios, post:86, topic:596”]
…like a mini-supercollider module…I really like the opportunities for feedback that the teletype creates: by bouncing output triggers through delays or end of cycles (add some matrix action?) back to the triggers in, you could create entire self-generating pieces that start with a single trigger or command input, without ever touching a grid or any other monome module.* this, at first glance to me anyway, makes teletype arguably the most solid contribution to the modular world to date for monome - mad props!
[/quote]agreed

i dont have any monome euro yet nor a grid but i’ll probably get this to run with some mannequins, trigger sequencers, and drum machines that accept gates

self patching will also likely be pretty fun

We’re all friends here, so no problem about personal criticism :smile:

I don’t want to derail this thread, but there’s some background to my keyboard idea, something that’s been in the back of my mind for a while. There’s really a striking similarity between a new 128 and a current generation Apple wireless keyboard. Just imagine the Apple keyboard without letters on the keys, and with all the keys adjusted to be the same size. Similarly, then imagine a monome grid that could also be used as a standard keyboard. The Das Keyboard models without letters play in here too.

To me all these three things are the same: a rectangle with buttons that have meaning. It’d be great if I just had the one, that could be used in different contexts, in different ways.

But, I digress…

The coding is pretty neat. I like what I see in the documentation. Of course I have to ask…Is there a way to backup/copy/memory to HD or save the code for later?

Man what about: http://www.artlebedev.com/everything/optimus/popularis/

Have a keyboard that dynamically displays your playable options / macros as they occur (or during the window when they could occur)? That would be sick.

Of course, there’s the price tag.

@sphiralstudios Exactly. I nearly posted that too, but thought I was getting carried away, and taking the focus off the wonder that is Teletype as is. There is something to this whole keyboard thing though…

Concerning ES. I’m having trouble decoding where synching the ES with the TT happens in the code:
“ES_PRESET
ES_RESET
ES_PATTERN
ES_TRANS
ES_STOP
ES_SH1
ES_SH2
ES_SH3
ES_SH4”?

Would there be any plans to integrate the scripting language into the existing teletype max.pat?

(maybe not the CV stuff, but everything else)

I am only asking in that I’d perhaps need a bit of time to get my head round this, and doing some scripting with the max.pat would let me evaluate how useful this module would be to me.

Or more accurately how useful I would be to this module

1 Like

I would guess that ES_TRANS stands for transport through the pattern, although I wondered if that meant just play or play one note. If it’s just begin playback of pattern, I don’t see an actual tempo-synced playback option either, although I haven’t figured out what the ES_SH1-4 are either.

I suppose you could set a trigger to play and then stop, effectively getting a note-per-trigger behavior.

I think SH stands for Shapes.

it was designed with MP in mind, but by no means required. that’s the beauty of modular, of course-- the core idea was to turn triggers into events.

walk was also central to the goal. hands-off complex control of a patch.

Makes sense! Now I’m wishing there was a small enough trigger sequencer that didn’t require I buy a grid - ha!

what’s the “IN” jack for? cv control of the param knob?

yes, whole presets (all scripts for triggers/init/metro) would be recalled, including the pattern bank (4x64).

there’s not a way to do this currently, but the firmware could be extended to do so. it’s not high on my list, because this is exactly what earthsea does best, better than the keyboard would ever do.

absolutely! no other monome modules required. i do, however, hope y’all will consider walk, as having footswitch actions truly elevates the performance potential of the modular.

also-- i’ll write more about this elsewhere-- but i want to stress this is not an audio engine. it’s an event engine. you can make some LFOs, but it’s not a great use of the system. the modular excels at LFOs, oscillators, etc. this module is to control those. teletype ramps values wonderfully, so the control of these other elements can be much more interesting.

i’m not confident this will work straight away. i’d have to get one, and read about the drivers. currently the teletype uses a simple HID keyboard driver. if the wireless/bluetooth/whatever needs something different, it’s not going to work, for now. implementing wireless keyboard support is not on my immediate todo list.

this would be v2 (stretch goal). we need to move the first 100 units beforehand. my plan is to have a read/write procedure with a usb thumb drive.

ES.RESET will hard sync reset the pattern.

i’m considering providing full clock to the ES pattern playback, but that will be a later revision.

ES.SH are remote triggering of triple-shapes. ES.TRANS is transpose.

no, but i’m considering porting the code into a max external, perhaps. i do have a simulator that runs on the command line, but it’s hardly a musical assessment.