Bug Report: Seems that the transition times are ignored when receiving OSC messages (like '/millumin/action/launchOrStopColumn', 2) when the option shift-skip transitions is selected in main settings. Otherwise everything works as expected
The OSC message /millumin/action/launchOrStopColumn only launches the column : it uses the timings specified in column's settings. There is no message that makes you able to launch a column with a different transition time.
If you activated shift-skip transitions and maintain SHIFT when sending you OSC message : yes, the transition will be skipped as expected. Else the transition is executed (I tested and it works fine).
I'm down the same rabbit hole. Continuous data tracks (MIDI, OSC, internal signals) are not affected by the transition time between columns.
As a workaround, I tried putting timelines with data tracks in the dashboard, but I’m running into another unexpected behavior: when you hide a layer containing a data track, the data track keeps playing.
Wouldn’t it make sense for the data track to be turned off as well?
I do not think it is the same use case (he does not use a data-track).
What is your transition ? "Crossfade only" (so no interpolation even for continuous the data-track) ? Or "Crossfade + animation" ?
Best. Philippe
PS : about hidding a data-track. Yes, this would disable it, but if this data-track is inside a timeline(and this timeline embed in the dashboard, indeed, this will not disable it (this use case is not managed). We will see if we can improve this in next beta version.
Oh thanks Philippe, sorry, I’m being stupid — I completely forgot about "Crossfade + animation".
Actually, in my use case (lights on an Arduino), I can only use the timeline to ramp my lights, thanks to the ability in the beta to change the frame rate to 25/50 fps. Otherwise, in 5.14i or when using "Crossfade + animation", my Arduino gets flooded (every ms I guess), and I couldn’t find a proper way to work around the anti-flood protection I also need in my code. But that’s fine for me.
Maybe it would make sense to also allow setting the frame rate of transitions in the dashboard? Not sure, just a thought.
If you're stuck with an old Arduino that can't handle that many messages (120 fps I guess), the easiest workaround is to lower your display refresh rate from ProMotion to 50 Hz (using BetterDisplay, for example). Millumin will adapt automatically and send the OSC messages at 50 fps.
For info, in latest beta, if you hide a layer running a timeline embedding a data-track : the data-track is ignored (same behavior as if you would directly hide the data-track).
Comments
Bug Report: Seems that the transition times are ignored when receiving OSC messages (like '/millumin/action/launchOrStopColumn', 2) when the option shift-skip transitions is selected in main settings. Otherwise everything works as expected
Hello @maronid,
The OSC message
/millumin/action/launchOrStopColumnonly launches the column : it uses the timings specified in column's settings. There is no message that makes you able to launch a column with a different transition time.If you
activated shift-skiptransitions and maintain SHIFT when sending you OSC message : yes, the transition will be skipped as expected. Else the transition is executed (I tested and it works fine).Best. Philippe
Hi,
I'm down the same rabbit hole. Continuous data tracks (MIDI, OSC, internal signals) are not affected by the transition time between columns.
As a workaround, I tried putting timelines with data tracks in the dashboard, but I’m running into another unexpected behavior: when you hide a layer containing a data track, the data track keeps playing.
Wouldn’t it make sense for the data track to be turned off as well?
Hello @hyll,
I do not think it is the same use case (he does not use a data-track).
What is your transition ? "Crossfade only" (so no interpolation even for continuous the data-track) ? Or "Crossfade + animation" ?
Best. Philippe
PS : about hidding a data-track. Yes, this would disable it, but if this data-track is inside a timeline(and this timeline embed in the dashboard, indeed, this will not disable it (this use case is not managed). We will see if we can improve this in next beta version.
Oh thanks Philippe, sorry, I’m being stupid — I completely forgot about "Crossfade + animation".
Actually, in my use case (lights on an Arduino), I can only use the timeline to ramp my lights, thanks to the ability in the beta to change the frame rate to 25/50 fps. Otherwise, in 5.14i or when using "Crossfade + animation", my Arduino gets flooded (every ms I guess), and I couldn’t find a proper way to work around the anti-flood protection I also need in my code. But that’s fine for me.
Maybe it would make sense to also allow setting the frame rate of transitions in the dashboard? Not sure, just a thought.
Sorry if I’ve hijacked the thread.
Could you elaborate on which feature you mean here: "thanks to the ability in the beta to change the frame rate to 25/50 fps"?
@ectoplasmosis
in Beta, in a timeline, check setup, you can change the frame rate of the timeline 24fps to 120fps.
Really useful to control the rate of OSC messages sent by Millumin.
My problem is, I think, Transitions fps in dashboard can't be customize so I guess OSC messages are sent each ms.
Does this option actually affect the OSC messaging rate?
Or is it just a timeline quantising setting?
it affects OSC messaging rate
For those who might be interested:
If you're stuck with an old Arduino that can't handle that many messages (120 fps I guess), the easiest workaround is to lower your display refresh rate from ProMotion to 50 Hz (using BetterDisplay, for example). Millumin will adapt automatically and send the OSC messages at 50 fps.
Hello @hyll,
For info, in latest beta, if you hide a layer running a timeline embedding a data-track : the data-track is ignored (same behavior as if you would directly hide the data-track).
Best. Philippe
Thanks a lot Philippe !