#202

Using it now, amazing :slight_smile:

#203

Yes, but as I expect is also true for others, my scenes are quite specific to my setup. I’ve also been really frustrated recently that when trying to create more complex scenes I very quickly run out of scripting space. I usually need 2 or 3 full scripts just to init all the grid ops etc. Other things that take up too much space include packing/unpacking multiple values into the 14bits of one pattern cell. I always seem to be short just ONE character on script lines arrggghh!! The 2 extra local vars have really helped things though. I’ve also started using unused/hidden groups of buttons and faders as storage (button levels, fader values) which is great. However, after seeing the amazing progress on PolyES, I think it is time for me to get an Ansible and use the Teletype more as a macro sequencer.

3 Likes
#204

(Pattern slots are in fact 16 bit… it’s possible that this is still incorrect in the docs, I’ve tripped on it myself)

#205

@EqualTemperament suggested using SCENE op as a way to extend scripts - dedicate one scene to setting up your grid controls and then call it from the main scene.

3 Likes
#206

Wow! Why did I never think of this? That will open up lots of possibilities. Thanks!!

#207

This post (Teletype 3.+ feature requests and discussion) gave me a MS EXCEL flashback. Not exactly the same as a norm dist OP with mean and std, but you can calculate it outside and provide it as a discrete lookup table.

edit: One thing I have to fix is not every $1 trig provides a value.

edit 2: need to fix output binning, skews to right.

Edit 3: I think I fixed it. Also using local K to free up global R at the expense of 1 line.

LAS VEGAS WEEKEND V3
RANDOM FROM DISCRETE DISTRIBUT
-----
PN 0: LOOKUP DIST (/100)
PN 1: OUTPUT DIST (COUNT)
$ 1: STEP BY 1
$ 2: STEP BY 1000



#1
P.I 0; J P.HERE
K RRAND 0 99
W <= J K: J + J P.NEXT
PN.+ 1 P.I 1

#2
L 0 1000: $ 1

#I
INIT.P 1

#P
...
5	0	0	0
11	0	0	0
21	0	0	0
26	0	0	0
21	0	0	0
11	0	0	0
5	0	0	0
3 Likes
#208

The code for Grid ops is extremely complicated to me at the moment, dunno if I’ll ever get my head around it.

#209

Is it perhaps that there is so much available? (of course a good thing). When I first came across it I was a bit overwhelmed - and I’m not a coder. So I set myself some simple tasks - like light up each button going right to left and when all buttons are fully lit - clear and start again. Do the same for going up and then down; throw in a little random. Found it useful just to get the feel of it.

1 Like
#210

this study should be a good start: https://github.com/scanner-darkly/teletype/wiki/STARTING-SIMPLE

3 Likes
#211

I’ve tried this technique with SCENE to extend scripts, but I’m not sure to understand how to implement it, it has to be called manually, is that correct ? If I call a SCENE from another one, it won’t execute the INIT script of this second SCENE ? Is it possible to provide an example of how to use this technique please ?

#212

yeah, it doesn’t execute init when you use SCENE:

but i think there are several ways to work around that (disclaimer: i haven’t tried any of this, just brainstorming). let’s say scene 1 is your main scene and scene 2 is the grid controls setup.

the easiest solution is to manually execute the init script. so in scene 1 init you do whatever you need to setup in your main scene and then the last line does SCENE 2. at this point it loads scene 2, you press F10 (or use grid control to execute init if you have grid already connected), it does what it needs to do and then as the last step executes SCENE 1.

a variation of the above that could make it easier: in scene 2 you create an extra button somewhere that executes the init script, and in the init just before it switches back to scene 1 you hide the button so it’s not in the way. this way you don’t have to switch to grid control mode.

another option: do initialization in metro script in scene 2. so, scene 1 loads, the init script switches to scene 2, at the next metro execution it will create all the grid controls and switch to scene 1. in this case you have to make sure you don’t put SCENE 2 in your scene 1 metro, otherwise it’ll create an endless loop!

2 Likes
#213

Thanks for your reply and this detailed explanation. I will try one of these solutions.

#214

YEAH (+ 16 characters)

#215

Just wondered whether there could be an option on this - either at firmware load or specialised word?

#216

yeah, perhaps a separate op which could be marked as “experimental” similarly to M!. this thread is a better place for discussion: Teletype 3.+ feature requests and discussion do you want to post there?

#217

trying to crowdsource this issue i’m having…

I’m new to TT and grid ops (and coding!) and with grid ops studies under my belt (yet still referencing), i wanted to check out the non-jf fugetta scene by @ghost. his script descriptions made it especially appealing as a beginner. I’m having an issue though and maybe someone has tried this out there.

i copied the scene a few times and had the same issue every time: no cv outs. are there lines i need to add to define cv values or variables? additionally, the 3 bottom right buttons (vertically) are wigging out a little, for lack of a better term, and the entire scene glitches out my grid to some extent. Is this because I’m running TT 3.0? would that have something to do with it?

any and all advice is greatly appreciated.

#218

do you get triggers output but not CV? from what i can tell you shouldn’t have to do anything to enable CV.

no, running tt 3.0 shouldn’t cause anything like this. could you describe what you’re seeing a bit more? i’ll try to test the scene sometime next week as well.

#219

Here’s what’s happening, apologies for the lack of quality in the clip. I’m getting trigger outs as you can see and hear, but no cv. The bottom right 3 buttons are flashing very fast (maybe related to the speed defined by the param knob, though I’m not quite sure). Those buttons are not toggled on. Strange.

#220

thanks for the video! i’ll test the scene and report back (won’t be able to get to it until next week though)

just a quick look for now: i think you’re meant to initialize your own scale in pattern values 9-15 (pattern bank 0). this is likely why you’re not seeing CV change. enter some values there (they are in semitones).

flickering is likely caused by reinitializing some grid controls which shouldn’t be necessary but hard to tell from a quick glance, i’ll need to parse the scene.

#221

Is there a way to display a fine meter type visualization kind of like a read-only fader at fine levels? I could use fader with type 4, but the inc/dec buttons obscure the lowest and highest leds.