Absolute vs. Discrete

can you be a bit more specific about the situation?

absolute data means no references. so you record values like "Pan = 236" into a cue, rather than "go look up the Pan value in a Palette called Sofa"

discrete data means usually "although there is a general information, this channel gets individual data". this can be in a By Type palette, where all the lights get the same data except the ones with discrete data. or about timing: although there is general timing (i.e. cue timing), one channel (or one parameter of one channel) gets individual timing information (marked by a + next to the respective timing pill in the PSD).

After further reflection, it appears there are 2 types of data, referenced and unreferenced.  Discrete data is unreferenced and absolute data can be a type of discrete data.  Your example of "Pan=236" is both discrete and absolute.  Both types are input (or is it inputted?) by the operator through the Ion command structure.  However referenced data that has lost its reference point becomes absolute through the Ion software with no action taken by the operator, yet it also becomes discrete by the fact it's unreferenced.  Seems to me they're pretty much synonymous.

ahh... not really.  Absolute data always refers to information that is entered for a parameter directly via the command line or via the encoders.  It is also possible to create absolute data for parameters that are currently in a referenced state by selecting channels/parameters and entering "make absolute."  When data that was referenced via a palette or preset is modified, an "R" is provided in superscript to indicate a reference has been overridden.  Via update, the user has the choice to "resync" to the reference or to break the reference.  I'm not clear what you mean by "referenced data that has lost is reference point becomes absolute through the software with no action taken b the operator."  hmmmm... can you describe what you mean by that?  References cannot be lost unless the programmer tells them to be lost. 

We use "discrete" for two conditions.  A)  channel/parameter level timing.  This is called discrete time.  Channels will no longer follow cue timing.  B)  Discrete data in a by-type palette.  Parameters with discrete data in a by-type palette will no longer follow the "source channel", but use their own data instead.  

So these things are, in fact, quite different.

Does that help at all?

Thanks,

a

Ok, good. This helps.  Thanks.  What I meant about data losing its reference was in the case, for example, when a palette being referred to is deleted (by the operator), then the data referring to it becomes absolute with no further action (by the board op).  No need to "make absolute."

This came up as I was trying to understand by type palettes.  The manual states (underlining is mine):

If {By Type} is used when recording, the lowest number channel of each fixture type will be the default channel. Generally, when storing by type palettes, you will want only one channel of each fixture type in use. Any additional channels in that fixture type will be recorded with discrete data.

• [1] [Thru] [5] [Record] [Int Palette] [1] {By Type} [Enter] - Channels 1 through 5 are saved to Intensity Palette 1. Channels 1 through 5 are of the same fixture type. Channel 1 will be the default channel and channels 2 through 5 will be saved with discrete data.

This reads like there's no reference to the default channel for the other channels but that data must be entered for them.  I'm good with discrete timing but the by type has me confused.  I think of "discrete" as something which stands alone as a seperate entity.

A good example would be 5 cheap LED fixtures and by-type Color Palettes. In theory, you could just record the By-Type palette with just one fixture, and the others would match - for example [1] [Record] [Color Palette] [1] {By Type} [Enter].

If you have to tweak a couple of other fixtures to get the same color, though, then you'd want to have some discrete data for those channels: [1] [Thru] [3][Record] [Color Palette] [1] {By Type} [Enter]. Channel 1 would be the leader (lowest number), 2 and 3 would have discrete data. 4 and 5 would track the value of 1.

You can, of course, go into a Blind editor for CP1 and change which is the leader (using the {By Type} softkey, which are followers (using [At] [Enter]), and which are rebels (using the {Discrete} soft key).

Hope that helps!
Luke 

PS You might want to look at tutorial 25 of the Tea Break Tutorials series:
http://www.etcconnect.com/support.tutorialseries.aspx?seriesId=15

I think I've got it now.  The lowest numbered fixture in a By Type palette becomes the default source of data for the others.  Change its value and the others follow.  But the others may each have their values changed individually without changing the default value.  They are deemed as having discrete data in that, while initially the value equals the default, each fixture's data may be changed without affecting any other fixture.

I think I've got it now.  The lowest numbered fixture in a By Type palette becomes the default source of data for the others.  Change its value and the others follow.  But the others may each have their values changed individually without changing the default value.  They are deemed as having discrete data in that, while initially the value equals the default, each fixture's data may be changed without affecting any other fixture.