I try to trigger clips in resolume via OSC Tracks. Now when I use a midi clip to trigger multiple clips at once, they don’t start in sync. I read somewhere, that Ableset has a default delay of 50ms after each message seperated by ; in a clip.
Is it possible to change this value or delete this delay?
Otherwise I would need to make a new track for every clip I want to trigger, which is a bit much, because it happens only once or twice in the whole set. (also I can’t trigger columns in this case - normaly I would, so that is not a workaround)
There’s currently no global setting to disable the default delay of 50ms, but you can add a //sleep 0 command between the OSC commands you’re sending to Resolume in order to disable the delay.
I’ll check if I can make this available as a global option though
thank you for this suggestion, that is actually a nice work around for my setting.
And if there is one day a global option, I’d be stoked. But for now, thanks for the hint and your awesome work!
Hey Leo, I’ve found out another thing about delays in ableset. I have multiple fixtures and for every fixture group I created an osc track in order to have a good overview.
Now, when I trigger multiple Groups at once (3 Osc tracks with midi clips at the same time), I get a delay of 10ms between each of them, starting with the top most osc track and then going down, adding 10ms of delay with each track. So Track 3 would have +20ms delay compared to track 1.
Is there any way around this?
Also as said above, the sleep command did not work when I tried it.
I’ve been able to reproduce both issues on my end and will push a new beta with a fix soon. In the meantime, to reduce the delay between commands, you can use //sleep -1 instead of //sleep 0.
In addition, by default, OSC tracks with an external address won’t have any delay between commands anymore starting with the next beta.
Let me know if you find anything else, I’m always happy to help
You’re awesome dude! Do you have any time frame when this beta will come out?
I’m not sure if i want to jump on the beta or wait for the full release, as I’m afraid the beta could be unstable, which would be pretty bad on stage.
@FAster77 I’ve been using the beta on stage for quite some time now and haven’t had any major issues with it, but of course there might still be bugs that I haven’t discovered yet, so I’d recommend thoroughly testing it with your setup before using it live