I am just curious if anyone else is wondering the same thing I am about the “My Database” section of the new ProntoEdit Professional software. I am in the process of migrating my TSU7000 over to the newer TSU TSU9400 and had a question about the best way to configure the devices for their commands. The way I did it in the older ProntoEdit NG was that I built a standard page(s) with all of the IR codes from my existing remote controls. That’s right, I sat down with all of my remote controls and created a new page(s) that housed all of the learned IR signals assigned to a standard button for my remotes. After playing around with the ProntoEdit software for a number of months this way just made the most sense to me for the way I was configuring my remote control. I would just like to know if anyone else takes/took this route or would it be better for me to start building my new configuration utilizing the “My Database” section? I have run into a few issues with the “My Database” section and just did not want to spend the time trying to correct the issue if other users were still utilizing their configurations in the manner that I am. Any advice is more than welcome.

I am just trying to build a configuration in the “best” manner possible. I am in the process of learning as much as I can about the newer Pronto’s (TSU9400 and even the 9600) and ProntoScripting language. I just want to make sure I am headed down the right track and not a track that will have me rebuilding my configuration in the coming months. I hope this make sense and welcome any input. Thanks to anyone who responds.

-Jason

I still keep my own IR code database via dedicated IR code devices, then linking to the IR code buttons in said devices throughout the rest of my configuration file. I spent a lot of time testing the "My Database" and "Factory Database" features of the editor during the TSU9600 beta test, but since then haven't touched them. I also still maintain my own gallery via folders on my computer browsing to said images when needed via the "Insert..." option. Why create extra steps for yourself if you don't have to. I just don't see the point.

Another reason to keep your own is that you can't view HEX data in the database codes. Nothing to copy/paste if nessessary.

Rich

Guys thank you very much. Glad to know my thoughts on building my configurations is headed in the right direction. So it sounds like I will just continue down the path I am already headed with my device specific IR-Codes pages. I am not real fond of the My Database section anyway.

On a side not I want to make sure I point out to anyone else that they may notice device name and settings corruption in the My Database section when trying to add any new devices or make changes to existing devices. I notice that either the Logitech Setpoint software or the Logitech G-Series keyboard profiler software were causing odd and erroneous problems while in ProntoEdit Professional. Once I exited out of both of those applications then everything was fine. If I get the chance to do any additional testing I will try to narrow it down to which one exactly it was. However since being given the guidance from some of the "pros" above I will probably move away from using any of the My Database section anymore.

Thanks again guys.

Not so. You have complete access to the codes in My Database.

Could you elaborate further. So far, all I've been able to do is open up a database code and it gives me the ability to learn but does not display the HEX itself. It just displays "DATABASE CODE" in the IR window. So if I have another program that will let me input Pronto Hex format into it, where do I get the data from?

The original idea of the My Database section was to allow custom theater installers to keep complete device collections in there, for systems they frequently program, so they can be quickly added to a new config, etc.

One time programmers may not get much benefit from it.

The process is to open the database, choose your device and then save it to "my database". Then you may learn in codes, etc and you will be able to see the hex, of those codes. You will not see the hex from any of the original database codes. Concept is; if the database codes work, then use them. If not, learn in the one's you need into the device in My Database.

Dave

If you already have an XCF that already has links to codes in IR-specific devices, then you add the IR-specific devices to "My Database" the existing links still point to the old IR-specific devices. It's not like the existing links are automatically changed to use the entries in the "My Database". Thus, for existing configurations that already use the IR-specific devices, I don't see much use for "My Database", unless, as Dave said, you plan on creating other configurations in the future that can use the "My Database" codes.