Resolume Forum

I'm sure it's me, But here we go:
In the OSC mapping section, I'm given two options:
/composition/layers/1/clips/4/video/opacity
/composition/selectedclip/video/opacity

The first option does nothing, the second option, however, works.
Am I overlooking something here?

The OSC address requires a float from 0.0 - 1.0 and you need to make sure you have a clip loaded in Layer 1 Column 4.

So for 50% intensity, it should the string should look like this: /composition/layers/1/clips/4/video/opacity 0.5

So in TD when I map a constant (singular slider) and name the output to:
/composition/selectedclip/video/opacity
I can move the slider up and down and it controls the opacity.

When I change the name to:
/composition/layers/1/clips/4/video/opacity
Nothing happens when I move the slider.

Same clip is selected, as is the clip in the osc description (clip 4)


Here's what's weird...
The '/composition/selectedclip/video/opacity' command that works,
When I try to do the same 'selected' type command for a layer opacity:
/composition/selectedlayer/video/opacity
That does not work coming out of TD.
I figured if one 'selected' style command would work, they all would.

I'm sure it's something on my end, but I'm really confused on this one.
I'm pretty sure the slider on my constant chop is sending the 0-1 value, as I have it setup as sending 0-1 when i move the slider, so that should be adding in my float value.

When I go into the OSC window under preferences, I can see communication, it's just not working???

It's just weird that one works and the other command doesn't.
Here's a screenshot to prove that i'm not just making this up lol
https://www.dropbox.com/s/x63e2oc9ivag7ma/osc.jpg?dl=0

would it be because that layer is in a group? or does that not matter?

Thanks for all the help

The group shouldn't matter but are you sure you didn't move the layer up or down between the time you picked the OSC address in the mapping section and now?

Nope.
I just crtl+shift+O, copied the OSC path and pasted it into TD. Nothing more was done.

It's just strange that the 'selected' path works, but the 'directed' path doesn't work.

I'll try it on a fresh comp in the morning. One without groups and report back what I find.

Didn't know if this was a bug or if I'm just an idiot an overlooked something. (Very possible lol)

Any chance someone else can try to recreate this issue? Testing out the selected AND the direct OSC paths and see what their results are?

Thanks

Any chance someone else can try to recreate this issue? Testing out the selected AND the direct OSC paths and see what their results are?

I tested the OSC string for the specific clip both with the layer by itself and in a group and it worked as expected but I didnt test with TD

Oaktown wrote:

Any chance someone else can try to recreate this issue? Testing out the selected AND the direct OSC paths and see what their results are?

I tested the OSC string for the specific clip both with the layer by itself and in a group and it worked as expected but I didnt test with TD

Same here, it works fine.
This is what I get in the OSC inspector as input:

TD was adding an additional / to the start of the osc command.
This is fixed.

does anyone know how to invert an osc value, what command to add to an address for that? Got bypass buttons that need to be inverted and of course in midi mapping you just click bypass ...hoping we have a solution in adding onto the osc name though?

This is something that needs to be done on the host end, not the client end. You'll need to request this in whatever osc sending software you are using.