Setting a Level and a Palette in a Single Command

I'm running version 1.9.6 on an ION and I can't seem to figure out how to set a level while setting a palette on our moving lights.

 

I tried something like: [1] [at] [Full] [Focus Palette] [1] [Enter] which I looks like it should work, but it doesn't.

Parents
  • 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.

     

  • 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]"

Reply
  • 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]"

Children
  • 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

     

Related