#1299

Aha! 20 characters of :bulb:
Thank you!

#1300

And yet these aren’t saved with the Scene, right? Why is that the case? I can use I to initialize my grid with specific functionality (thank you sooo much for the very helpful tutorials on GitHub, they are great) but I can’t save a pattern of buttons.

#1301

button states and fader values are definitely saved with the scene. do you mean button and fader definitions? these are not saved automatically, the idea is that you would put the ops that initialize them in your init script.

#1302

Just so that I understand, let’s say I’m following your Simple Step Sequencer example, trying to turn the internal grid into a trigger sequencer. I know I have to place the grid ops definitions for the buttons in Init so that the scene initializes them, but can I save the current trigger pattern (essentially the on off state of each button) with the scene, so that my trigger sequences are there when I load the scene?? I guess these would be values on each grid point, so those would get saved after all, and it’s just a matter of Init to apply the proper grid ops to take advantage of the values!
Makes sense.

#1303

yes, button states and fader values are saved precisely because otherwise something like a trigger sequencer wouldn’t be very usable if you lost your patters each time you power cycle, and they are restored whenever you load a scene. the only exception is SCENE.G op which is intended to be used precisely when you don’t want to restore button states / fader values.

when you initialize grid controls, that doesn’t reset their state, which is why you can reinitialize them in the init script each time a scene is loaded. if you do want to reset values it’s easy enough to do with G.GBTN.V or G.GFDR.V (which will set the button state or fader value for the whole group) or just looping with G.BTN.V / G.FDR.V.

1 Like
#1304

Hey all, this is my first post here so I hope I’m doing it right. I’m trying to update the firmware on my TT, and I can’t get the bootloader to start. I’m using a USB A to A cable, and I’ve tried loading it without a cable at all and nothing is happening. I’m sure I’m just missing something, any help?

#1305

To be clear: You are holding down the front panel button while powering up, and the Teletype behaves as normal (instead of going to bootloader)? Bootloader mode on the Teletype should appear as a blank screen and undefined behavior of the LEDs.

If it is an issue with communication to your computer, please double-check that you have installed the Atmel drivers.