I still can’t believe the shadow script proposal got ditched…

Such a perfect match for the grid ops. And “functions” without sacrificing trigger inputs in general…

1 Like

no one working on it != ditched

3 Likes

Yes, but IIRC the proposal got mainly disapproved back then.

I think the pool of people needing shadow scripts shrunk somewhat when SCENE.G was introduced. Rereading the “more scripts” thread it seems like the shadow script idea, proposed by scanner, was well-received but scanner themself wasn’t convinced of its need. They have stated no intention of taking up the matter. But there are other active developers (@csboling and @alphacactus, notably) who might be convinced to take up the cause :slight_smile:

1 Like

I just wanted to chime in and say this is a total game changer for me. I have been thinking of all the use cases and so far it has been great!!

While the ability to call other scenes may have alleviated shadow scripts, the 4x64 patterns is still a significant limiter in my use case. I understand the interface challenges with implementing more patterns, and the fact that the amount of memory available is limited. I personally would gladly trade scene slots for more patterns.

1 Like

Script polarity is pretty interesting, thanks for the work on this.

I have to say that SCENE.G allows so much space for grid/Telex setup that I don’t find myself wishing for more scripts.

Another silly question: with the addition of the new local variables and such, should the variable status screen be updated slightly? Even to what we have now, I think the addition of the ‘in’ value would be super useful! I’m not sure how that would happen, but maybe a ‘status’ screen could be prototyped instead of viewing the globals from the live screen? Maybe the same keystroke on the live screen could bring it up. This could contain values of globals and locals so you could see stuff happening in real-time.

This got me to thinking how the fonts are handled on screen. Is that part of the firmware or native to the screen itself? Could the fonts be scaled to half-size? This would allow a single page status screen (and [ahem] could increase script length…). I know that would break everything and won’t happen. I’m just curious.

I see that this would be a useful feature but I use the current live screen w/ variables quite often to try things out. So I would not want to loose it for a status screen w/o live mode.

1 Like

Like the CV and TR getters, KR.CV, FADER, TELEXi ops and others, IN and PARAM are polling ops – they grab the ADC value only once when you execute the op, the “continuous” value of these inputs is not known. There is not really a way to display the current IN value, the best you can do is poll it by storing it to a variable in the metro script, in which case you can see its value get updated at metro rate.

The font is defined in a bit-packed format here, it has a fixed height where characters are 6 pixels tall. I imagine you could get a smaller typeface like 3x3 to work, though some alias symbols, like &, might be hard to render. This would probably require reworking everywhere in the Teletype code that draws text to the screen.

1 Like

sorry for a downer but i had started doing work on shadow scripts and going through the code to figure out how to implement it but i fell into debt and serious depression around everything political happening where i live rn and i just dont have the energy to work on it. i’m trying to trade my tt and some otherstuff to hopefully get a norns since i know i can add new engines and translate ideas to it easily. i just dont have enough money for the kind of eurorack instrument i want to build (a 6u x 84hp case full of stuff i like comes out to ~ $4500 and i just cant do that or have that amount of money in one instrument).

3 Likes

Yeah I’m aware that we wouldn’t see the continuous value of the IN, and I wouldn’t expect it. However even just an update everytime it is sampled would be illuminating.

I appreciate the font information! Interesting stuff. The 3x3 font is not nearly as nice as the current 6x3.

Bit of a niche request here, but ever since I discovered my 12 year old walnut 64 works nicely with teletype I’ve been thinking about how much fun it’ll be to have both that and my new grid (which runs into ansible) for live performances. So, I was wondering… would it be possible to add support for the tilt sensor to teletype? It would be so cool to read the state of that, especially for live performance use!

I have a big problem with SCRIPT.POL on my teletype 3.1.0 6FBA23A. Basically I can’t get it to trigger only on rising edge. Here’s what it does in each mode:

0: no triggering (as expected)
1: no triggering
2: triggering on both rising and falling edge
3: triggering on both rising and falling edge (as expected)

Anyone else with the same problem? (My teletype is just back from repairs and I put version 3.1.0 on it immediately. Hoping it’s not a hardware issue.

EDIT: turns out that this bug only shows up if you’re using DEVICE.FLIP (as I am). Flipping the screen and inputs round reverts to the usual behaviour for me.

1 Like

sorry for bringing this up again. but I fail to see how SCENE.G is an alternative. yes you can move the initialisation stuff to another scene. but you still likely want scripts as backbone for grid ops logic and effectively also loose a trigger input. just my 2c

Probably when you’re FLIPped $.POL is affecting script 8 instead. Sorry for the trouble, will work on a patch for this tonight.

1 Like

Fixed build for broken trigger inputs with DEVICE.FLIP engaged:

teletype.hex (581.2 KB - 2ef0d28 - 2019/07/11)

Here’s the PR. They really ought to add a git commit --facepalm.

6 Likes

20 chars of “Thank you :pray:

New beta: teletype.hex (584.2 KB - 6ddf2c7 - 2019/10/06)

  • FIX: broken SCRIPT.POL behavior when DEVICE.FLIPped
  • FIX: improve CV output latency
  • NEW: call metro with SCRIPT 9 or init with SCRIPT 10
  • FIX: parts of help mode had display glitches and couldn’t be read
  • NEW: search forward (C-f / C-s) or backward (C-r) in help mode
  • FIX 2019/10/06: out of bounds crash with repeated searches
21 Likes

Awesome, thanks for the fixes and new features! I’ll try this out.

its_happening.jpeg

Are the $ aliases included?