I'm working on my own personality-files for pearl 2004 but have a questions about RANGE, TABLES and MACROS.
What do all those numbers stand for?
TABLES:;
A color table for the colour wheel
PFTABLE "Color" -1 4 6
Open 1 0 0
What do all those numbers stand for?
MACROS
MACRO "LAMP ON" 1 1
data 0 e6
delay 1 50
data 0 23
What do all those numbers stand for?
RANGE
RANGE 8 ;Gobo 1
Thanks in advance for any help.
Regards, Bert.
personalities creation for pearl
Moderator: Moderators
-
powerdesign
- Posts: 4
- Joined: 28 Apr 2007, 13:10
Blimey!
PFTABES and MACROS are covered in the manual. I can't really explain fully any better than simply copy/paste!
It can be a little confusing so I'll concentrate on the specifics here and assume you read the manual in conjunction.
PFTABLE:
Preset focuses (palettes) can be pre-defined either assigned to buttons (ie. auto-focus when patching) or for access through the tables on LCD (originally intended for graphics tablet).
In the definition the first number defines the attribute the table is associated to. '-1' means not associated.
Following this are DMX channels to be defined based on the offset value used in the DMX definitions. In your example there are two DMX channels to be defined in the table and are whichever correspond to offsets 4 and 6. Therefore actually unlikely to be a definition for colour wheel unless there are two. Commonly a colour wheel table will have only the one DMX value. A colour table might have four channels (ie. wheel & CMY) which is probably the most useful application of a table (similarly for RGB LED fixtures).
The next lines contain the values. First number is associated button, followed by data in hex.
The Names will be displayed in attributes & tables view on LCD. This view is automatic (if exist) when you select relevant fixture followed by the appropriate attribute button. It can also be accessed manually in Program mode from the 'attributes and tables' softkey. This will present a menu where available tables are in inverted text.
When you are defining tables like this to be used from tables view (as opposed to being for automatic palette creation) you scroll through the defined values by wheel. Holding down [avo shift] while scrolling avoids selecting in-between colours. However, with the introduction of quick-keys it is no longer possible to see the table while doing this. A known conflict!
I must admit I am a little confused over the difference between using '-1' in the definition and within the table values themselves. Experiment!
PFTABLE definition must end with PEND
MACROS:
Definition line shows name followed by DMX values to be used - again based on offsets. Your example is invalid - you would not define the same channel twice.
Next lines are data to be sent in hex.
Delay values. From the manual:
Macros must end with MEND
RANGE:
These are exported from the D4 and are not always easy to recreate!
Basically the number is again the dmx offset for the attribute you want to define ranges. Here there can and must only be one value.
Following lines show the start and end values (in decimal!) that the associated text belongs to. Obviously the values should not overlap.
If you observe exported range lists you will see that there can be more complex definitions in the text field - commonly allowing a percentage to be displayed proportional to the 'range' defined.
Range tables are associated to 'intelligent' selection from quick key 1 (attribute display). Selecting 'raw' reverts to actual values if ranges have been defined.
Range table definition must end with REND.
Finally, range tables are the ONLY changes in a personality you can apply without repatch/loss of data. You can do this via system/utilities/update personality.
HTH. I'm going back to the sun....
PFTABES and MACROS are covered in the manual. I can't really explain fully any better than simply copy/paste!
It can be a little confusing so I'll concentrate on the specifics here and assume you read the manual in conjunction.
PFTABLE:
Preset focuses (palettes) can be pre-defined either assigned to buttons (ie. auto-focus when patching) or for access through the tables on LCD (originally intended for graphics tablet).
In the definition the first number defines the attribute the table is associated to. '-1' means not associated.
Following this are DMX channels to be defined based on the offset value used in the DMX definitions. In your example there are two DMX channels to be defined in the table and are whichever correspond to offsets 4 and 6. Therefore actually unlikely to be a definition for colour wheel unless there are two. Commonly a colour wheel table will have only the one DMX value. A colour table might have four channels (ie. wheel & CMY) which is probably the most useful application of a table (similarly for RGB LED fixtures).
The next lines contain the values. First number is associated button, followed by data in hex.
The Names will be displayed in attributes & tables view on LCD. This view is automatic (if exist) when you select relevant fixture followed by the appropriate attribute button. It can also be accessed manually in Program mode from the 'attributes and tables' softkey. This will present a menu where available tables are in inverted text.
When you are defining tables like this to be used from tables view (as opposed to being for automatic palette creation) you scroll through the defined values by wheel. Holding down [avo shift] while scrolling avoids selecting in-between colours. However, with the introduction of quick-keys it is no longer possible to see the table while doing this. A known conflict!
I must admit I am a little confused over the difference between using '-1' in the definition and within the table values themselves. Experiment!
PFTABLE definition must end with PEND
MACROS:
Definition line shows name followed by DMX values to be used - again based on offsets. Your example is invalid - you would not define the same channel twice.
Next lines are data to be sent in hex.
“data†that the following data will be passed to the instrument. Note that this MUST be in lower case and enclosed in double quotes.
Delay values. From the manual:
“delay†This optional statement defines that a delay time before running the next step. When used it must be followed by a 1. This field is for future use.
Time is the delay time in units of 0.1 seconds and is in hexadecimal.
3 seconds would be 2E
Macros must end with MEND
RANGE:
These are exported from the D4 and are not always easy to recreate!
Basically the number is again the dmx offset for the attribute you want to define ranges. Here there can and must only be one value.
Following lines show the start and end values (in decimal!) that the associated text belongs to. Obviously the values should not overlap.
If you observe exported range lists you will see that there can be more complex definitions in the text field - commonly allowing a percentage to be displayed proportional to the 'range' defined.
Range tables are associated to 'intelligent' selection from quick key 1 (attribute display). Selecting 'raw' reverts to actual values if ranges have been defined.
Range table definition must end with REND.
Finally, range tables are the ONLY changes in a personality you can apply without repatch/loss of data. You can do this via system/utilities/update personality.
HTH. I'm going back to the sun....
-
powerdesign
- Posts: 4
- Joined: 28 Apr 2007, 13:10
Who is online
Users browsing this forum: No registered users and 55 guests