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.
