Custom Controls
A custom control is a series of commands, or
button presses, that are recorded together into
a single macro. When you run that custom
control, the switcher runs all the commands and
button pressed that were recorded in the macro.
This allows you to simplify complex sequences
of commands into simple button presses. For
example, you can create a custom control that
will recall a camera shot to preview, add a lower
third, and then transition the background and
key on-air.
The switcher supports up to 2304 custom
controls.
Working With Custom Controls
• ALL+ALL Reset — Including an All+All reset
in a custom control with other events may
result in unexpected results. If you need to
have an All+All reset in a custom control, it
should be either the only or last event in the
custom control. Alternatively, you can
perform the All+All and then store that state
to a memory. This allows you to recall that
memory as part of the custom control instead
of the All+All.
• Attached CC Ignored — If you include a
button in a custom control that has another
custom control attached to it, the command
to run the second custom control is ignored
when the initial custom control is run. This
does not apply to actual custom control
buttons.
• Auto Recall — If you are including a memory
recall in the custom control, you must ensure
the Auto Recall settings are the same as when
the memory was stored. This ensures a
consistent output.
• Correct Source — A custom control that
selects a source on an ME will select the
correct source when a different bus map is
used, only if the original bus map still exists
on the switcher.
• Bus Maps — A custom control can be used
to assign a different bus map to a bus. Use
the Assign Panel Bus Maps menu (Press
HOME
>
Setup
>
Personality
>
Bus Maps
>
More
>
Assign Maps
) to assign a bus map to
a bus and record the event in the custom
control.
• Button Presses Only — For non crosspoint
buttons, a custom control only records that
a specific button was pressed, and does not
record the state that the button was in. For
example, if you press the TIME CLOCK button
on the Preview Overlay module while
recording a custom control, the custom
control will only record that the button was
pressed. If you run the custom control
immediately after recording it, TIME CLOCK
is turned off.
• CC Hold — You can insert a Custom Control
Hold command into a custom control that
will hold the custom control at a specific
point until the continue command is
received. The custom control is continued by
either pressing the custom control button
again, or by a GPI Input trigger.
• CC RECORDING — When you are recording
a custom control, the message
CC RECORDING
is shown on the Main Menu.
• CC Size — The size of the selected custom
control is shown next to the name, in the
Selected field on the left of the menu (xx/yy
bytes) on the Custom Control Menu. The first
number (xx) is the size of the macro, and the
second is the size of all the macros in the
selected bank (yy).
• Fader Isn't Recorded — To program a
custom control that will recall a memory and
then perform a transition, you must recall
the memory on the ME you want to perform
the transition on, then use the Cut or Auto
Trans buttons to perform the transition. A
custom control cannot record the movement
of a fader.
• Looping CC — You can create a Looping
Custom Control by inserting a Loop CC event
into the custom control.
• Menu Navigation — You can use a custom
control to navigate to a specific menu either
by using the Go To Menu event, or by
navigating to the menu when recording the
custom control. Not all menus support this
feature.
• ME Permissions — You can create a custom
control that will affect an ME that is not
assigned to your control panel by creating
the custom control on a control panel that
does have the ME assigned to it.
• Pauses Needed — A custom control will not
automatically compensate for the time a
memory recall or transition will require to
complete. In these cases, you must insert a
Ultrix Acuity Operation Manual (v10.1) — Custom Controls • 67