On the Live Edit page, only one knob is used and it is the knob to select the page. I think one of these knobs could be associated with a control for the currently/most recently triggered Live Edit. The user could then assign a DMX channel for a fixture or group of fixtures to be controlled by this knob. In other words, each live edit cell could have an optional associated control that can be manipulated by one of the knobs.
That way, for example, if one live edit cell activated a prism on a moving head fixture, the associated knob in the live edit page could be mapped to the prism rotation speed (so instead of having to create different live edits for each speed of prism rotation, you would only need one cell to activate the prism and then the knob would be mapped to the channel that controls the speed of the prism).
Just like how you can override the DMX values in the live edit page, each live edit cell could have a DMX channel that is mapped to the “knob” when that cell is selected. In the the prism example, the live edit would enable the prism and the “speed” channel would be mapped to the prism rotation DMX channel which could be controlled on the live edit page by one of the first three knobs.
Feature Request - "Speed" Knob for Live Edit
Re: Feature Request - "Speed" Knob for Live Edit
We've been thinking about this. The challenge is how to assign the channels and the min and max values for each encoder.... 
Re: Feature Request - "Speed" Knob for Live Edit
Hmmm that is a tricky one. Maybe something would have to be specified in the profile in that case, which makes things more complicated.
On the other hand, one option could be Shift+Gobo opens up a Prism page (which would be similar to the Gobo page), with the ability to select no prism, or one of the prisms along with the rotation amount.
One possible workaround would be that some DMX values are specified in a range that goes from fast-to-slow. In this case, the value boundaries itself in the fixture profile for the specific preset would set the upper and lower limits of the speed range (For example, a "gobo scroll" often has low values being for slow scroll and high values for high scroll, while it is set between other gobo values). For other parameters, perhaps a different channel could be selected with the assumption that the boundaries of this channel would be 0-255.
Another option would be to create a "macro" page, (perhaps one that would be accessed via shift + live edit), where the knobs can be mapped to various DMX channels. I'm imagining something similar to the way macros are implemented in Ableton Live (although Live usually maps MIDI values, so the values there are 0-127). In this case, each knob could be mapped to one (or several, in the case of multiple lights) DMX channels, and each mapping would have min/max values for each associated channel.
On the other hand, one option could be Shift+Gobo opens up a Prism page (which would be similar to the Gobo page), with the ability to select no prism, or one of the prisms along with the rotation amount.
One possible workaround would be that some DMX values are specified in a range that goes from fast-to-slow. In this case, the value boundaries itself in the fixture profile for the specific preset would set the upper and lower limits of the speed range (For example, a "gobo scroll" often has low values being for slow scroll and high values for high scroll, while it is set between other gobo values). For other parameters, perhaps a different channel could be selected with the assumption that the boundaries of this channel would be 0-255.
Another option would be to create a "macro" page, (perhaps one that would be accessed via shift + live edit), where the knobs can be mapped to various DMX channels. I'm imagining something similar to the way macros are implemented in Ableton Live (although Live usually maps MIDI values, so the values there are 0-127). In this case, each knob could be mapped to one (or several, in the case of multiple lights) DMX channels, and each mapping would have min/max values for each associated channel.
Re: Feature Request - "Speed" Knob for Live Edit
This is pretty much what I was considering doing....One possible workaround would be that some DMX values are specified in a range that goes from fast-to-slow. In this case, the value boundaries itself in the fixture profile for the specific preset would set the upper and lower limits of the speed range (For example, a "gobo scroll" often has low values being for slow scroll and high values for high scroll, while it is set between other gobo values). For other parameters, perhaps a different channel could be selected with the assumption that the boundaries of this channel would be 0-255.
I'm thinking shift + hit one of the 3 encoders to edit it, then choose the presets you want the encoder to control in the same way you choose the presets to include in the Live Edit. You could set a custom name for the encoder in the same way as you would for a live edit. There would only be 3 per project but I think it's enough for most cases. If you put too many then it loses its live feeling...and we end up with possible memory and performance sacrifices too if we overload it.
Re: Feature Request - "Speed" Knob for Live Edit
Yeah, honestly 3 should be fine as there are only four knobs and one of them controls what page you are on. Just one extra way to get control without having to use up Live Edit spots for different speed values. Maybe just pressing the fader would release control back to whatever the default value/preset value is.
I've also done some trickery like remapped fixtures that don't have a Gobo but have auto programs where the auto program speed DMX channel becomes Gobo rotation and each gobo itself selects one of the auto programs.
I've also done some trickery like remapped fixtures that don't have a Gobo but have auto programs where the auto program speed DMX channel becomes Gobo rotation and each gobo itself selects one of the auto programs.