Resolume Custom OSC out -> Companion button trigger

Post your questions here and we'll all try to help.
Post Reply
phssydstryr
Posts: 1
Joined: Fri Nov 21, 2025 20:17

Resolume Custom OSC out -> Companion button trigger

Post by phssydstryr »

Hi everyone,

I have a small problem. In Resolume Arena, I have a video—let’s call it “mapping” for simplicity.

I set it up so that when this “mapping” finishes, it jumps to a blank clip where I wrote a custom OSC out address (/location/1/0/0/press). In Companion, this triggers a button that does the following: on that Resolume machine, it starts a basic loop; on another Resolume machine, it starts a video; it starts a Spotify playlist; and it pushes a fader on the SQ audio desk.

My problem is that whichever Resolume machine I send the OSC command from, no matter what I do in the composition, it always behaves as if I clicked that clip manually.

Does anyone have any idea how I could send a feedback to Companion that the mapping video has finished so that it can trigger the next actions?

tijnisfijn
Team Resolume
Posts: 352
Joined: Fri Dec 06, 2019 00:01

Re: Resolume Custom OSC out -> Companion button trigger

Post by tijnisfijn »

Whether the clip is triggered automatically from another clip or you click it by hand, Resolume sends the same OSC connect message, so Companion can’t see the difference.
You can work around this in two ways.

1) Listen to the connect state of the blank clip

Let’s say your blank clip is Clip 3 on Layer 1. Its OSC address is:

Code: Select all

/composition/layers/1/clips/3/connect
That address doesn’t just send 0/1, it returns different values depending on the state of the clip (selected, playing, both, etc.).

So in Companion you can do something like:
If the value is greater than 2, fire the action.
That way it only triggers when the blank clip is actually connected/playing, not just when Resolume is doing internal switching.

2) Listen to the position of the mapping clip

A cleaner option is to look at the transport position of your mapping clip, e.g. Clip 2 on Layer 1:

Code: Select all

/composition/layers/1/clips/2/transport/position
This value goes from 0.0 → 1.0 during playback.
You can put the clip on play once and hold so it stops at one

In Companion you can set a trigger like:
When the position reaches 1.0, trigger the next actions.
That gives you a very reliable “clip finished” signal, no matter how the clip was started.

Personally I’d go with option 2 – watching the transport position is the most bullet-proof way to know the mapping video actually reached the end.

Post Reply