Select your language
User Definable Keys

Channel Data UDKs

Recording Channel Data UDKs

In the same way you can record a lighting state onto a playback as a cue, lighting states can be recorded directly onto User Definable Keys (UDKs) as "Channel Data" UDKs. This allows you to record fixtures, with associated fade times, directly onto a UDK. First, set up the fixtures as required, in the same way as programming a cue. 

Then tap Record followed by tapping the UDK you wish to store your lighting state onto. UDKs will flash after tapping Record if they are empty, and will not light if there is something on them already.

Overwriteudk

Tapping a UDK that is already recorded, will give you the option to cancel, or overwrite it. The console will state the "User Defined Key x/y is already recorded", where x is the UDK page, and y is the UDK number.

Flx Faders Desktop

The Faders window will show you information about programmed channel data UDKs. It will display the UDK number, the fact it is a Channel Data UDK, and then a row of settings information.

Naming Channel Data UDKs

UDK’s which have been recorded can be named by pressing Name and then pressing the UDK button. An onscreen keyboard will appear for you to type in the required name. Press Enter to complete.

The name will then be displayed in the onscreen UDKs in the Faders window.

Updating Channel Data UDKs

If you need to make a change to a UDK you can update it. As with updating cues, it is a good idea to output your UDK, make your changes, and then save the update. You may therefore wish to configure the UDK button to be latch rather than flash, if it isn't already. See the UDK Settings section for more information.

Once set to latch, tap the UDK so that it is active and outputting, make your changes, tap Update, and then tap your UDK. Your manual values will be merged with the UDK.

Deleting Channel Data UDKs

To delete a UDK, tap Delete, and then tap the flashing button of the UDK you wish to Delete. You can then confirm by clicking Yes. Tapping the button of an unprogrammed UDK will display a message stating the UDK is not programmed.

For example:

Delete UDK1 Enter

Delete UDK <1>,

This deletes UDK 1.