I'm using the Pronto to control a distributed audio system including an Escient FP-1, an ADA XM Brick, a HD AM/FM Tuner and other components. Currently, the user must select a room on the pronto and then I can link the hard buttons for each of the d. audio devices to the particular zone to the volume +/- and mute macro for that zone. This get rather tedious for 8 zones and >4 sources.

I'm almost certain, there is no easy way to do this programatically at this point.

One item which would alleviate a lot of the redundancy would be to allow a device under a device or a device under a page and adding a "Use Parent Page Actions" check box to the Hard Button Properties menu, much like there is already a "Use System Page Actions" now.

Any thoughts/suggestions?

The method you are using with links at the moment is currently the only way.


Even if you had a parent device as you explain, wouldn't you still be creating 8 devices for 4 zones?

Well, if I have a "Parent" for the base page of each zone I would only have to assign the hard buttons once (in the Parent properties) rather than copying and pasting each device (which I still need to do) AND THEN assigning the hard buttons for each page within.

So, assigning hard buttons once per zone and telling the "children" pages/devices to "Use the Parent Page Actions" would be much less work on my part and be much less prone to errors.

What amp(s) are you using that you can control the volumes seperately by page?

FYI, regarding the Prone To Error. On the TSU9600, you can now have Special Actions in an Action List. This was not possible on the NG remotes. The practice that I followed on the NG remote as well as on the 9600 remote is as follows:

1. Create a new device.
2. Create a page in this device.
3. On this page, create a button for each hard button as well as the Device Action List (NG remotes).
4. On the Device Properties page, link each hard button to the button on the page you created.
5. Save this config as "NewDevice.xcf".

Now, whenever you need to add a new device, simply merge in this config.

Why? Because unlike hard buttons, soft buttons can be "Linked" with Alt+Shift+Drag. Makes it much quicker to wire together a config.

With this type of setup, it is much less important to "Use System Page Actions" as you can now open the page with all actions in use by your hard buttons and quickly tab or F7 to see all the actions without having to click each hard button in Device Properties.

whdigital: It's an ADA Suite 8100 (Eight Zone receiver with a built in Tuner): [Link: ada.net]

It's just a different command string (IR or Serial or IP or ADA bus) to turn on a zone, switch sources on a zone or control volume, etc.,. on a zone.

Lyndel: Thanks for the suggestion... I'll look into this method.

I follow Lyndel's method as well. My device template can be seen here. As you can see, each device in my configuration file uses this device template. The device template consists of one page called "Hard Buttons". While a simple page with plain buttons would have been sufficient I chose to have some fun and go with a graphical representation of the remote. The buttons on "Hard Buttons" page are where I make the hard button assignments for a given device. The hard button assignments on the "Device Properties->Hard Buttons" tab are in turn linked to the buttons on the "Hard Buttons" page as shown in the pic. This is a huge time saver as Lyndel points out. In any event, for those that would like a copy of my device template feel free to download it via this link. Enjoy!