Fade Override Buttons Topic is solved
Forum rules
Please do NOT post bugs here! If you spot a potential Bug please report it HERE first then you can chat about it with other users in the appropriate section.
Please do NOT post bugs here! If you spot a potential Bug please report it HERE first then you can chat about it with other users in the appropriate section.
-
dwebb1911
Fade Override Buttons
We mainly use simple single step sequences and change them using the override buttons. Is there a way to set a fade time when switching between buttons. So that when button 'a' is active and we select button 'b' there is a fade out of 'a' and in to 'b' ?
-
dwebb1911
Re: Fade Override Buttons
Simply put ... can I set a cross fade between override buttons
-
aussiechris
Re: Fade Override Buttons
Unfortunately no. Overrides are on or off. Nowhere in between.
You could use submasters to achieve this, sort of...
Load the single step sequences into a cuelist and then load that cuelist into a submaster. Now you can select each state with the Go/Back buttons then hit Run to trigger that state. This requires you to select the states from a list then trigger them with a single Run button rather than having a separate trigger button for each state. The submaster method is powerful because you can select multiple properties (Gobo, Pan/Tilt, Colour, etc...) on different submasters and run them all at once. It is a little more involved and complex though.
If you are a bit of a whiz you could use MAX or some other language to switch between submasters in the way you describe but it would take some programming knowledge. It would basically involve interpreting input and outputting the required string of commands to freestyler. eg: If you are at cue 5 and hit the button for cue 7, Max would need to send Freestyler the MIDI note mapped to G0 twice then the note for Run. It's not impossible, but not for the casual user.
You could use submasters to achieve this, sort of...
Load the single step sequences into a cuelist and then load that cuelist into a submaster. Now you can select each state with the Go/Back buttons then hit Run to trigger that state. This requires you to select the states from a list then trigger them with a single Run button rather than having a separate trigger button for each state. The submaster method is powerful because you can select multiple properties (Gobo, Pan/Tilt, Colour, etc...) on different submasters and run them all at once. It is a little more involved and complex though.
If you are a bit of a whiz you could use MAX or some other language to switch between submasters in the way you describe but it would take some programming knowledge. It would basically involve interpreting input and outputting the required string of commands to freestyler. eg: If you are at cue 5 and hit the button for cue 7, Max would need to send Freestyler the MIDI note mapped to G0 twice then the note for Run. It's not impossible, but not for the casual user.