I mailed this to Mitch at RTI... but here are a couple of things I would like to see...

A few programming/hardware suggestions I would love...

(1) Problem... in a multi-zone environment... you may want to control the DVD player from several differently configured rooms... however, using the "standard" DVD player screen, you are not provided needed conditional statements for things like volume control. That is, I need to create separate screens for the SAME DVD player just because I want to have the volume control buttons control a different volume control on a different unit, or a different path on the same pre-amp. Same issue with several other buttons (Power, Menu, etc.).
Solution... obviously there are several options here... the BEST (I think) would be to have a couple of "state" variables which can be assigned and accessed from within your macro language. That way, I could set a state variable to "LivingRoom" when the remote is accessing controls for the Living Room zone. I could then use the single "standard" DVD player screen and put a macro on the volume control buttons which had a conditional statement allowing for different commands be sent (to different components... and different routes) depending on the value of this state variable. Thus I could create just one screen for the DVD player... instead of the one screen for each zone as required now (I think).

(2) The ability to assign a Command Code to a different button from within a macro. That would solve Problem #1... and allow for some nice programming features... I haven't checked if you can have a page-link and a command-code assigned to the same button, but if you could... you could have a button for Living Room, which assigned the volume control command-codes dynamically to the "stock" DVD screen, based on the individual configuration for the living room.

(3) The ability to create a button link to a specific page of a screen... I'm not sure on terminology here... but it would be nice to have a "main menu" for each page... that would click to the specific portion of the screen that the user needs... rather than force them to scroll through all the options. This is based on the assumption that additional screens take up more memory than additional pages of the same screen... this would be nice to know too... a basic memory usage list, indicating whether a screen or a page on a screen take more memory, the same, etc.

(4) An RS-232 confirmation/failure string test in the IRF-6. That is, as part of the programming in the T2, send not only the ASCII control string... but send the confirmation and failure string... with an optional ASCII code response. Have the IRF-6 check the response, if success... it continues... if failure... it sends the ASCII code response. I know... requires hardware programming in the IRF-6.

(5) A wish list item... Transport controls would be nice.

(6) A wish list item... would be to be able to put in hardware in the IRF-6 the ability to do some very basic functions, and allow the the remote to trigger those functions. Fundamentally, they should all be confirmation or sync functions. That is have an option to tell the remote to tell the IRF-6 to continue sending the Power On button until the "Power dongle" indicates the power is on. This would be a "functional" yet dumb replacement of the non-bi-directional nature of the RF remote function. If this was done via a macro... you could have the IRF-6 buffer subsequent commands until the item was properly sync'd. Along the same lines, you could solve the issue with "toggling power commands"... by having a function in hardware in the IRF-6... that sent the power command, waited 0.2s for power up confirmation, then resent if confirmation was not found. Again, accessible from a macro on the T2, this would allow to sync up with these devices. There are a couple of other interesting permutations here... but since hardware programming is expensive this would be my most favorite.

Cliff