You might have something there, it's definitely logical. It is also obviously device independent as I am using macros with other devices and everythings works fine. I will give the forum an update when I hear back from the Nevo support people.

i think the above would also explain the problems people have with some commands being sparatic. ie: by xbox 360 A,B,C,D and guide buttons are VERY sparatic and work about %75 of the time when used from the Touchscreen. however when programmed onto hard keys they work every time as i can hold the button down, where as on the TS it seems to make no difference how long you press.

UPDATE -- First let me state what a large help the Nevo develope team was in helping me resolve this problem. I had close to a dozen emails traded with them of which all were responded to very promptly. The simple solution to this complex problem was to re-learn the digit codes from the original remote, this time depressing the designated remote key very briefly, as briefly as possible yet enough to have Nevo read it succesfully. I relunctantly performed this activity not understanding how the individually entered digits from a keypad page could work flawlessly and yet the action sequence using the same learned IR code would not. After performing this procedure, my button action sequences for all the channels also now work flawlessly. :)

Maybe this forum is where they get their info...no respect... ;)

Interesting! Yes, button learns are a huge variable. I also agree the shortest possible press of the target key is indeed the best way to learn. This has been an issue on the Pronto products for a long time. I also wish in Ver 1.5, they would allow you to see the learned hex codes, immediatley after the learn function, so someone with knowledge could look at them and see they are either:

1) Poorly formatted (learning problem)
2) Dirty (learning problem caused by excessive repeats (holding target ket too long), etc.
3) Dirty learns caused by other environmental issues such has immediate, harsh lighting close to the two remotes, possibly fluorescent lighting, etc.

I understand their need to protective intellectual property (their internal DB codes) but they should show a learned code in Hex,since it is not part of their intellectual property.

I will mention this to them in an email, as we are part of their beta software team.

Dave