Palette by type, broken reference inconsistent

Well, there are few thoughts going on here.... so, the "R"s first.  This is an indication that you have manually overridden referenced data with absolute data.  So, in the first instance, you saw the "R" because you were modifying a channel/parameter(s)  that was (were)  currently in a palette.    In the second instance, you were replacing a palette with a new palette.... so no "R".  the "R" is significant, because if you update, you'll actually be modifying the palette itself.  UNLESS you update / make absolute.  When this command is entered, the "R" will be removed, as you will no longer be impacting any referenced data in the update action.

The + in the CP tile on the direct selects (when stored as a by-type palette) indicates that some channel involved in the palette is not using the default value, but has discrete data instead.  If you have modified a channel that was in a by-type palette, when you conduct the update, that data is stored as discrete data in the palette.  If you want the data to be stored "by type" you can append the "BY TYPE" button to the update command.    When this is done, the desk finds whatever the default channel is for that fixture type in the palette and stores the new color data there.    This means you can easily modify the default data for a palette without needing to remember what the default channel is.

If you modify data for a default channel, but do not append the "BY TYPE" command while updating, that channel will be stored with discrete data and the next numeric channel of the same type that was "tracking" the default channel data will become the new default channel.

If you end up with discrete data in a palette by mistake, you can go to blind for that palette, select the channel and [at] [Enter] it.  That will reset it to using default data instead of discrete data.

Hope that helps,

a

Well, there are few thoughts going on here.... so, the "R"s first.  This is an indication that you have manually overridden referenced data with absolute data.  So, in the first instance, you saw the "R" because you were modifying a channel/parameter(s)  that was (were)  currently in a palette.    In the second instance, you were replacing a palette with a new palette.... so no "R".  the "R" is significant, because if you update, you'll actually be modifying the palette itself.  UNLESS you update / make absolute.  When this command is entered, the "R" will be removed, as you will no longer be impacting any referenced data in the update action.

The + in the CP tile on the direct selects (when stored as a by-type palette) indicates that some channel involved in the palette is not using the default value, but has discrete data instead.  If you have modified a channel that was in a by-type palette, when you conduct the update, that data is stored as discrete data in the palette.  If you want the data to be stored "by type" you can append the "BY TYPE" button to the update command.    When this is done, the desk finds whatever the default channel is for that fixture type in the palette and stores the new color data there.    This means you can easily modify the default data for a palette without needing to remember what the default channel is.

If you modify data for a default channel, but do not append the "BY TYPE" command while updating, that channel will be stored with discrete data and the next numeric channel of the same type that was "tracking" the default channel data will become the new default channel.

If you end up with discrete data in a palette by mistake, you can go to blind for that palette, select the channel and [at] [Enter] it.  That will reset it to using default data instead of discrete data.

Hope that helps,

a

Anne, thanks for the explanations.  I believe what you are saying for the "R" is that it is only displayed for an override using absolute data.  So that because I did an override with referenced data no "R" will be displayed.  Correct?

And for the plus sign, again the default value in a By Type palette has been overridden by discrete data.  But isn't a different palette discrete data?  Or does discrete data really mean absolute data?  However it is defined, the fact is that one fixture of that type has different data stored than the others and there is no flag to remind the user of that fact in the case where the overriding value comes from a reference rather than absolute data.

Dale, to the first point, yes.  As to the second....

If you replace a palette with another palette, that has no impact on what is stored in the first palette - and no, we don't consider that discrete data.  It's simply a new reference.  Does that make any sense?   If you have discrete data within a By type palette, the only indication of that is the "+" sign on the direct select and the channel list in the associated palette list display.    And of course, when you look at the palette in blind, discrete data is displayed in white.

The + sign means nothing related to what the channels are currently doing.  It simply means that there are some channels within a by-type palette that have discrete data... some channels in that palette will not use the default channel data upon a recall. 

There are a few terms that might be useful:

Reference data - parameter data is drawn from a palette or preset.

Absolute data  - parameter data is drawn from numeric information entered on the keypad, via the encoders or from a tool such as the color picker.

Default data - parameter data is drawn from a by-type palette.  A "source" or "default" channel is stored, which identifies what the data should be for other channels of the same type.

Discrete data - parameter data is drawn from a by-type palette, but within that palette, that particular channel has been stored with different values from the "default" channel.

Does that help at all?

a