My findings are very similar to Greg's. If I'm using it continually it seems to have less failures. I have been noticing some fairly consistent button press failures when controlling my Tivo HR10-250. When I'm "FF" I hit "Play" and about 70% of the time play doesn't register and requires a second button press.

I'm not yet sure if it's an actual button press failure or an IR issue with the Tivo. I've noticed this to be more of an issue since my Tivo was updated to the latest firmware version 6.3a. But since the beta releases for the MX-900 came out about the same time it's hard to tell which device is at fault.

I will need to pay closer attention to the remote when the button press fails. But since I will no longer be using Tivo as of this Friday I may not be able make that determination. I will have to try and duplicate the problem when I get my Motorola 6412 cable box.

Mitch, see this post for discreet power macros for the Motorola 6412: [Link: remotecentral.com]

Mitch: They are selling the 6416 up here, which has 160 GB HD instead of 120. Can you wait until they come out in your area? Or would you be able to upgrade for nothing when they do? Just a heads up.

Since I have an earlier non-updated version of the editor, is that why I have fewer (basically NO) problems???

I'm guessing the answer is yes. IIRC, my MX-900 used to work perfectly until I updated the software/firmware. It looks like URC inadvertantly did something to screw it up.

Thanks for the link. I actually found your link last week when I was searching for discrete codes on the Motorola 6412. I'm definitely going to use them.

Greg,


Thanks for the heads up on the 6416. Unfortunately they don't have it available here yet and don't seem very willing to tell me what the next upgrade will be. I guess it will have to do until something else becomes available.

I've been using my MX-900 tonight and noticed that even with the new firmware it misses a button press every now and then. Seems to happen more often after I haven't used it for awhile, and on the second (not first) button press.

Definitely more work needs to be done to get it right.

IMHO, there is no reason to ever turn off the Motorola 6412. In fact, I highly recommend leaving it on all the time. For some reason, if the box is off and it starts recording something, you can't get any sound when you turn the box back on. This is a well known bug, and quite annoying to say the least.

This is for anyone at URC or anyone who has access to them...

Since the fix is taking longer than expected and the beta updates are only going to a few people, would it be possible to release an interim update which is simply a rollback of the firmware to before this all happened?

I like being able to turn the device on and off.

My macro deals with the mute problem. The reason the device mutes automatically is so as not to wake you up in the middle of the night when it starts to record "Real Sex".

Been using my MX-900 more tonight. Its failing sometimes on the first button press after I haven't used it for awhile.

You know what, it fails pretty randomly, although less than it used to. Not particularly on the first or second press after all.

A new beta was released today. Version 1.10.092b. I just downloaded it and I've only had one button press failure out of about 75 presses. It might just have been the way I pressed it. It was a page button and since those are so skinny it may have just been the way I pressed it.

However, a new issue has cropped up with the latest beta. Press and Hold macros have failed at least 4 times. My "Before" macro executes a series of commands and my "After" macro executes a 1 second press and hold "GOTO PAGE" macro. The "After" macro fails to execute. When I press the button the LCD screen DOES highlight the text next to the button and stays highlighted until I release it which then executes the before macro.

Looks like they fixed one thing at the expense of breaking something else. I'll do more testing this weekend and post my findings.

More work still needs to be done.

Please let us know what you find. I have no problems with the press and hold macros, I do a 1 second press and hold on each device to jump to the device page without executing the device macro.

I then created a new file with 5 press and hold macros (all set to different times) and all work perfectly. The only way it doesn't do the after state is if I have it set to 5 seconds and I only hold it for 4 seconds, then it does the before macro just as it should.

I am interested in what you find please let us know.