A Composite Example - One for All EXTENDER A1 FOR URC-7780 Instructions Manual

To illustrate how you do this, suppose you want to put a global Long Key Press on button A. First create
a Long Key Press on button A for any device (say device 2 for this illustration), with the desired actions.
Then create a macro on key A with macro keys
Now if you press key A with Device 2 selected, the original Long Key Press will be found first and acted
upon. If you press key A with any other device selected, the macro will be found, key A will be replaced
in the keystroke queue by X_DEV2, A, the X_DEV2 will switch the active device to Device 2, the
(second) key A will then be acted upon with Device 2 selected and the Long Key Press will again be
found and acted upon.
Note that provided a key bound to a Long or Double Key Press is the last keystroke in a macro, the
Long/Short or Double/Single selection will apply to the macro bound key, even if the Long or Double
Key Press is bound to a different key. In our illustration we could have put the Long Key Press on a
phantom key and put that key into the macro instead of key A. It would still be a long or short keypress
of key A, the key bound to the macro, that would determine the function performed.
I have used this ability as follows. In section 8 there was an example of how key A could be set to turn
on both the currently selected device and the TV. But key A is not a natural power switch. I want to use
the Power button, with a short keypress to turn on the selected device and a long keypress to turn on both
it and the TV. I first set an LKP for a phantom key on Device 1:
Dev1 Phantom1 = LKP, Duration 4,
I then created a macro on the Power button:
Power = X_DEV1, Phantom1.
The X_CANCEL in the LKP ensures that the XShift-Power acts with the currently selected device. Since
XShift-Power is not bound, shift cloaking operates to perform the power button action without causing
recursion.
As a refinement, I do not want a long keypress to act in this way when the selected device is Device 1, in
case it turns the TV first on, then off. So I created the key move described in section 4.1 that maps
Device 1 Power to itself. When the selected device is Device 1, this is found before the macro and so pre-
empts the macro action.
Any Special Protocol can be given a global action in this way.

10.9 A Composite Example

Here is an example from my own setup that illustrates a combination of several Special Protocols. I have
an Onkyo TX-SR606 AV Receiver that has two zones. The original remote has dedicated buttons to
switch it between controlling Zone 1 and Zone 2. I wanted to emulate this on my URC-7781, and in
addition have a short keypress of the digit buttons acting as the digits of the original remote, but a long
keypress of buttons 1-9 acting as input selection keys for the nine devices of the receiver for the current
zone.
I have created two devices in Remote Master for the two zones, with setup codes 2000 for Zone 1 and
2001 for Zone 2. Code 2000 is assigned to the RCV device, which is Device 3. Code 2001 is not
assigned to any device. In both codes the digit buttons are bound to the digit functions of the original
remote. The device selection functions of the original remote are not assigned to any buttons in these
setup codes.
To begin, I created the 'subroutines' I would need, assigning functions to phantom keys. I first created 18
key moves, on X-Shift/1-9 for each of devices 1 and 2. These are being used as phantom keys – I have
disabled keypad access to X-Shift as described in section 7.5. The key moves on Device 1 are assigned to
X_DEV2, A.
Short = X_CANCEL, XShift-Power,
Long = X_CANCEL, XShift-Power, X_DEV1, XShift-Power
19