#100

i definitely agree that the ability to copy whole scripts would be quite useful. perhaps even just the ability to copy multiple lines would be useful? i often find myself deciding to break out multiple lines to their own script.

from a ui perspective, it seems like using shift + up/down to select multiple lines could be an intuitive way to do this? then the selection could be copy/cut as usual. i suppose then the ux issue that would arise from that method would be dealing with what happens when pasting multiple lines into scripts that are already populated.

1 Like
#101

this +1

command + shift + C to copy all?

#102

+1 on this too… I often find myself wanted to copy whole pages of scripts to a new scene

#103

The scene command definitely works, that’s one off the list.

#104
  • 1 for copying scripts.
#105

ok it’s in

6 Likes
> teletype : code exchange
#106

Scoooooreeeee! Thanks!

#107

The more i use my TT the more i find myself in need of more than 3 general purpose arguments (ok 4 with T…) and this limitation often prevent me from achieving some interesting and more advance algorithms.

• So would it be complicated to add 3 of them (maybe U, V, W) ??

:innocent:

#108

use A-D and just assign your TR’s with 1-4

#109

Didn’t know about that, sry … :sweat:

1 Like
#110

considering what I read about the use of incoming MIDI information (basically, I mean: payload’s message of a midi note message are the pitch and velocity for instance), I have a request for v2.

I’d like to be able to make the teletype read specific value from the outside.
For instance, I have a script running.
It is “open” to sense the outside world, I mean some CV inputs.
As far as I know, it only can read one CV value. But I’d like to know if trigger input are digital software-based but there are ADC behind them.

The idea would be to make another module controlling scripts using more than one voltage.

Forgive me if that is already implemented. Indeed, I still didn’t dive into it as deep as some of you already did.

3 Likes
#111

Something like that ??? => http://llllllll.co/t/a-teletype-expander/

1 Like
#112

@tehn
I don’t see anything about curved functions possibilities (LOG and EXP) in the github? As we spoke a little bit about it last year i was wondering if something similar in taste is still topical. :slight_smile:

2 Likes
#113

would be useful to have a variable, % or something like that that would resolve to the script number. so if you have CV % 1000 on script 1 it will resolve to CV 1 1000, on script 2 it will resolve to CV 2 1000 etc etc

i find i often duplicate the same line or script between different triggers only changing the outputs, so this will mean not having to edit the output number. could be used for other purposes, of course. this will especially be helpful once it’s possible to copy complete scripts.

not sure what would make sense for M and I scripts, perhaps just have it resolve to 0 for both.

6 Likes
#114

Couldnt find this mentioned before but sorry if it was

It would be interesting if users could load only scripts or only tracker patterns from scenes instead of both. Just thinking of how interesting it would be if an ongoing pattern is being played, only to be played in a new way by new scripts

#115

I just noticed that the latest firmware supports numeric keypads for launching scripts manually. Would it be possible to add the same functionality for the factory keyboard using a shortcut? For instance CTRL-number etc.?

1 Like
#116

i believe that exists as windows key+1-8

#117

Manual Script Launch Key Combo

[WIN] + [CTRL] + [1-8]

Thx for pointing it out; so handy!

:slight_smile:

1 Like
#118

Excellent thanks. Can’t believe I missed that one!

#119

And an II ALL.STOP? I routinely find myself wanting a dead stop to a piece, rather than fading back the mixer.