Hello.

I have a question regarding the setting of outputs when there is no command on a button.

With only a macro on a button, the properities dialog doesn't show the IRF-6 tab, so the output cannot be selected. When the button is pressed, all the outputs light up on the IRF-6. This is a problem for what I am trying to do, which is to control 2 TiVo's. I have been trying to avoid learning a second set of codes for the second TiVo and just use the IRF-6's natural capability to separate the two TiVo's into zones.

This isn't a problem when the there is a command on the key, but then, the macros don't seem to work right and the codes in the macro still go to all outputs. I had been using a nested sustain-dbl click in order to get the transport and cursor controls to live together. During testing, with only one TiVo plugged in, they worked great. But now that I see all the outputs lighting up, it's neat, but not what I want.

So, rather than taking the time to learn the second remote, I'm spending even more time writing about it and experimenting, trying to get it to work. Worse case, I have another scheme that I found in the files from the d/l section here that I could implement w/o macros.

Jeff

Jeff,

Use the macro editor and double click each command in the macro list you wish to amend. You can setup each command in the macro differently.

Rob

Rob,

Yes! I just finished figuring that one out. Looks like this won't be the way to go in the long run though b/c my plan in avoiding learning the second remote was to be able to tweak the macros on the primary TiVo and then just duplicate it, select all the buttons and change the output from the first TiVo to the second one. Unfortunately, the commands w/in the macro aren't affected by their button being selected. So this is as bad or worse than having to re-drag all the commands in from a second remote. Arghh.

I think I will go to the alternate approach of using the Guide button to move to an alternate page where the arrows act like cursors.

I also found that if I put the commands used in the macros on their own button in an unused frame, and then use these instead of pulling from the library allows the attributes of the buttons to be used instead of the default all-zone behavior.

Another question though: When using macros, do you put the default button command in the final "else" of your macro or on the button itself, or both? I'm still testing, but it seems like macro behavior is different if the command is in the macro than if it is on the button.

Jeff