You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So.. If I start the sequencer and then load another interface via the interfaces menu, its cool that the sequencer still runs.. the problem is that the sequencer state isn't retained when i go back to the sequencer interface.. so i cannot edit what is running, or more importantly, stop the sequence..
this is with version 1.2 on the ipad.
The text was updated successfully, but these errors were encountered:
Yeah. The sequencer patch could have a database table attached to it and some load / save buttons. That would be a few hours of work though. Another thing that would be nice is the OSC Messages could be bundled and timestamped... should be able to get much better timing that way. Right now there's no way to send bundles directly from Control though.
I have thought about the issue with not being able to clear timeouts after you leave an interface. I've been meaning to implement some type of global container for timeouts that would always be cleared whenever you leave an interface. This would allow you to have multiple timeouts running in an interface and still have them all be cleared correctly whenever you transition to another interface... basically every time you left an interface the array of timeouts would just be looped through and cleared.
So.. If I start the sequencer and then load another interface via the interfaces menu, its cool that the sequencer still runs.. the problem is that the sequencer state isn't retained when i go back to the sequencer interface.. so i cannot edit what is running, or more importantly, stop the sequence..
this is with version 1.2 on the ipad.
The text was updated successfully, but these errors were encountered: