MX700 Remote - software "live update" behavior?

[netarc]

So I _finally_ got around to programming my MX700 remote last night (ahem ... it's only been, what, ~2yrs - funny thing is I've been programming clients' remotes right&left, just never seemed to find the time to do my own!).

Have a question re: the MX-Editor software. The Parasound docs/website admonish one to only use the Halo-specific version of the software to program the Halo's MX700 remote ... fair 'nuff. After (re)installing this version on a new system I ran LiveUpdate - naturally it found lots to update. However, upon update completion and restarting the MX-Editor app, I found that a) it had the *same* version (help/about...) as before the update, and b) the IR d/b seemed the same as well ... certainly, it didn't have a great many devices that the "standard" Universal Remote MX-Editor did. Has anyone else experience the like, or does liveupdate work ok for you?

I ended up programming my Halo MX700 using the standard (non-Halo) MX-Editor, because I wanted the remote to have the newest firmware and also wanted access to some addt'l devices in the latest IR databases. I just downloaded the remote's config into MX-Editor (to retain all Halo functions), and left the "power" for all devices swapped (left-to-right). Anyone see anyone potential issues with this method?

[bhuskins]

Power commands getting swapped is the only issue. As long as you keep that straight you'll be good to go. I've always used the MX-700 software from Universal and not the Parasound version, but I forget about the power commands 75% of the time and kick myself once I test the remote.

Why the upgrade consideration? Just curious.

Brent Huskins
Media Design
HTGuide Sponsor

[netarc]

Why the upgrade consideration? Just curious.

Found a sweet deal I couldn't resist An ancillary reason, though, is that I use my home theater/living room as a demo room for potential clients, and the C1 is just rather more impressive than the C2...

[Chris D]

Netarc, you experienced the same Live Update problem after the DPLIIx update that I also had. I created a thread about it here in Club Parasound a month or so ago... just search back a bit. Basically, I used a version of Halo MXEditor's installer pre-DPLIIx update and applied the discrete codes. The brand new one currently posted on the Parasound website is having the same LU problem that you and I both ran into.

[netarc]

Netarc, you experienced the same Live Update problem after the DPLIIx update that I also had. I created a thread about it here in Club Parasound a month or so ago... just search back a bit. Basically, I used a version of Halo MXEditor's installer pre-DPLIIx update and applied the discrete codes. The brand new one currently posted on the Parasound website is having the same LU problem that you and I both ran into.

Hey, Chris ... yah, funny thing I did chance across your thread a few pages back (just after posting this). It's not quite the same issue, though - I was attempting to use LiveUpdate just after a (clean) install of the Parasound-specific MXEditor, and hadn't installed the DPLIIx update ... hmmm, or is said update already wrapped up in the v2 MXEditor that's currently posted on Parasound's site?

[Chris D]

Right... the issue is that some people are experiencing Live Update problems with the new MXEditor that is currently posted on the Parasound website, both the standalone file and the one packaged with the DPLIIx update. This new file came out at the same time as the DPLIIx update.

Some people may be using the new MXEditor install file without problems, although I haven't heard of any yet. I'm sure they're out there.