This seems to be the issue:
Parity & Toggle Bits
A somewhat common problem is when a device (such as a cable box) will accept a learned code once but not twice in a row. For instance, you can enter the channel "1 - 2", but not "3 - 3". This is not a fault with your new remote, but rather a very hard to work with design employed by your equipment.
What happens is your original remote tacks on a "parity bit" (sometimes called a "toggle bit") to the end of each code. So, the first time it sends the code it follows up with a "0". The next time it ends with "1". The problem is that a learning remote can only learn or send the signal one way – the way it learned it. Your equipment, unfortunately, will not accept the code again unless it ends with a new parity bit or you send a different code to clear the memory buffer.
The most common example of equipment that uses this system is anything that employs the Philips RC5 or RC6 code format - such as Philips or Marantz products, or even Microsoft Media Center Edition remote controls. As the RC5 and RC6 implementation guidelines make parity bit checking optional, not all RC5/RC6 devices will respond the same way to non-alternating learned codes. Some may require parity bits at all times, some may only require it for certain commands (such as "power"), some may use the parity bit only for closely repeated commands (meaning you could send "3-3-3" quickly with the original remote but only slower using a learned code), while some ignore parity bits completely and show no noticable operational difference with or without.
The Philips Pronto is the only remote that I am aware of that can learn codes with alternating parity bits in the method required for several (not all) brands of equipment. If you have one that is not yet covered you can try tacking on a "do-nothing" code after each real one. So, your button for "3" would send the "3" code followed by another code to clear the buffer. What can that code be? Anything that the equipment senses as a real code but doesn’t affect operation. It may be next to impossible to find such a code.
If the brand is supported, most preprogrammed remotes will properly send parity bits. For example, database codes in the Home Theater Master MX-500 or MX-700) will work correctly with parity bits, but learned codes will not. For other universal remotes, there is not much you can do for this problem.
Is there a solution for this?