Resolume Forum

Hello everybody,

I have encountered another issue with OSC message transmission.
I use clipname to control an external application (TouchDesigner). However, I found that Resolume does not send clip names in certain cases (the same applies to other parameters when they are used).
Everything works correctly when I manually trigger a clip from the Dashboard. However:

• 1. When I use the Column Run button to start all clips in a column, Resolume sends the clip name for only one of them.

• 2. When I use Autopilot to switch between columns automatically, Resolume does not send anything.

• 3. The same issue occurs when using other parameters via OSC. For example, I use Fake Effects in Resolume to control VFX in an external application. OSC messages are sent only when the effects are located on the currently selected layer.

Here is a video demonstrating the issue:

Clip names are expected to be sent on deck load, and on clip name editing.

You probably get the messages on the clip selection changing with #1.

What are you trying to do with these?

I use special clip names to control shutter of my projectors.
I use special names like "P1ShutterClose" and "P1Shutter open" to send it to TouchDesigner. Touchdesigner sends pjlink command to certain projector then.

ok, so I'd recomend to have touchdesigner make a buffer of the clip names, on load or deck switch,
You can also ask for the clip names in advance, from TD, by sending a ? as string to /composition/layers/*/clips/*/name
You'll get the names, and can extract the clip position from the message addresses.

Then when TD sees the /composition/layers/1/clips/3/connected type messages, that would mean a clip's play state changes.
This has 5 states,
0= empty slot,
1=clip present, not connected or previewed
2=clip previewed, but not connected
3=connected, but not previewed,
4=clip previewed and connected.

You could then do a lookup in your clip name buffer and if there is a hit, do the thing you'd like.

This would work with the OSC output all messages preset.

Hello,

Yes, using the name buffer in TouchDesigner is a partial workaround. However, synchronizing all clips requires additional functionality (my project contains a score of 150 columns in Resolume).

Moreover, this approach requires the Resolume project to remain unchanged unless it is synchronized in advance. Overall, this solution feels like a workaround rather than a proper implementation.

Why not implement OSC transmission of the names of triggered clips? This would be much more convenient and would eliminate the need to synchronize clip names between TouchDesigner and Resolume.

Most importantly, it would allow flexible transmission of any string parameters, since currently this is the only way to output string data from Resolume via OSC.

This would significantly enhance automation in Resolume and simplify its integration with external applications. In this case, Resolume would become not just a playback tool, but also a centralized parameter hub for all connected external applications.

I hope you understand the idea.

Why not implement OSC transmission of the names of triggered clips?

Sounds like you need a solution quickly, you can buiild that on the TD Side in a few hours probably.

Most importantly, it would allow flexible transmission of any string parameters, since currently this is the only way to output string data from Resolume via OSC.

Wire patches could be used to send out OSC messages on triggering them. You could have these patches as effects or clips. With a custom Wire patch you can even have a String parameter to set up the message address you want to send out.
Making such a patch would be 5 minutes.

Sounds like you need a solution quickly, you can buiild that on the TD Side in a few hours probably.

No, nothing urgent for me. Fortunately, I’ve only encountered this issue in one of my projects.

Regarding the suggestion to create a separate patch in TouchDesigner: I’m not looking for a workaround, but for a long-term solution that I can use in other projects without additional overhead.

It seemed to me that extending the OSC module in Resolume to send the names of triggered clips should not be particularly complicated. If that is technically difficult to implement, that’s unfortunate.

This is simply a broader idea of using Resolume as a universal control hub for managing projects.

Wire patches could be used to send out OSC messages on triggering them. You could have these patches as effects or clips. With a custom Wire patch you can even have a String parameter to set up the message address you want to send out.
Making such a patch would be 5 minutes.

Thanks for the suggestion, but I have never used Wire in my projects. Also, I’m not sure whether a regular Resolume license allows me to create Wire projects. As far as I know, it requires a separate license, doesn’t it?

OSC shortcut system in Resolume is set up to send changed values. So when a name doesn't change, that won't go out, as many other params which don't change on clip trigger also don't go out.
I don't see this changing in the near future.

Wire would indeed need it's own license to run patches without watermarks. You can compile patches with a licensed Wire, and those patches woudl not need a Wire license any more to run.

Thanks!

I understand now. Thank you for the suggestion to compile the Wire patch. I’ve already done it. This is also a good solution for me.