I have programmed a macro that when I press and hold a device, it will jump to that device, and then switch to the appropriate input on the AVR.

I have
-Tivo
-Roko
-Dune Bluray player
-Widows Media Center PC
-Chromecast

The Macro only works with the Tivo and the Dune.

On the "TV" main page, the macro includes the direct input for the Zone 2 inputs on the AVR.

I have the AVR Zone 2 as a device, and when I have the device selected, all of the direct inputs work perfectly.

The macro uses the same IR code as the AVR device.

Why isn't this working? Even more odd, why is it working on two of the macros, but not the rest?

thanks for your help!
Here's a link to the CCP
[Link: dropbox.com]

Just for the heck of it I used the RECORD macro button the program the macro that didn't work.

It works. It's kind of a pain in the butt to do that, but now I think my wife can finally use the new remote.

Does anyone have any idea why it's not working as it should?

~Jay

Try the jumps after the IR

Can you post a screenshot of your Macro? Might have something to do with delays or location in the macro string of where you put the Jump (which I usually put at the end of the Macro string).

Thanks for the replies,

You can use the Dropbox link if you want to see exactly what I had.

For the two macros that worked (Dune an TiVo), the jump was first, then the ir command.

In the program that I linked, I went so far as to add the source ir command twice with a delay in between to try to make it work. It never did.

I'll attach a screen shot of the recorded Macro that works perfectly.

[URL=[Link: s248.photobucket.com]][IMG][/IMG][/URL]

When you do your testing is the AVR changing inputs?

I also notice the the AVR is set for IR and other devices are set for RF. Not knowing how you have the system setup this could be the problem. You are also using the front blaster. Is there a reason you are not using emmitters?

Your macro does not have a power on for the DVD and the Roku. Try inserting a home command to wake up the Roku and a play stop command for the DVD to power on.

Dave

Sometimes beginners drag or copy IR codes into the macro instead of recording as you call it. All the commands should show as aliases and not IR commands.

Hi Dave,
My system right now is in the process of an upgrade with a pending room remodel.

Some devices are out of site, and they depend on the blaster.
RF is not very good in my house, so I am in no rush to put it on everything.

But now that you mention it, the only devices that work are those that are not using RF, but ir exclusively.
Example - the Tivo and Dune are new devices, and use ir. the AVR is new and it uses ir. The macro works as it should.
The Roku, and PC depend on the ir blaster via RF, but the AVR is still using ir only.

Maybe there is a bug in the remote or software that causes the macro to run in either ir only or RF only, not a combination of the two.

Once the room has been remodeled, I plan to have everything in a cabinet, and likely have everything but the TV and projector using RF. I will have the cabinet built with glass doors just in case i get a wonky device that refuses to work with RF.

thanks,
~Jay

I don't understand what you are saying.

If I understand macros correctly, there are two ways to make a macro.

First way is the choose the ir command from the list in the IR database, and drag it into the macro.

Second way is to click on the red RECORD dot in the macro window and then start clicking buttons on the simulator. When I do that, the ir commands show up as an alias.

The second method is how I got it to work on the devices that previously did not work.

The First method worked for two of the devices.

thanks,
~Jay

When you drag a code from the ir database into a macro the program basically just sees that command as a ir code with no additional programming associated with it. At that point the remote will just spit out a infrared signal from its built in ir blaster.

Now when you record a macro and click on commands in the simulator you are basically copying all the additional programming set within that button. This can be as basic as the program knows to route that specific command to base station ID #4 emitter 3. Also if you had a macro programmed into a button you could alias that macro into another macro. For example, if I wanted to program a press and hold macro for a all zones on macro. First I would program a macro that would turn all zones to a specific source. Then on my macro for let's say listen to CD the press side of the macro I would just program the remote to play cd in the current zone I'm in. On the hold side of the macro you would just click on the all on button I created earlier. If you have a lot of sources you want to program this way it can save lots of time.

I hope this gives you a better understanding of why your macros didn't work the first way but did the second. And hopefully it gave you some ideas of other cool stuff you can do.

Insert at least .3 second delays between steps. Unlike RTI, URC doesn't automatically insert any delays. I would usually give between .5 and 1 second to be safe. Try that out and see if it helps.

If you need help with your programming, let me know.



Damon