Alternatespeed #877
Alternatespeed #877
Conversation
The idea is: RGBMatrix innerSpeed differs from "normal" speed. The "normal" speed is the "outer" speed. The innerSpeed is the speed of each step. Same for Chaser: The innerSpeed is the speed for each step (in Common speed mode) Other alternateSpeeds are available for Chaser, these are the speeds of each individual step (in Per Step mode) The alternateSpeed allows getting/setting these new Speeds. This will allow the VCSpeedDial to change the speed steps of a Chaser. The main goal of alternate speeds is: when changing the "normal" speed of a chaser or rgbmatrix, the inner speed is not affected.
Otherwise the cuelist looks stopped while playing with a speeddial
Overridespeeds are ignored anyway
|
Screenshots of the speed dial properties & the function selection tool: 2 AlternateSpeed from a chaser are affected by this speed dial: When trying to add other functions or function alternate speeds in the speed dial, the currently selected alternate speeds are grayed (as is currently the case with functions) |
|
Ouch ! Perfect timing to conflict with what I am doing in the bpm branch 😭 By the way, how does the Function selection widget behave with Sequences ? |
Yes, I've seen you've been working on this too. Sorry about that 😄 For sequences, it simply writes "step 0", "step 1"... instead of "0.function0", "1.function1".... I'll post a screenshot of a sequence in the function selection tool tonight if you want. |
|
Here are screenshot with a sequence
|
Without this, when adding a sequence-container scene to a vcspeedial, the contained sequence and it alternatespeeds are not selectable anymore.
|
If you need help merging alternatespeed and bpm, let me know. Nitpicking: steps in UI should be numbered from 1, not 0, it's more "human" :) |
|
Too many conflicts with the bpm stuff :( |
|
What about my proposal of "speed override priority" ? |
This could be split in 2 pull requests:
Details in the commit messages.