Setting a Level and a Palette in a Single Command

No, That's not how palette's work, I'm afraid!

Focus Palletes just record focus (ie Pan and Tilt) values, not Intensity.

So [1] [record] [focus palette] [1] [enter] will record the pan and tilt position of the moving light on channel 1.

If you want to record the level you need to either record an intensity palette as well or (probably more commonly in this kind of situation) simply record it in a cue.

So to use the focus palette:

[1] [focus palette] [1] [enter]

sets the pan and tilt of the mover on channel 1 to the previously recorded focus palette 1

[1] [@] [full] [enter]

sets the level at full

{record] [cue] [1] [enter]

records the mover at full in the position set by focus palette 1 into cue 1.

That help a little?

Andy

I don't think I made myself clear enough. I understand that palettes only record one category of data. I'm not trying to record or create palettes; I'm trying to recall the palettes to a fixture in live.

My problem is that I can't seem to recall a palette to a fixture and set a level with only one entry in the command line, even though it seems the manual suggests this should be possible.

It's already possible to recall more than one type of palette to a fixture at once. Ex: [1] [Focus Palette] [1] [Beam Palette] [2] [Enter] will recall beam palette 2 and focus palette 1 to fixture one

You could try recording an intensity palette. Even if it's simply a case of recording 1 through x at full in IP1...

Thoughts for a new desk function: could intensity palettes work like cues? ie, chan x @ IP ON. Then, you could say (to use  the above example): [1] [Focus Palette] [1] [Beam Palette] [2] [IP] [ON] [Enter]

Of course, [IP] [OFF] might be more useful (saving making channels data 'absolute', for example)!

to me it feels like a bug. the desk doesn't return an error message so the syntax should be valid, shouldn't it? however, it only executes the intensity command and ignores the palette. maybe Anne or someone from the team could shed some light on this...

Intensity and Focus are 2 separate palettes and cannot be combined on a command line as far as I can determine.  Not a bug, just the way the console works.

Record all as a Preset then Recall or Sneak the Preset.

Steve B.

hey steve

well, you can set different palettes in one command line. and if the intensity is in a intensity palette it works. just don't see why it shouldn't work when values of absolute data and palettes are combined....

cheers

ueli

This certainly does seem like a bug to me. I don't see why the others aren't seeing quite what I'm trying to do.

Also, what does having a [Intensity Palette] [On] function have to do with this? That's already what recalling a palette does. Also, an off function is not necessary, as we have <Make Manual>.

Anyhow, let's not stray from the point of this thread: It doesn't seem possible to recall a palette and set a level for a fixture at the same time.

Since this does seem to be a bug, could someone from ETC address this in the future?

Actually, you cannot set a channel to more than one palette in the same command line.  If you are using the direct selects, pressing the record target you want is terminating the command line and pressing the next palette/preset that you want is reopening the command line and setting the new palette.  So, it isn't actually a correct statement that you can do this with referenced data but not intensity values.  You cannot (for example) enter a command line instruction that is [channel list] [focus palette] [5] [color palette] [2] [Enter].

Combining numeric instructions with referenced data recall is not undoable, but it is a bit of a slippery slope.  We do not prohibit using the @ button for setting non-intensity parameters.     Therefore, there is possibility for confusion about what the intent of the appended @ might be.

We do not consider this is bug.  This is currently considered a syntax extension that we have not yet decided that we want to do, given the possibilities for ambiguity.

:-)

a

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