#82

Seeing some odd behavior with loading scenes:

My Scene 31 is for calibrating my Telex output offsets and it only has stuff in the Init script.

If I power off from that scene, then power back on, it comes up in Scene 31. All the scripts except “I” are blank. If I press the button on the Teletype module, select another (blank) scene, then press the button again–I still have Scene 31’s “I” script.

This happened with another scene too: all of its scripts carried over into the selected scene.

(a few minutes messing around …)

Oh, it looks like the “new” scene is actually overwritten–I just lost what was in Scene 1 when it was overwritten by Scene 31’s stuff (i.e. init script and everything else blank)

Edit: Running V2.2.0-ALPHA.10 … that was the latest I could find in the thread.

#83

Beta 1 is linked at the top of this thread. But that’s not substantially different from Alpha 10. Chances are it won’t affect the behavior you’re observing.

#84

I tried to reproduce the problem but was unable to.

Here’s the testing procedure that I used.

  • Setup:
    • Power up teletype
    • Populate 1, 2, and I scripts in scenes 1, 2, and 31
  • Test:
    • Press button
    • Turn knob to select scene
    • Long press button to load scene
    • Investigate scene contents
  • Test Sequence:
    • Test scene 31
    • Power cycle teletype
    • Test scene 1
    • Power cycle teletype
    • Test scene 2
    • Test scene 31
    • Power cycle teletype
    • Test scene 1
    • Test scene 2
1 Like
#85

(Updated to beta firmware …)

The problem was that I wasn’t pressing the button long enough.

But the behavior is very odd (and undocumented AFAICT) when you perform a shorter button press: the scene number, as confirmed by hitting the ESC key, changes to whatever you selected but all the scripts in the scene you came from show up. It looks very much like a copy & paste operation.

1 Like
#86

An interesting UI case, certainly.

The logic is that:

  • You entered the scene load menu
  • You changed the menu position
  • You exited the scene load menu
  • The internal state of the load menu does not change

There is conflict between two obvious expectations:

  1. A fresh load menu should display the current scene
  2. The knob position should directly relate to the current scene

If @tehn and the community thinks that 2 is more important than 1, then teletype is working as intended. If not, then the behaviour can be changed with a trivial amount and complexity of code.

The workaround will be simple but an edge case arises with knob jitter wherein if the knob is in a “jittery” position, then expectation 1 will not be met as the knob jitters after or during menu load.

1 Like
#87

Hitting ESC after editing scripts and getting anything other than the current scene number seems to violate the rule of least surprise. I write code for a living, and it had me fooled.

My $0.02: If a long press is intended to load a new scene, then I think a short button press should abort the scene loading process altogether–not leave it in a hidden select state.

2 Likes
#88

I agree that is one of the sides in the conflict (side 1, above), although I wouldn’t call the current knob position “hidden”.

In the modular community there is an opinion that knobs should have immediacy. It might be desirable to know that if you crank fully clockwise, then press and long-press the button, that you will load scene 31.

I don’t have a preference either way, as I always have a keyboard plugged in so I can SCENE 31. Users with something else attached to USB during a performance probably will.

1 Like
#89

Not sure if this is a bug:

A few weeks into using 2.2 alpha 10, I got a strange behavior in Scene Load mode, where the scene number moves quickly to number 19. It doesn’t jump, but quickly increments (or decrements, if above 19) to 19, and stays there. When I try to manually change it, it resists!

This happens consistently and on every try, not occasionally.

Things I have tried which did not help:
Upgraded to 2.2 beta 1
Downgraded to official stable release, 2.1
Disconnected the keyboard (to mike sure the problem is not a faulty KB).
Powered on with no KB attached.

If it is a bug, then it must have been introduced before 2.2, because downgrading to the official 2.1 did not help either.

Any ideas what could be going on?

========[SOLVED]========

The PARAM knob was the culprit. Fiddling a bit with the knob fixed it.

#90

always 19?

try turning the param knob to select?

still 19?

#91

That did it. I’m not sure what was going on. But turning the knob fixed the issue.
Thank you.

#92

Would it be possible to let the SCRIPT op call M and I as 9 and 10?

4 Likes
#93

Being able to call the Init script certainly would be useful.

1 Like
#94

I’m imagining using it to make shuffled/swung metro times as well

1 Like
#95

Great suggestion that desserves at least 20 characters !

#96

Indeed! But why not M and I as argument to SCRIPT? More readable and less obscure (I for a long time had no idea about those key bindings, and kinda found pressing M and I way more obvious)

1 Like
#97

Yes, especially since some of us would like to see scripts 9-16 (or whatever) added. :smiley:

#98

But M and I are already used for other variables and I feel that could get confusing

1 Like
#99

very true… not even sure the grammar would allow this. I shouldn’t post to a forum before morning coffee :bowing_man:
still don’t like 9 and 10 myself.

SCRIPT 0 for I would kinda make some sense, then again triggering M is much more interesting

#100

I wonder what one could reach by triggering M from a script that would not be possible by using M in that script?

I can see a use for resetting to I though when all orher scripts are in use. Should be possible eith the upcoming timeline though.

#101

see boob’s post above: