I encountered two problems during a show I made using Resolume 6.0.7 and OSC.

First problem : let's say I want to control clip 1 on layer 3 : if I send "/composition/layers/3/clips/1/transport/position/behaviour/playdirection" and add an int argument between 0 and 3 (as written in documentation) I will only be able to play backward or forward with "0"and "1" values, "2" and "3" values won't have any effect (no pause or random playback).

The second one appeared when I tried to control the same clip timeline position through OSC. Wherever I move the position, the media restarts and then go to the asked position. This doesn't appear when the position is moved with a mouse. A trick I found is to set the media on pause manually (because it doesn't work with OSC as said above) and then move.

Are those bugs known ?

Thank you,

Alex

Last edited by theoriz on Mon May 28, 2018 15:48, edited 2 times in total.

I still have the same problem.
OSC play and pause (.../direction/2, .../direction/3) don't work, on global, layer and clip levels,
This problem exists both when trying to send OSC messages manually, but also when syncing two Resolume Arenas on two computers through OSC.

I apologize, that's what I meant.
Sending integer / float 0, to an address like /composition/direction or /composition/layers/1/direction, works.
Sending any other number, int or float, always triggers the "play forward" button.
As if inside Resolume Arena the type is actually coded as a boolean (where anything other than 0 is interpreted as 1).

Like I said, this also causes a problem with Resolume's own OSC syncing feature, so it is definitely a bug on Resolume's side.