Resolume Forum

Hey Ravensc,

I finally got a chance to really give your Resolume controller a good try and it's really fantastic! Thank you for developing it!

A few questions and comments:

Any chance to minimize that big red exclamation point when the controller is not in focus so that we can still see the scenes. How about a big thick red line around the window?

Any chance you could implement layer control of layer transition time so that each layer can have its own time in a similar way as the blend mode:

• @T6.5 layer 3@ sets transition time of layer 3 to 6.5
  @T1 layers 2,4@ sets transition time of layers 2 and 4 to 1
  @T5 layers 3-6,8,10@ sets transition time of layers 3,4,5,6,8 and 10 to 5

then ideally all could fit in the same clip name such as:

• @T6.5 layer 3@@T1 layers 2,4@ etc...

What OSC command do you use to set the global transition?

Is there a way to trigger scenes in your software from a third party OSC controller such as Qlab? I tried but there seems to be a conflict when I try to do so and I get an automation panic which could be because there is no way to turn bundles off in Qlab! Thoughts?

Ideally, I'd want to be able to connect to Controller (port 7001) and launch scenes with a command like this: /scene N where N is the scene number. Is that possible?

Oaktown wrote: I finally got a chance to really give your Resolume controller a good try and it's really fantastic! Thank you for developing it!

I'm glad you like it!;)

Any chance to minimize that big red exclamation point when the controller is not in focus so that we can still see the scenes. How about a big thick red line around the window?

I see how that could be useful, I'll include a switch for this in preferences for the next release.

Any chance you could implement layer control of layer transition time so that each layer can have its own time in a similar way as the blend mode:

• @T6.5 layer 3@ sets transition time of layer 3 to 6.5
  @T1 layers 2,4@ sets transition time of layers 2 and 4 to 1
  @T5 layers 3-6,8,10@ sets transition time of layers 3,4,5,6,8 and 10 to 5

then ideally all could fit in the same clip name such as:

• @T6.5 layer 3@@T1 layers 2,4@ etc...

I'll have a look at this, this has implications for autolaunch.
autolaunch is designed so that if the autolaunch is happening sooner as the current transition ends, the transition time is adjusted to allow the transition to finish before autolaunch.
for example when launching Scene no2 : 3seconds autolaunch with 5 seconds transition "fadeIn" then this scene's transition time is modified to 2.95 seconds so it finishes in time. - thinking of this, I'll add a setting to disable this behavior.

What OSC command do you use to set the global transition?

I'm just setting the transition time for each layer individually. /layerN/transitiontime f

Is there a way to trigger scenes in your software from a third party OSC controller such as Qlab? I tried but there seems to be a conflict when I try to do so and I get an automation panic which could be because there is no way to turn bundles off in Qlab! Thoughts?

you got that message avalanche because you tried to osc to localhost, and Controller responded to the same port, causing a osc feedback loop with itself, and if resolume was running on the same localhost, then resolume's osc messages were recognised as remote commands...
I never thought that Controller would be controlled from localhost via osc, so the remote destination port was the same as the Controller listen port.
I'll add a setting for this port,
and for the case you want to have Qlab and Resolume and Controller on the same machine, you'll need to set Qlabs OSC destination so that is different from the Resolume destination port.
for example Resolume OSC out to 127.0.0.1, and Qlab OSC out to 192.168.1.12 (LAN Address)

Ideally, I'd want to be able to connect to Controller (port 7001) and launch scenes with a command like this: /scene N where N is the scene number. Is that possible?

It will be.

Thank you!!!

I tried the IP address instead of localhost and got the same behavior but I got it to work on with Arena 5 + Controller on PC media server and Qlab on a MBP.

I noticed a small typo in your readme.txt

I believe it should read:

• transition time /transitiontime Float 0.0 - 10.0

instead of:

• transition time /transitiontime Float 0.0 - 1.0

This is my 2nd consecutive post so don't miss the other one.

Another thing, if Controller is on, the following OSC commands:

• /layerN/transitiontime 0.0-1.0
  /activelayer/transitiontime 0.0-1.0

sent from a different controller to Arena that's being controlled by Controller (IP port 7000), have the unexpected behavior to move all layers at the same time instead of moving just one.

If I quit Controller, normal expected behavior is back.

Any thoughts?

Oaktown wrote: I tried the IP address instead of localhost and got the same behavior but I got it to work on with Arena 5 + Controller on PC media server and Qlab on a MBP.

this will hopefully be fixed in the next release.

I noticed a small typo in your readme.txt
I believe it should read:

• transition time /transitiontime Float 0.0 - 10.0

instead of:

• transition time /transitiontime Float 0.0 - 1.0

Yes, not a typo, this is for better Human readability to send 10 secs to Controller if you want 10 sec transition.

Another thing, if Controller is on, the following OSC commands:
/layerN/transitiontime 0.0-1.0
/activelayer/transitiontime 0.0-1.0
sent from a different controller to Arena that's being controlled by Controller (IP port 7000), have the unexpected behavior to move all layers at the same time instead of moving just one.
If I quit Controller, normal expected behavior is back.

Controller is designed for global transition times, so the Client 1/Master resolume can set other slave's and itself's layers global transition time by moving just one fader in the master.
if you don't want this behavior switch off 'transition time relay" in Controller preferences.
Then these transitions won't be controlled by the master.

what happens is
OSC to resolume to set transition time for layerN
OSC from resolume to Controller for transition time layer N
OSC from Controller to Resolume for transition time layers (all but N)

I uploaded an update, with some of these issues fixed. (v1.94)

1.94 :

• new:
  • OSC Remote (your phone) port changeable.
    OSC Remote can directly launch scene with /scene i message
    when in background, window warning can be switched to let user
    • see the scene list. see "show scenes in background" in preferences
    added option for "Adjust transitiontime for shorter Autolaunch" for example when
    • launching Scene no2 : 3seconds autolaunch with 5 seconds transition "fadeIn" then
      this scene's transition time is modified to 2.95 seconds so it finishes in time.
  fixed:
  • scheduled scene launch sometimes inaccurate
    Controller running on BootCamped Windows reported different machineId (see preferences)
    changed: connection check interval setting moved to clients tab in preferences
    Disabling automation didn't disable Schedule
    When preferences was reopened fast, the old setting values were shown.
    Autolaunch Transitiontime correction was not restored when corrected
    • transition was overrided by the user.