#312

indeed an old bug: https://github.com/monome/teletype/issues/172
i’ll post in this thread when i have a fix for it.

1 Like
#313

Topic: Loading St8p
If anyone have troubles with loading this scene fully working into teletype, simply remove in script 8 at first line (G.GRP Y; A MUL Y 8;) the last semicolon or add a space. As there is no space directly after it, the complete line will be missed while loading into teletype (3.2).

2 Likes
#314

Topic: 4-track, 16-step trigger/CV sequencer (v3.2)
I already corrected line L 0 3: TR.TIME I 10 to L 1 4: …
Don`t understand the usage exactly. In principle I understood what it should do. Example: Push and hold a button in top row. Adjust a row beneath the CV-amount what should be outputted on CV 1 at this step. Put a clock trigger into TR 1. It should run through all 16 steps and change the CV 1 amount on the one step you have adjusted. Instead it seems that the loop length is fixed to 1. With the two button technic as described from @andrus to change the length of the track it seems that I can only change the one single step which is constantly cycling. Perhaps someone would be so kind to post a short video to understand the two button technic.

#315

without parsing the scene - you should be able to press a key, hold it, then press another key.

that scene was likely done before G.GBTN.C and G.GBTN.X1 etc ops were added - these ops make it easier to detect and use multiple presses.

1 Like
#316

Will try it again tomorrow, but it seemed that it didn`t worked for me correct. Thank you for your hints G.GBTN.C and G.GBTN.X1. G.GBTN.C already did a very helpful job for me :slight_smile: .

1 Like
#317

Topic: morphing faders scene - added LIVE POSITION RECORDER
morphing faders with live position recorder.txt (2.6 KB)

A great scene by @scanner_darkly which shows teletype and grid potential very much. My add-on was at first inspired from the module Catalyst (https://vimeo.com/314062041). As there is some space left in the original morphing faders code I thought it could be possible to add a recorder for the morphing. I realized that it needs also to integrate the Telexi. As it is a fresh built and I only did some tests while programming yet, please let me know if there are any bugs or suggestions for improvements.

Getting started:

The original functions are - beside a changed cv slew control - the same.

TI 1: INTERNAL CLOCK RATE
TI 2: SLEW VALUE [@ TI 1]
TI 3: 0= STOP >0= PLAY
TI 4: 0= REC >0= STOP REC
>0.3= RESET
PARAM + IN: MORPH WHILE REC

IN:
TR 1: MORPHING [OSCILLATING]
TR 6: STEPS THROUGH RECORDING
OUT:
TR 1: CLOCK
@ EXT CLOCK TR IN 6:
TR 2: CLOCK DIVISION BY 2
@ REC:
TR 4: CLOCK

Turn all Telexi knobs to 9 o´clock. Best to use Teletype´s TR 1 out as a master clock source for recording. Switch to pattern mode to get visual feedback at pattern 2. Set the speed with TI 1. Turn TI 3 down to 0 to stop playback. Turn TI 4 to around 12 o´clock to reset 2nd patterns position to 0. Start loop recording by Turning TI 4 to 0. You can twiddle and record the morph position by turning PARAM knob. Adjust slew to your likes with TI 2. Stop recording and reset head to 0-position by turning TI 4 back to around 12 o´clock. Don`t forget to turn back TI 4 to 9 o´clock to release the reset. Turning TI 3 up will start playing your just recorded sequence.

You can also use the scene now as a simple 16-track collective sequencer.

Adding physics to the scene possible?

5 Likes
> teletype : code exchange
#318

great mod! morphing faders is one of my favourite scenes.

1 Like
#319

Thanks a lot for sharing all this amazing stuff. I am trying to understand the code and everything.
I have just one question about this Scene, that I can not find an answer for. What is triggering Script 3? Thanks

#320

huh, looks like script 3 is not used in that scene - i based my scene on @misuba’s scene and i guess when i modified it i replaced the buttons that were using it but left the script itself there.

a lot of these really ought to be cleaned up / documented - in my plans!

3 Likes
#321

Hi!
Thanks for sharing your script!
Im sending a clock to input one but the sequencer is not moving :frowning:
Im probably missing something obvious!
Thanks :slight_smile:

#322

Hi Thopa,

W AND EZ P.NEXT NE P.I - B 1:

A : at the end of a line is against the tt-rules. Delete the :. Should be all what I had corrected - didn`t saved this one in my archive. If this doesn´t solve the problem we need a more detailed look.

But nevertheless please also see my response to this scene a few weeks ago. Couldn´t get all working as intended. If you get it how it works, please let me know!

1 Like
#323

I keep meaning to finish a new take on Pressure Points but I’m a bit distracted right now by a mad quest to turn Just Type into a Subharmonicon… glad the idea has germinated even though my code is janky.

2 Likes
#324

Um… BOTH of your ideas in this 2 line post have caused me to drool on my keyboard a bit…

#325

Before you get too excited, you’ll need a TXi. Adapting for a faderbank would not be hard. Right now I’ve got it setting the base volume for both voices with PARAM and/or IN and looking to A, B, C and D for voltages to subtract for the volumes of the subs… that can probably be improved upon. And you’ll need a shitload of stack cables. But for a starting point:

SUBPAR NONAGON
RIPPING OFF MOOG INSTEAD OF
MAKENOISE FOR A CHANGE

TXI KNOBS CONTROL RHYTHMS
RHYTHMS PULSE TRIGGERS

PATCH TO SCRIPTS 5 & 7 (STACK
CABLES RECD) FOR SEQ 1 & 2

PATN LANES 1 & 2 ARE SEQS
LANE 3 SLOTS 1 & 2: SUBS FOR
VOICE 1
SLOTS 3 & 4: SUBS FOR VOICE 2

DO NOT TAUNT LANE 4

A & B: VOL REDUCTION FOR VOX 1
C & D: SAME FOR VOX 2

SCRIPT 1: CLOCK



#1
M LAST SCRIPT

#2

#3

#4

#5
I N + PN.NEXT 0 12
J - I N PN 3 PN 2 0
K - I N PN 3 PN 2 1
JF.VOX 1 I X; JF.VOX 2 J - X A
JF.VOX 3 K - X B

#6

#7
I N + PN.NEXT 1 12
J - I N PN 3 PN 2 2
K - I N PN 3 PN 2 3
JF.VOX 4 I X; JF.VOX 5 J - X C
JF.VOX 6 K - X D

#8

#M
I O; X ? EQ IN 60 PRM IN
IF ER TI.PRM 1 16 I: TR.P 1
IF ER TI.PRM 2 16 I: TR.P 2
IF ER TI.PRM 3 16 I: TR.P 3
IF ER TI.PRM 4 16 I: TR.P 4

#I
JF.MODE 1; O.MIN 1; O.MAX 16
L 1 4: TI.PRM.MAP I 16 1
M 125

#P
12	64	4	10
1	1	1	1
0	0	0	0
63	63	63	63

5	0	2	0
0	0	5	12
7	0	3	19
0	0	6	24
4	0	0	28
0	0	0	31
0	0	0	34
0	0	0	36
0	0	0	38
0	0	0	40
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0

#G
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000

0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0

I’ve got plenty of room left, shockingly, so I might add some grid controls for convenience, but what’s here is pretty fun to play with. I don’t have exact feature parity and I’m not convinced it’s gonna be practical to get it, but I’m also not very interested in it? I wanna see whatever hybrid nonsense we come up with.

Does this even make sense

3 Likes
#326

This sorta makes sense, but like most things in this forum, it’ll take me a bit to grok.

Lucky for me, I’ve got the TXi just waiting for some good use. I don’t have a lot of stack cables so it might wait a little for that. But dang, this is cool.

#327

shoot i guess i never saw this, or assumed someone else would pipe up. i know it is months later… but needs must.

it is a terminal command.

you open terminal
use cd to navigate to the location of the file to convert
type the command, replacing windows.txt with the file you want to conver,t and unix.txt with the desired ouput filename.

1 Like
#328

I’m trying to understand this amazing scene. Could I ask you some questions?

  1. I can’t find the op BREAK on the manual.
    In your code that means that every time P Z is not 0, script 8 won’t execute the following lines of code?
  2. I don’t have a TEXEXo yet and I don’t understand this line of code:
    TO.OSC.N Z + 40 PN 1 Z
    Why do you add 40?
#329

it’s under the control flow section - all ops are also listed in alphabetical order below if you need to find a specific one. BREAK halts execution of the current script, so yeah, in my script if P Z is not zero it will skip the rest of the script.

just to transpose it up by 40 semitones - the number doesn’t really have any significance, probably sounded good!

1 Like
#330

Thanks for the info! This afternoon I’m going to study the whole scene a little bit more.

1 Like
#331

I would like to ask you a few questions more (to you or to anybody who knows the answer):

M SCALE 0 15 30 200 G.FDR.N 0

  1. I don’t understand SCALE op. This means that M is a value between 170 (200-30) and 15 (15-0) based on top fader, right?

I + 35 * 30 G.FDR.N Z

  1. Are 35 and 30 arbitrary values like the 40 semitones you mentioned before? I guess they have no significance beyond that they are good oscillator decay values, but I’m not sure.

  2. This a more generic question regarding loops behaviour. Is script 8 called 16 times at each metronome beat? When is executed a line like TO.OSC.N Z + 40 PN 1 Z? Sequentially? I mean, we don’t know oscillator decay value yet. Decay value is two lines down. So I guess that all the lines from script 8 are executed in parallel 16 times per metronome beat. Does make any sense to you what I’m trying to explain?