OSC update order / timing causing inconsistent trigger arming

Hey @zacjohnsnz, the order of OSC updates is something I’ve tried to improve with the latest betas of AbleSet. With AbleSet 3.0, OSC values would be updated 1-by-1, so when a new section is reached, for example, the activeSectionName value might already be updated, but the activeSectionDescription might still contain the value of the previous section.

With AbleSet 3.1.0-beta.8 and newer, all related OSC values are updated simultaneously to prevent these kinds of race conditions.

Could you check if this works better with the latest beta?

One alternative I could imagine is creating two OSC tracks that set the keysTrigger and keysTriggerLabel variables at the beginning of related songs.

One track would be called Keys Trigger +OSC [/shared/keysTrigger] [single], and the other would be called Keys Trigger Label +OSC [/shared/keysTriggerLabel] [single]. You can then place clips named after the value you’d like to set.

Would that work for your use case? :slight_smile: