Setting a Level and a Palette in a Single Command

Try this. it worked for me in offline.

[1] [at] [Full] [Focus] [Focus Palette] [1] [Enter]

[1] [at] [Full] [Focus] [Focus Palette] [1] [Color] [Color Palette] [5] [Beam] [Beam Palette] [3] [Enter]     (Beam or Form)

If I leave out the [Focus] [Color] [Beam] it will not work.

Try this. it worked for me in offline.

[1] [at] [Full] [Focus] [Focus Palette] [1] [Enter]

[1] [at] [Full] [Focus] [Focus Palette] [1] [Color] [Color Palette] [5] [Beam] [Beam Palette] [3] [Enter]     (Beam or Form)

If I leave out the [Focus] [Color] [Beam] it will not work.

that's quite clever. i had thought about the ambiguity of At and tried [1][FocusPalette][1][Intens][50][enter] which had the same effect as using at instead of intens (i.e. setting the level but ignoring the palette). but i didn't think of using the parameter groups in combination with the palettes...

I use this syntax all the time. but with Presets.

When the lighting director ask "put all the movers on lift 4 and in that congo color we used last week and that breakup pattern"

[ Group 222] [@] [Full] [Focus] [Focus Palett] [104] [Color] [Preset] [12] [Beam] [Beam Palette] [5] [Enter]

And you can take the CYM from one Color Palette and the  Color Mode or Color Wheel from another Palette or Preset. 

Beam is fun to do this with. Gobo 2 from Palette2 Iris from Palette3 and  Beam FX from Preset 1

hey anne. sometimes it's not about keystrokes (and i remember that i was part of the clear/undo/where is my finger moving to - discussion), but about multiple stuff happening at the same time... ;-)

Indeed, leffertd's solution does work. It seems quite redundant though.

Could somebody explain the type of situation where [at] could be ambiguous?

Also, Anne's statement that you can not set separate palettes in one command does not seem to be true (at least on the software version that I'm using).

By the way, when I said that the manual suggests that this type of instruction is possible, I'm referring to page 142 where an example reads:

"Select channels 1 through 8 at intensity level 45 and sneak into color palette 4 over 40 seconds.
[1] [thru] [8] [at] [4] [5] [Sneak] [4][0] [Color Palette] [4] [Enter]"

Alright, you've got me.  :-) This is unintended syntax, which I'll admit I've never even thought to try... the enter key is closer and much faster to find.

Thanks for the heads up about the error in the manual.  We are doing a rehit for 2.0, so we will make sure to get that addressed.

One could argue that the [at]  command following a recall of FCB palettes should (could) modify the values for parameters drawn from those palettes.   [channel list] [zoom] [BP] [5] [at] [5] [Enter], setting the zoom values drawn from BP5 to 50% of their stored levels - as an example of a possible command - one which would be somewhat in keeping with the current support of [at]  when setting parameter values from the command line (not required, but not prohibited either).   

As I said, we have not yet ruled out adding extensions of at which would always be routed toward intensity, nor have we decided to do it.

Thanks much!

a