What does not work (but would be nice):
/composition/link1/name
(dashboard effect names, per layer or comp)
/activeclip/name
/layer1/name
This is using Resolume 5, however
Now that I'm using Resolume 6, I've got a couple problems.Zoltán wrote:Resolume 6 supports text via OSC.
You can ask for the names by putting a question mark before the addresses.
Addresses for names are pretty straightforward, for example layer 1 name:
/composition/layers/1/name
to set it send a string to this address.
As another example, a column 3's address is
/composition/columns/3/name
A clip's address is
/composition/layers/3/clips/5/name
you see the scheme right, this is layer 3 clip 5.
The composition BPM's address is
/composition/tempocontroller/tempo
You can find out any address and expected value type and range by going to Shortcuts menu-Edit OSC and clicking on colored items.
Would you want to get a metronome signal via OSC?Downtown wrote:Also kind of disappointed I can't do a metronome over OSC.
Thank you for your response. Most of my concern was a lack of response at all. I love the program and I know you all work very hard on it.Joris wrote:OSC has always been a monster feature that's difficult to develop. It's insanely powerful and insanely versatile. That makes it especially difficult, since it can be used for so many things and we have to cover all those bases in a single implementation.
For instance, we've received lots of complaints about the granularity of OSC commands and the volume of output data on 5. This is what we've addressed on 6.
It can be expected that now not everything works exactly the same as before. After all, we're only human and we can't possibly foresee every possible use case. So when calling us out on this, please go easy on us. We've got a shit ton of things we need to work on every day. A long thread filled with lots of examples and broken use cases generally will get glossed over, since we can't realistically solve everything in one go.
So what I suggest is the following: Name the one thing that you're missing in the OSC implementation right now. Try to boil it down to a single use case. We'll then do our best to make that happen in an update. And like that we'll chisel at taming the beast that is OSC together.