OSC sending too many messages

[nmugnaini]

Hey hey
I'm having issues with OSC sending too many messages when clicking on clips. For every clip that has a custom address I get the previous message plus the current clip's message. It seems as though there's a 'release' command being sent out followed by the triggered command.
This wouldn't be a problem as much if the 'release' command and 'triggered' command happened in order every time but sometimes the 'triggered' command comes first then the 'release' command. Resulting in the previous clip's command being heard last.

Is this a bug or is there something I can do to fix this?
Cheers -Nick

[Sadler]

Do bundles help?

[nmugnaini]

No, it's still sending 2 messages.
I think I need the option to disable the OSC release message. Only looking for the OSC send message, probably something that the devs need to implement.

[Zoltán]

Have you created your own shortcut preset, or are you using the Output all messages preset?

Which messages do you receive exactly?

[nmugnaini]

I'm send Hog4 commands. I set 3 clips that would send trigger 3 different cues. Triggering the clips 1-2-3-1, I receive the messages pasted below: (Last to first)
RECV: GO CueList 1 Cue 3.000000
OSC RECV: '/hog/playback/go/0/1.3', types: 'i', args=[1]
RECV: GO CueList 1 Cue 1.000000
OSC RECV: '/hog/playback/go/0/1.1', types: 'i', args=[3]
RECV: GO CueList 1 Cue 3.000000
OSC RECV: '/hog/playback/go/0/1.3', types: 'i', args=[3]
RECV: GO CueList 1 Cue 2.000000
OSC RECV: '/hog/playback/go/0/1.2', types: 'i', args=[1]
RECV: GO CueList 1 Cue 2.000000
OSC RECV: '/hog/playback/go/0/1.2', types: 'i', args=[3]
RECV: GO CueList 1 Cue 1.000000
OSC RECV: '/hog/playback/go/0/1.1', types: 'i', args=[1]
RECV: GO CueList 1 Cue 1.000000
OSC RECV: '/hog/playback/go/0/1.1', types: 'i', args=[3]

If it's hard to follow, basically what's there when triggering the next clip I get a message from the previous clip as it's released. The problem with this is the trigger message and the release message can randomly be switched around which triggers the wrong cue.

[Zoltán]

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?

[nmugnaini]

Yeah I follow thanks. Just hope that release messages gets an option to be turned off. If you take a look at TouchOSC editor they have this implemented.

In the end I got frustrated and started triggering resolume with the console via DMX.