Eric recommend to list the top ten improvements to URC software.

These are mine.

1. Input of hex into the mx software.
2. Ability to make a single button output either IR or RF.
3. Address the output of the single button listed above to a single IR out.
4. Ability to add more than three RFX1's to the MRF300
5. Import IR codes from the MX3000 to the MX850.
6. Import .pcf files to all MX software.

Mike

Sounding off, my most important issues (not necessarily in order of importance)

1. Direct entry of pronto-type discrete IR HEX codes
2. Resolving the occassional (frequent, in my case) "file corruption" issues that occur on the MX-700 thru MX-850 MXF files, when said file has been updated/saved multiple times (e.g., this is presumably the cause of errors I often see at the tail end of downloading an updated MXF to the remote, and causes the remote to lock up); see [Link: remotecentral.com] for more details on this.
3. Import/export macros
4. More intuitive "copy & paste" of IR codes/buttons within the MX editor
5. Ability to *copy* an IR code from one screen to another, rather than just create a shortcut/alias
6. Enhanced reliability of RF transmission (though this is probably more a remote thing, than software)
7. Having the MX editor's TEST IR function actually test the IR code assigned to a button in the *editor*, rather than in the remote (e.g., if I change an existing button to a different IR code in the software and then *test* it, the remote emits the IR code that was previously assigned to said button.

BTW, I'm a custom installer, and specialize in the MX700 thru MX-850 remotes

Inter-changeability from one verson of MX to the other. Have been doing 850's for a long time now. Started doing the 950's, only to find out I have to re-do most of what I have already done.

1) Ability to send a signal through the PC connected remote and clone/receive to/from MX-500 (have profile already but need to get the profile to PC somehow, add discrete codes from MX-700 database, then clone back to MX-500) and MX editor to support MX-500, at least basic features. Or perhaps get MX editor to IR clone over IR dongle of some kind.

2) Single line button option ie "WATCH DVD" is configured as one button/device rather having to do copies of the macro & a goto link to the real device.

3) Long filename description of macros ie like the TC1000 remote (call a macro say system power, but have a longer description that's seen in the MX editor ie "Turns TV, DVD, amp and projector on"

4) Open source firmware

5) Release a new remote firmware, if possible.

I believe you can do that now ... just rename the source device to "Watch DVD," associate the macro with this button, and it'll automagically execute macro and switch to DVD source control when it's pressed.


Excellent suggestion! I'll weigh in my vote here too!

- Remember the last device I chose for each code in the database. Right now, every time I dip into the code database I have to specify the model number and device type again. It should remember my last choice for that device and start from there.
- Direct hex entry.
- Ability to keep the 950's LCD screen on all the time (without the backlight).
- Allow downloaded updates to the MX-950 without rebooting the remote afterwards.
- User notes for individual keys that only show up in the editor.
- Combine the software. The 850 and 950 should be handled by a single program. They have very similar user interfaces, unlike the 3000 which probably needs to continue having its own editor.
- Easier moving of keys/codes between different models of URC remotes (700/850/950).
- Ability to import whole devices from other models (950 imports a device from a 700, for example).
- A more straightforward way of plucking codes out of the database and putting them on various keys. The 950 editor is a big step forward here, but it still has a way to go so that it doesn't require 65 clicks to get a key code.
- Publish the file format specifications. This will allow others to write add-on software, without the exposure (and questions) releasing the source code would cause. If you don't want to do that, you could license it with a small fee and a standard non-disclosure agreement to keep it out of the public domain.

I'm an end user, with two MX500s, a 700, an 850, and a 950. I also have an R7 and a URC-100 that I've been playing around with recently. (Okay, so I'm a nutty, remote-oriented end-user. Who else would hang out on this forum? ;-) )

I'd like to see the improvements implemented newest to oldest, so the 950 first, then 850, then 700.

The software and hardware is very, very good. Markedly better than the early days. It is very nice to see how far it has come in such a short period of time. Kudos to you and your engineering team! Hope you all are all having a good holiday, too.

Sean

Here are a few

1. Importing Hex codes
2. 1 program for all remotes and abilty to have multiple remotes open at once..2 850's and a 950, or a 950 and a 3000
3. ability to import a single IR code into a macro without having to have the code hidden on another page on the remote
4. more reliable RF....

Sean,

Just to clarify, the 850 and 950 aren't even close to similar. The 950 is essentially a 3000 crammed into a smaller package without the high-end options and color screen. 950 and 3000 are Windows CE devices.

I love this thread. How about identifying which remote control you would like to see the improvements to. I'd also like to know whether you are an end user or a custom installer.

Best Regards,

-Eric

Eric Johnson
VP of Technology
Universal Remote Control, Inc.

I believe you can do that now ... just rename the source device to "Watch DVD," associate the macro with this button, and it'll automagically execute macro and switch to DVD source control when it's pressed.

hmm don't think you undertand- If you have "Watch" which is empty device page, except for macro on the button with IR commands then eventually a goto "DVD"
and the "DVD" which is your real device.

You still have to do macros and goto link on Watch. I guess wasting devices for every "Watch" is a shame either way, but I find it easier to use. Although I would like MX-500 clone feature on the top of my want list, the one line button feature is a much less desireable feature.

6) Oh request to shut off the LCD screen perhaps after preset time ie 3 hours, and switches on when button is pressed. I noticed some of the pixels on the LCD are worn, so now when I finish with the remote I set it to FAV page (which is empty)

7) Description for Device names only seen in MX Editor, I have several "Watch" "Use" and "HIFI" devices solely for single line approach, also identically named devices for different uses (ie DVD for films with PT volume to AV processor, but another activity also called DVD but PT volume to 2 channel pre-amp) so whilst editing and linking/PT and moving around things gets a bit confusing since some thing like goto won't actually show up just which "WATCH" is which, if you have loads of them (usually I rename the page to something that sticks out ie "EEEE" until I've finished with it, then rename back..it would be great if to the right of the device some colour text can be added to aid the user, and whenever PT or goto linked option it appears. See here pic one for what I'd like and pic two to confuse use with multiple identical named devices.

On the difference between the 850 and 950 -- point taken. Behind the scenes they are very different hardware and firmware-wise. But, functionally they are similar enough to share an editor, or at least the user interface of the editor, even if the back-end code is different for the two of them. The 3000 is totally different both from a hardware and UI standpoint because of its graphical touchscreen.

I'll edit my original post with the additional info Eric requested.

Sean

Also, the ability to insert one IR Command on one page, when that page is being used for a different device. (On the 850). For Example, using the cable box page, but also having a button that wil turn the TV off. You only do this now with macro or alias pointing to that command on a different page, which has to be hidden.

Mike

As simple as this might be, in the MX 3000 editor I'd like to be able to save cutom grid layouts, ie PAGE > GRID > DISPLAY GRID. I'd like to be able to customize those, then save them so they aren't lost the next time I open it.