Teletype workflow, basics, and questions

desolationjones · 2018-05-16T17:17:08.118Z

Unfortunately slewing values within a script isn’t possible directly. The TT CV outputs can have slew applied to them. Hypothetically to make use of that slew for a variable you’d have to dedicate a hardware channel to the task and read the value of that channel very quickly as it skews.

Vessel · 2018-05-16T19:04:08.905Z

Thanks, I kind of guessed that might be the case. Not a problem though, modulated VCAs do the job!

josker · 2018-05-25T09:08:14.232Z

Hi!

It’s very much early days with my brand new Teletype, but I’ve run across something that I’m wondering about:

I’d like to do something like

(EDIT: forgot the DIV)

PROB 57: DEL DIV LAST 1 2: TR.PULSE 1

I think multiple PRE-operators(?) can’t be chained in one command… Any ideas on how to do something like this?

GoneCaving · 2018-05-25T09:37:11.745Z

> teletype : code exchange

I think multiple PRE-operators(?) can’t be chained in one command… Any ideas on how to do something like this?

Correct. Only one PRE allowed per line. Perhaps move the DEL into it’s own script, and call the script?

jonsimon · 2018-05-25T09:48:48.910Z

god i hope to be as smart as you guys are with this someday.

josker · 2018-05-25T09:55:08.866Z

> teletype : code exchange

god i hope to be as smart as you guys are with this someday.

I’m very much just starting out, and I’d love to get a good beginner Teletype discussion going! Getting the syntax down is one thing, but I think the real issue is being able to dream up all the possibilities these building blocks allow…

josker · 2018-05-25T09:59:56.836Z

> teletype : code exchange

Correct. Only one PRE allowed per line. Perhaps move the DEL into it’s own script, and call the script?

Oh, very clever! So something like:

Script 1:
PROB 57: SCRIPT 2

Script 2:
DEL DIV LAST 1 2: TR.PULSE 1

GoneCaving · 2018-05-25T10:00:52.768Z

Yes, exactly that. For 20 chars of scripting fun.

Starthief · 2018-05-25T11:33:04.018Z

> teletype : code exchange

PROB 57: DEL DIV LAST 1 2: TR.PULSE 1

TR.P 0 safely does nothing, which you can use to your advantage here. Sadly the line would be too long to fit, so you need to break it up:

Q LT RAND 100 57
DEL DIV LAST 1 2: TR.P Q

If you used a normal variable instead of the queue, any other script changing it during the delay can cause the wrong channel to trigger. Of course if any other script messes with the queue this will break too.

If you wanted 50% rather than 57%, you could use:

DEL DIV LAST 1 2: TR.P TOSS

Another two-line solution:

PROB 43: BREAK
DEL DIV LAST 1 2: TR.P 1

rikrak · 2018-05-25T13:16:37.000Z

> teletype : code exchange

I’m very much just starting out, and I’d love to get a good beginner Teletype discussion going!

Have a look over here, @josker
https://llllllll.co/t/teletype-workflow-for-dummies

(Edit: Posts were moved to this thread. Thanks Mod)

josker · 2018-05-25T14:28:20.004Z

Thanks Mr. Mod.

And Thanks @rikrak and @Starthief – I guess my evening just got booked solid, looking at Starthief’s examples and reading through this thread! I’m just loving the TT so far, and I have zero coding background.

Hlp · 2018-06-08T15:45:04.258Z

I am so damn tempted…especially now with Just Friends in my not yet fully finished 56hp.

I start to be less scared of the coding part reading around here but i would like to get a few questions out of my head.

-for any midi use, one would need Ansible or any midi to cv/gate/trigger module? I ask because it seems Grid is plugged directly into TT too and not sure if TT actually understands midi?

-a while ago i asked on MW about sth that would be able to „house“ a bunch of allflesh pads to act as cv source (1v/oct) and TT was actually recomended for this. So are the inconsistent triggers of the allflesh enough to work reliably with TT and would it be a simple matter of having a scene that for example corresponds to notal 1v/oct output of 8 triggers?

-is it possible to create envelopes between the trigger ins and the Cv outs?
I think so, but wanted to make sure…

-is it common, possible and practical to create lets say 10 scenes for different applications/patches and leave coding out for a while and simply switch scene on the module to the present use case and jam out?

-is just Type the next step of complicated or more a matter of (i think copy paste/load wont work?) typing in available code, maybe adjusting and saving to a scene to be set and availbale anywhere without further need of code?

-what exactly are the onboard functions when away from keyboard. Does the Parameter only change scene or has multiple functions?

So damn tempted

Justmat · 2018-06-08T16:17:30.746Z

One at a time

The grid is not a midi device. TT doesn’t support midi.
Not sure i understand the question, but yes you can trigger stuff with allflesh. What happens when you trigger a script will depend on whats in the script.
Envelopes aren’t really TTs strong point, but you can slew cv values. The TXo expander has more envelope capabilities.
Yes
Just type is no more complicated than general TT scripting.
Outside of selecting a scene, the onboard functions/Param knob do only what is defined in the current scene.

I am sure that you have, but have you checked out the TT studies? They give some great insight into what the TT is capable of.

EqualTemperament · 2018-06-08T16:50:27.014Z

Hlp:

what exactly are the onboard functions when away from keyboard. Does the Parameter only change scene or has multiple functions?

As a newer Teletype owner, I can offer you a perspective here. I was pretty concerned about introducing a QWERTY keyboard into my modular workflow, and kind of wondered the same thing. As it turns out, so far, I leave the keyboard connected just about always. It’s actually a great deal of fun and feels more like it belongs there than I ever thought possible. YMMV of course but for me the whole “QWERTY keyboard” issue was purely contrived in my own mind.

You don’t have to always be “coding” with it. You can use it to change values in one of the patterns, for example, or setting a pattern’s end point, and it really doesn’t feel that much different than wiggling a knob, to me.

Hlp · 2018-06-08T16:50:38.598Z

Is copying codes (and adjust) a recomended way one could learn the module?

Hlp · 2018-06-08T16:53:05.839Z

Oh well… that belongs still to the coding category for me haha. But thanks for the insight!

So when the keyboard is of. All parameters wont be editable in any way right?

Too bad to hear about the envelope limitations. That d make a big difference for me.

One thing i dont get, if the ins are all trigger based. How would one actually connect pitch cv and in case of just type even poly? Or do the ins accept any kind of cv?

dani_derks · 2018-06-08T16:54:07.927Z

Hlp:

Is copying codes (and adjust) a recomended way one could learn the module?

for sure!

I’d say spending time with the Teletype Studies and Just Type Studies will also help get you started. By supplying small chunks of code explanations and a final scene with a musical example, this helps frame the code as cause → effect. Once you get started, making small modifications to these final scenes is a really nice way to personalize your interaction with the code.

Olivier · 2018-06-08T17:09:09.653Z

Hlp:

One thing i dont get, if the ins are all trigger based. How would one actually connect pitch cv and in case of just type even poly? Or do the ins accept any kind of cv?

I’m not sure I fully understand the question, but as a relatively new TT user, I’ll see if I can clarify

Think of the trigger INs as simply ways to activate your scripts. If you’ve coded a few musical events or parameters in SCRIPT 1 (e.g. the speed of the internal metronome, the value of a CV out), sending a trigger to input 1 will cause those events/parameters to occur.

Remember that, in the case of Just Friends + TT, the two modules are connected via i2c on the rear. As such, no physical connection is needed to send say note or trigger information to Just Friends.

For example:

SCRIPT 1
JF.VOX 1 N 6 V 9

Each time I send a trigger to input 1 (linked to SCRIPT 1), the first channel of Just Friends will be activated, playing note 6 at a velocity level of 9.

+1 to @dani_derks recommendation of checking out the studies though - I’ve just scratched the surface above!

xeric · 2018-06-08T17:09:55.962Z

Hlp:

One thing i dont get, if the ins are all trigger based. How would one actually connect pitch cv and in case of just type even poly? Or do the ins accept any kind of cv?

There is a single CV input that can be read by your scripts, and 8 trigger ins that will trigger the corresponding scripts. The TXi expander will give you an additional 4 inputs and 4 param knobs, if you can get a hand on one:

EqualTemperament:

Does the Parameter only change scene or has multiple functions?

You can use the current Param knob values in your scripts, it is only used for navigation if you want to change between ‘scenes’ (saved collections of scripts).

I’ll also point out there’s a lot you can do on Teletype without the keyboard connected, depending on how you build your scenes. I generally don’t have the keyboard connected, but just make use of my existing scenes.

Also, with regards to all-flesh, I haven’t used them myself, but I don’t believe tapping an all-flesh will give you a trigger, it used your body as a patch cable. So you’d need a second all-flesh attached to a voltage source and your body would temporarily connect to the Teletype all-flesh.

edbkt · 2018-06-08T17:12:10.302Z

Hlp:

I ask because it seems Grid is plugged directly into TT too and not sure if TT actually understands midi?

Do not plug your grid directly into your TT. TT can’t provide enough power for a grid, so you risk damaging the TT and the grid. You’ll need a separate power supply for the grid such as the Offworld 1.