Hi All
Newbie here, so forgive anything obvious that I'm asking about.
I've got a client who has the following config (so I'm using a template in the xcf file)

Yamaha RX-V1900 receiver
connects to

Samsung BluRay
Humax 3000THDR
Foxtel iQ2
Phillips flatscreen TV in their Alfresco
iPod dock
Samsumg Smart TV but only used as a monitor

TSU9400 on 7.3.3 firmware
RFX9400 (1 of) on ? firmware - need to c onfirm.

RFX9400 is hard wired via IR1 to back of the Av receiver
IR2 is off to Bluray and Foxtel using the IR emitters
IR3 is to Humax decoder (with second channel to nothing)

Problems I have:

Unable to find a Bluray player in Component list - am using the DVD component listing in Philips database

Cannot work out how to enter the IR channels in ProntoEdit - when I configure the functions as a macro, I choose IR1 to power on the AV receiver and select its input channel, but when I then go to power on the Blueray on IR2, it also sets the Av receiver to IR2:

Page is WATCH TV
BluRay button has actions:

Delay0.2s
Power on AV receiver (on IR1)
Delay 0.5s
Power On DVD player (on IR2)
Delay 0.2
Page Jump to PLEASE WAIT page
Page Jump to Bluray Menu (which is the play / FF/ REW buttons

Do I need to split the Power On's to 2 seperate actions as the actions only support one IR channel?

allagras,

The IR port is associated with the device (Component), not a macro step. You can change this port by clicking on the device in the device list. All commands for a given device use the same IR port.

Look carefully at the IR Library manager because you can add a new device to your library and learn the IR codes from your remote.

Use of the "Please Wait" screens is optional. It's a matter of personal style, I prefer not to use them. If you use them, distribute commands to the same device across multiple "Please Wait" screens. For example, after a POWER ON command one may need to wait a few seconds before issuing an Input select command to that device. The purpose of the "Please Wait" screens is to give the user something to watch and to show progress while waiting for commands to execute. In one extreme case I needed to wait 30 seconds.

Just a suggestion about PLEASE WAIT pages. I have a simple prontoscript that checks a system variable is not zero, and if not it shows a decrementing seconds counter on the WAIT page, as user feedback. Also, there is a "Skip" button on the page to set the counter to zero and return.

cosmicvoid,

I hate those "Please Wait" screens. I developed a command queue. This queue is passed from activity to activity. A command is pushed onto this queue with an execution delay. One can be assured that this command will be held, then executed -- no matter which screen is current. This makes the remote seem so much more responsive because you don't ever seem to be waiting. If I need to hold TV commands for ten seconds or so after POWER ON, I can immediately go to the cable page and set my channel while the pokey TV is waking up. When the TV is ready, its Input command is executed. "Please Wait" makes the remote seem slow. In my scheme, staring at a dark TV screen places the blame where it belongs.

Another plus to this scheme is that the operator cannot overrun the remote or controlled device. This is wonderful when dealing with slow cable boxes. One can quickly queue up a bunch of commands that might require the best part of a minute (or more) to execute. I am constantly overrunning cable boxes when using their native remote. Now, I can enter a channel number at light speed and move on while the commands are delivered to the box at a pace that it can digest. (And this "pace" might change with cable box firmware updates.)

Also, it is irksome if the system starts up and the previous Volume setting is too high for current conditions. With a "Please Wait", one is trapped at this excessive Volume until the "Please Wait" finishes because the Pronto buttons are locked out. With my Queue, the Volume buttons are always available.

Thanks to all
Worked it out, and took Buzz's advice and dropped the Please Wait
.
When I explained this to the client, he didn't realise the progress bar was just an image! He was quite happy to dump the please waits too - thanks for that tip.

Great Forum!

Grant