Sequencer suffering after 50% space has been hit
Posted: 27 May 2014 12:18
Hello!
I've got a sequencer working on slave clock.
As I had the interface separate from the rest of my Uber-Sooper-Blooper-Bacon Flavoured interface, everything worked like a charm.
Now that I have everything set up in the same interface (55% space occupied and counting), the sequencers don't start where they should, they randomly catch up after 1-2 bars, even in the middle of the sequence.
I already have experimented slowness in the Scripting phase as the whole interface updates everytime everything, but when using it live, it has Always worked like a charm.
Have you experienced anything like this?
Let me know.
Thanks guys!
I've got a sequencer working on slave clock.
As I had the interface separate from the rest of my Uber-Sooper-Blooper-Bacon Flavoured interface, everything worked like a charm.
Now that I have everything set up in the same interface (55% space occupied and counting), the sequencers don't start where they should, they randomly catch up after 1-2 bars, even in the middle of the sequence.
I already have experimented slowness in the Scripting phase as the whole interface updates everytime everything, but when using it live, it has Always worked like a charm.
Have you experienced anything like this?
Let me know.
Thanks guys!