Since this Dual Remote System was designed with the custom installers in mind, I'd like to start this thread with your initial opinions, questions and answers about the MX-700, SideKick (MX-200) and the MX Editor software.

No custom installers using the MX-700 yet, or checked out the software?

I purchased an MX-700 for myself, with thoughts of how to use it in installations. I see little use for the Sidekick in most cases. Maybe the right customer will want it, but that might be one out of ten. It might be better if they offered the MX-700 stand alone, or, if wanted, in the package.

Other then that I have been playing with the MX-700 on my home system all weekend. It was very easy to setup, and almost flawlessly learned all my IR codes. So far the experience was great.

I just picked up my 3-pack today and will be toying with it over the weekend. The software seems similar enough to Pronto Edit that it should not be a big deal to get the hang of.

MX Editor's IR database has been updated to vs. 1.44 (May 21, 2002) for Live Update.

Firmware and program remain the same.

... Greg :-)

Greg:

We just installed a system today with our first MX-700. My INITIAL impression is VERY positive. Here are my thoughts:

1) I can see a lot of my customers actually using the Sidekick. I seem to work with a lot of couples where one partner is a complete technophobe. I can overcome technophobes "fears" with a Crestron or AMX touchscreen, but a Pronto has its limitations in this regard. The Sidekick offers a great solution for the technophobe.
2) Programs MUCH faster than the Pronto, at least based on the way I do programming. And that was without ever referring to a manual.
3) Super easy to read with a great backlight.
4) Fits great in your hand.
5) Macros were pretty easy to program but I am not sure I like how it is done. You program your macros by pointing to other commands on the remote. That suggests to me that if the button that the macro is pointing to changes, so does the macro - not good. It also suggests that you have to have a button for each command you want in a macro, even if you don't need to have the individual button "shown". But you can "hide" pages (and therefore hide a button), so it shouldn't be a problem. I haven't read the manual yet so I could be wrong about these issues.
6) Like every other similar program I have used, it
lacks the ability to attach any notes to your programming. This can be done with Crestron and should be a requirement of all programming software, IMHO.
7) Overall, it seemed to work flawlessly. No problems uploading or downloading. I didn't discover any bugs (knock on wood). Did all of my programming with the built-in codes.
8) When you create a device (lets say an RCA satellite receiver) it automatically throws every command on the appropriate hard button and lists "extra" commands in the LCD window. Then you can easily delete commands you don't want in the LCD window as well as drag and drop them. Fantastic!
9) Takes a little bit long to download.
10) I predict a lot fewer failures of the MX-700 than the Pronto, IMHO. We have had a lot of Pronto failures.

Overall rating - 9 out of 10.
Of course this is how I often feel when I use a cool new product. I am sure that within another month or two I will have discovered all sorts of things I would like it to do better, LOL.

I don't want to turn this into a MX-700 versus Pronto debate but IMHO many customers find a Pronto hard to use (yes, even a well programmed one) and I think the MX-700 will be better in this regard. I am not selling any more Prontos now that I have this to sell and I will leave it at that.

p.s. Here is a quote from the first page of the small introduction brochure that comes with the unit - "Custom programming of a complex home theater is one of the most challenging tasks wihtin a home theater installation. It involves an intimate knowledge of how the components interact and exact details on the proper sequences of control. Only a Home Theater Master dealer has the requisite experience and training to quickly and effectively customize a remote control for true automated operation".

I thought it was nice they are trying to support us with this statement.





This message was edited by QQQ on 05/25/02 01:22.51.

why? chances are if you change equipment you will put the same commands in the same place. That way you won't need to change the macros, just because you upgraded some equipment.

Anthony:

Using the term "chances are" couldn't be more appropriate and that is why I don't like "switch pointers", because you are taking a BIG chance whenever you change a button that you could be screwing up numerous other commands unintentionally. UNLESS the program implementing "switch pointers" warns the user that changing a button that is being pointed to may inadvertantly change twenty other commands, I don't like it. Especially when you cannot attach notes to your programming as I mentioned in my "review".

I want to qualify one more time that I have not thoroughly studied the MX software yet so it might indeed warn someone for all I know. I am going to read the user manual in the coming week.

This message was edited by QQQ on 05/25/02 17:23.31.

Q, I have not tried the 700 or the editor (too busy). But it does sound like the way alias works on the Pronto. So please excuse me if I say something wrong. On the Pronto I have used alias a lot, and to be honest, I started doing that after having made a lot of mistakes that ended up giving me problems (deleting wrong buttons, moving buttons....) could you do something similar to what has been dubbed an alias.CCF on the 700? i.e. for every device you create a hidden page that contains the learnt code. This way you know there will not be any reason to change the function of a button (at least by mistake) and hen all the usable buttons become "macros" aliasing codes on the hidden pages.

Anthony:

Absolutely, I agree. That is how you could do it.

I’ve been waiting for this product (MX-700) to come out since November of 2001! I must say it was well worth the wait. I have used it to completely program my personal HT system over the weekend and will use it for my clients as well.

1.Power on commands for my Sony ES receiver didn’t learn at first. Then I turned of Auto Power. That fixed the power not learning. My biggest problem is that the Sony ES receiver has a 2-way remote that doesn’t work with anything except it’s own remote. Most commands did learn, but the only sound fields I could program were Cinema B and 2-Channel.
2.Some devices are listed by the remote name and others by the device title.
3.Limited downloads available for devices. This should improve with time.
4.No .mxd downloads (yet) on Remote Central. Please! Please!! Please!!!
5.Could use a Record hard button on next rev for PVR’s.
6.The On and Off buttons should be on the punch-through page as well. I kept shutting down individual components when I really needed to go the main menu, then to Off.
7.No real need for the Side Kick but will see how it goes with clients. Could make it a simple remote for another room like the Bedroom by hiding the pages on the main remote. Humm?
8.Must order 3 units to get a programming cable. Needs to be one in each package.
9.Much easier to program than any other software I’ve used.
10.W.A.F. is very high because it’s so easy to train anyone to use it.
11.Need more discrete commands!!
12.For jobs, I highly recommend learning each and every remote completely before starting to program your project as most devices will not be on the site yet.

All in all I give it a 9 (out of 10)! Thanks for delivering a product that works the first time!! No owners manual needed.

Guys! Please post your reviews in the User Reviews section!

Thanks!

... Greg :-)

Some people will love the SideKick. Some won't. I wasn't all that pumped about it until one of my grandchildren came over and wanted to watch TV, and use my 700. The SideKick was programmed that same day and it works great!


Isn't that what the custom installers want? ;-)


I'd like to see an LCD with a lighter background, both in the backlight mode and the non-backlight mode.

In non-backlight mode, it is harder to see in dim light and at an angle than the LCD on the MX-500. In backlight mode, the green should be lighter for more contrast between the black text and the background.


We've known that for while with the MX-500! :-)


I'm not a custom programmer, but I would think that in most cases, this is the way you would want it to be. Notice, I say "most" cases.


Nice feature. URC will see this post and perhaps we'll see it in an update down the road.


This is a good thing! :-)


Yes, I was very pleased when they finally implemented drag 'n' drop for the LCD buttons and the devices. This was one of the very last features to be added. Makes customizing the remote a breeze!


Huh? A two minute download when compared to all the time you've saved in programming the remote? ;-)


I certainly hope you are right!


I think this rating will hold up, especially after you've created MXD files of your most used components, and when a good-sized library of MXD files is available on this site.


Some will prefer the Pronto. Some will prefer the 700. But it is nice to have a capable button remote for those who aren't into touchscreens!


It's because they love you! ;-)

... Greg :-)

Another happy camper!


Eventually those 2-way Sony remotes won't be a problem after we get some CCF's converted over to MXD's and uploaded to this site.


And some of those codes listed under the remotes don't even reflect what is on the remote itself. The IR database needs a real overhaul.

But, again, that will be less of a problem as the library of MXD files grows.


You'll see hundreds of them in no time.


Actually, there was TWO last time I looked! :-)


A conscious decision was made not to have it on the body of the remote, since it is too easy to push for "technophobes" as QQQ calls them, and record over something they didn't want to lose. But, yes, the PVR people don't like the idea. I think that once they get used to having the REC on one of the lower LCD buttons, it will be a moot point.


Stop doing that! ;-) I'll have to think about that, but I don't see the use of having punch through for the ON and OFF buttons. Keep in mind that the MAIN page can be configured as a device itself, and not just a list of devices.


Bedroom use is one of the ideas behind the SideKick.


Marketing. Most custom installers will buy 3, and only need one cable.


As I said above, this is a good thing!


Yep! Same sentiments have been said about the MX-500. The ability to have a macro on any button makes the WAF even easier to achieve!


MXD files converted from CCF files will take care of that. Plus, URC will continue to update the database.


And then saving them down as an MXD file for use in your next job. You gotta love it!


It's still a good idea to read the software manual. It has some very good tips in it.

... Greg :-)

what I've found with the mxd files is that they're nice, but in order to get full functionality, I'd rather see mxf files...

the mxd files only import device commands...

the mxf files send along any macros that are programmed within a device, ie, 4 pages of favories on cable, satellite, etc. Using mxf files this way is essential to quick programming, especially if all your customers use the same cable and/or satellite systems, or if you set them all up with basically the same gear...

i've only done one 700/200 system so far, and every night, the customer tells his wife how much he loves me... heh!

Al
Katy, TX (near Houston)