OK, cool. Funny that similar behavior struck us pretty much at the same time…

If possible, maybe try with a wired cable if it strikes back?

I’ve “deleted” scenes by saving a blank scene over the top of them, either via USB stick or the on-board TT save interface (which may not be available to you) by tabbing through with [ or ] before pressing ALT+ENTER.

Can you switch scenes using the SCENE X OP?

Proposing here a possible enhancement to add an op, possibly “PX” that can address the pattern data as a linear 0-255 (or possibly configurable) array to simplify when arbitrary dimensions are needed for a particular application, rather than 4x64 (or rather, in addition to the existing 4x64 capability).

This is a forward from the discussion segment that goes into more detail at:

1 Like

I started to get an issue with the teletype as mentioned here.

The problem: when you hit escape you’re prompted to switch scenes, if you hit alt+esc you’re prompted to save current scene. In both cases, the default suggestion from the teletype is the current scene, right? Ok, the problem is that “sometimes” my teletype starts to suggest a scene (both with save and switch scenes) that corresponds to the position of the PRM knob. Kind of as if it gets confused if I hit the small button on the panel and want to do keyboard-less loading.

It started after I added a JF to my i2c bus (tt + 2x txo + txi + JF + er301), and it only happens “sometimes”, usually after a while. I powered the case off and just waiting for everything to cool off, maybe it’s heat related.

Anyone had anything similar happen and found a solution?

That is very strange. In normal operation is there a threshold for PRM knob change that takes you from “suggest current scene” to “use knob position”? If so, you might have a noisy knob input.

EDIT: I don’t yet see where the knob value gets translated to preset selection in the code. preset_w_mode.c only shows [ and ] for switching presets…

Thanks! You got me on the right track!

I’m running a hacked firmware, and there was a problem in my code, everything is working perfectly now!!!

2 Likes