Same deal; reduce the number of repeats for each command this increases the execution speed for each macro. It is much easier to do this in a global sense by using the Sonance IR library manager. Repeats are there to ensure that lazy receiving devices, or devices obscured by a lot of IR interference get a complete picture of what you are asking them to do. This is fine for example, a clear/exit command is discrete one time event so you can throw that at a device all day without any ill consequences, however number buttons are a different issue, in that a cable box might interpret each repeat as you simply pushing the button over an over.

So for example if you press the #1 and it has 5 repeats attached to it and you factor in the lag time of the receiving device, your #1 might come out as 111 or 11- the dash being a missed hit which the box does not fully understand. This is particularly frustrating in that if you press the button again, you might end up with –11 on some devices.

On the flip side, with some devices if you do not throw enough repeats at them, you can have all kinds of missed or half events. Some people have asked me, “well I learned the codes from the factory remote and that’s the number of repeats that the library manager came up with”. Keep in mind that many factors determine what the Library Manager is going to do with the codes that you throw at it, its kind of a best guess situation.

I have found that for most devices:

Volume+ or-: is best at no more than 1 repeat, with the sustain box checked

Channel+ or-: is best at no more than 1 repeat, with the sustain box checked

1234567890 : is best at no more than 0 or 1 repeat


When building complex macros, try to use as few repeats as possible, other wise the macro may take an unacceptable amount of time to accomplish its task.