I'm currently beta testing the CCF converter addition to MX Editor and it looks very, very promising.

I just got it this afternoon. One thing I HAVE to say, as a beta tester, that for the first eval I got, it opened a bunch of CCF's FIRST TIME! with no probs. You've got to love that.

Anyway, I just thought I'd let you know that it is definitely being worked on and is in the late stages of development from what I can see so far and it is looking good.

... Greg

Greg,

That's terrific news! Thanks for the update :)

David
www.BlueDo.com

Greg, don't know if this goes against any none disclosure agreement, but
a) does it convert a whole CCF
b) can it convert a single code (i.e. paste the code in the box and you get the MX-700 code in your remote)
c) do you have a choice in what buttons/ir codes are converted

Greg, can you give us a sense of how this works when we want to use Pronto codes on the MX-700? You mentioned opening CCF files - does this mean we can open a CCF and pick codes to assign to specific buttons on the MX-700?

Here's an idea of how it works right now. Obviously, with software, additional features could be added later.

It opens up the CCF and shows you each panel and allows you to drag any IR code to any button on the MX-700 in MX Editor. It is as simple as that. It doesn't have hex code entering, but this is something I will still encourage them to do.

So, it doesn't actually convert the whole CCF and import it into the editor as a device (i.e. not batch conversion). It just shows you the CCF panels, and a tree view similar to ProntoEdit, and lets you drag individual codes to MX Editor.

Quite simple, and it has worked flawlessly on the CCFs I've tried so far.

... Greg

That is about the way I expected / hoped that it would turn out. Easy for novices with the drag-n-drop method!

That sounds like the ticket, Greg. Converting whole devices makes no sense because there's no (sensible) way to match a virtual button layout to a fixed button configuration.

Let me know if you need more beta testers :).

DJ

One anomaly I've noticed so far is that if the panel contains buttons that have been labeled with Pronto font lettering (ie: has a "Name" in "Properties"), that lettering is not showing up on the MXEditor screen. However, if you start to drag the button, an MXEditor button flag pops up and gives you button name. The IR code is always there though and that's the main thing. Very nice job!

Mike
www.SurfRemoteControl.com

Sounds really great, Greg. Let's hope that the ability to enter a Pronto code directly is added, but otherwise its sounds well thought out.

Can either of you answer the following question: can the MX-700 handle IR codes it can't otherwise learn via this method? I'm thinking of the Sony sound field codes, in particular?

Sorry David, but I don't own or sell any Sony equipment to try it out with. Good question though. It would be very nice if it did work.

Actually, if you know of a specific CCF with a few Soundfield commands, I could create an mxd file and e-mail it to you to try.

Thanks for the info Greg and Mike


do you mean special characters? that would be normal since they only exist in the Pronto font. I guess they could install it, but then that might have legal implications.


I was just going to say that when I read the first part of your reply. Also I think some of the sound field commands are not one code, but macros, so the translator might not be able to handle them as is

Just as long as the sound field commands are made up of IR codes, you can transfer the commands and then set up your own macro.

The macros are actually shown in the MX Editor CCF window, so it would be no big deal to make up a new macro in MX Editor.

The sound fields I have in my Pronto configuration are one code, albeit fairly long ones. One interesting thing, though, is that I found an MXD file on this site containing a few - not all - of the sound fields.

Mike, my MX-700 is on order, and I should have it early next week as it is currently in the hands of FedEx. I'd certainly be interested in trying the sound field import, but in terms of answering the question, there may be someone else here who already has the required hardware.

I'll check this thread this afternoon after I get back home, and if nobody else has chimed in, I'll prepare an export from my Pronto configuration for you to try. I can then try it and report back to the forum once my remote arrives.

Sounds great! This is very exciting news.

Will the conversion tool be fully integrated into the main MXEditer software, or will it be standalone. From the descriptions, it sounds integrated, which I think would be best.

Also, is there any reason they are putting off the direct code entry other than just wanting to do the file conversion first? Seems like the direct code entry would be easier to implement, but the file conversion would be more desirable to end users.

In other words, I agree with their priorities -- I'm just greedy and want it all! ;-)

Sean

Actually, any text that's added to a button with ProntoEdit (rather than being part of the graphic) is not showing up. I've only seen it with a couple of CCFs so far, so I'll have to check it out further.

Sean,

The conversion tool is just another window in MXEditor. Even if all you had was a hex code, you could assign it to a button in ProntoEdit, then open that CCF in MXEditor. Granted it's an extra step, but easy to do when you're only talking about a few commands.