re 1: Out in this context bascially means home, so e.g. for red that's (for library fixtures) at 255.
re 2: that's on the list afaik. you can do that already for Setup>Show. for Setup>Desk you would need a macro. Setup>Desk>Displays is recorded into snapshots.

Thanks for the reply.

ueliriegg said:

re 1: Out in this context bascially means home, so e.g. for red that's (for library fixtures) at 255.

A. This is misleading because "out" shouldn't mean to take something to full, it should take it to 0. This is how it works with intensity and it's confusing to have "out" sometimes be the same as [full] and sometimes be the same as [at][0][enter]

B. If I want it to be full/home, I can just hit the full key or the home key so there's no need to have a third key that does the same thing.

3. Cannot do palette and intensity on same command line. - please change

4. [sub]x[out] should terminate the command line but doesn't.

5. Please add the ability to label channels in live.

EDIT: Not on a console, but Chan 1 @ 50 ColorPalette 2 Enter should work.

Hey Ueli!

When typing Chan_X_@_Y_CP_Z EOS takes the command line without any error message but will only change Intensity.

Using Preset instead of Palette it will give a Syntax error. Is this because the Preset could have an entry for Intensity to?

Would be bad for People like me who use presets more or less never with Intensity...

6. "undo" for magic sheet editing that undoes only the last magic sheet edit

7. unloading a sub from a fader shouldn't stop effects or change levels.

8. Have an option to hide/collapse/resize the parameter tiles. I never use them; I use either encoders or ML controls.  Not relevant now that the "about" display can be in a frame.

9. Enable a rate submaster fader for step-based effects Implemented, thank you

10. When creating a magic sheet - if I select fields to be a certain color, they should be that color from then on and not keep showing up in white.

11. The ability to re-import CSV values back into the console. Example: On many shows I have assisted, we will export Qs out the console and then Label Qs ourvelves....then er want to give them back to a Board Op for CSV Re-Import so their list can get updated with our Labels or Notes. We have to do as Assistants anyway and it we can give a file back to the Op, rather than spending Tech Time labelling hundreds of cues, this feature might alleviate all of that. 

12. More customization options on CSV Export. FastFocusPro generates its own folders of many, many CSV files. But, what if we want to re-create similar files? We are not able to. FFP is able to export CSV by specific parameters on Moving Lights, we do not have any options that allow us to select just "pieces" of things during an export. Ideally, it would be very nice to export the same files FFP generates in the console, but opened up to allow to user to choose what they want to send out. Really helpful for those not using FFP, but are using the raw data for different applications.

If you want your ML controls to open in the CIA, it would be nice if the tiles weren't there to cut down on scrolling.

It would be nicer to some day to have a way to open controls in an ephemeral window, kind of like the way the virtual keyboard on Nomad works, especially for context-sensitive controls like the ML control or certain magic sheets. I think that's what the OP is getting at. The tiles are wasted real estate if you don't use them, and the ML is wasted real estate if no channels with multiple parameters are selected.

#14: I'd like to have a double push of the "home" key is read by the console as "@home enter" basically as it works with "full"