Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

start sequencer example, load different interface, come back #9

Open
x37v opened this issue Jun 3, 2011 · 1 comment
Open

start sequencer example, load different interface, come back #9

x37v opened this issue Jun 3, 2011 · 1 comment

Comments

@x37v
Copy link
Collaborator

x37v commented Jun 3, 2011

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.

@charlieroberts
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants