I'm a Pronto TSU7000 user, and have been for about 3 years now. I think I've finally gotten to the point where I've accepted the fact that I just don't want the touch screen anymore. I guess I kept telling myself that I would eventually learn to love the touchscreen, but the bottom line is, as much as I love being able to make the remote look and perform exactly how I want, the touchscreen thing just wasn't working for me.

So which is why I'm here. I started researching the higher end "hard button" options out there, and came across the MX-810. It seems to be exactly what I'm looking for. First of all, RF is an absolute must for me, as all of my equipment is behind a wall, and I like the sound of this "narrow band" stuff. I periodically would have issues with my Pronto not recognizing a button press, or it being delayed. I've read through all of the complaints on these forums about ProWizard software of the MX-810. I'm not an installer, so frankly that isn't as important to me - as long as I can get it to do what I need it to do, even if it means extra tedious work on my part. I just want to make sure of a few things. I need everything to be set up "activity-based". So I assume I will be able to set up a custom macro button on the color screen section to, for example, turn on the TV, preamp & DVR, and take me to the appropriate "page". Then, to turn everything off (regardless of the "activity" I'm in), I would simply hit the 'Off' button? So in this case, what purpose does the "On" button serve? I'm assuming (hoping) that I wouldn't need to first push the 'On' button, and then push the custom "Watch TV" button?

I've also considered the MX-980, but frankly I like the layout of the MX-810 a lot better. I figure I could sell my Pronto with the RF receiver for close to $500, so either would be in my budget. The one thing I don't like about the 810 is that it doesn't have a charging cradle? What's up with that? I suppose that's not a deal breaker for me but it also doesn't make any sense.

Any advice to a potential touchscreen fence-jumper?

With the 810, you first create devices - tv, dvd, reciever. Then you create activity macros using those devices. When you create an activity, you tell the remote which device primarily controls the component - then it jumps to that device.


Yes, you can tell the remote to power down all the equipment by pushing "Off." In the devices, the On button is the power button for the device. In the activities, the On button runs the macro in upper left corner. After selecting an activity, the On button sends the macro again. You do not have to hit the On button before selecting an activity.


The 980 would give you much greater flexibility in programming, but mostly for the more complicated systems. As far as programming, the 7500 is more like the 980. But that may be over-kill for some systems. If you have discretes for all components, either will do the job of running macros to turn on a few components and and set the inputs. If you need to do more complicated macros with variables, etc, then you may look at the 980. But, for a straight-forward 1 room system, the 810 will work great. I have an 810, coupled with an MRF-350, controlling 5 components that is more than adequate.

As for the charging craddle, it hasn't been an issue for me personally. The cord simply plugs into the bottom of the remote. I get around 1 week per charge, so the remote isn't plugged in all that often.

Thanks for the info dsp81. I ended up ordering an MX-810 with the MRF-350. I seriously considered the MX-980, but the bottom line is I liked the look/feel of the 810 better, I like having the record button, and I much prefer the activities/devices logic as opposed to watch/listen. The only thing in favor of the 980 (besides the software) in my eyes is the docking station. I realize the software is a deal-breaker for a lot of people, but as a non-installer who will basically be programming the thing once and leaving it be, I'm willing to work through the frustration if it means I'll have a better remote (for me) in the end.