With a lighting console, I'd set triggering up the other way around, having the console trigger Resolume via DMX
Looks like enabling the clip connect as output with a custom address, you actually get the 'connected' state.(actually gives you more info than the 'clip/connect')
This has 4 states,
0= empty slot,
1=clip present, not connected or previewed
2=clip previewed, but not connected
3=clip previewed and connected.
So if you launch clip1 in layer1, you get clip1/connected int 3,
if you launch clip2 in same layer, that will eject clip 1, so you get a /connected int 3 for clip2 and /connected int 1 for clip1, which has been disconnected.
If these are sent in a single OSC bundle (transition time=0) then they might be interpreted in any order.
We have a ticket for making clip connect available to map via OSC. (#12009)
Does this make things more clear?