PID $016C: XMP Protocol

alanrichey · Post by **alanrichey** » Thu Jun 24, 2010 7:59 am

I think it works, no-one has complained yet

I use the EXE version so maybe that is in there.

Post by **The Robman** » Fri Jun 25, 2010 9:59 am

As part of the "clean up" process that I am doing for upgrades in the file section, I am converting "Manual Settings" upgrades to use named protocols when they are available. As such, I want to convert for the XMP "Manual Settings" upgrades too.

In KM there 3 XMP options:
XMP (UEI)
XMP (JP1)
XMP - which selects UEI or JP1 depending on whether the UEI executor is installed in the selected remote.

Obviously, I'd like to select the 3rd option as it's the most flexible, however if I do so, the upgrades will not be importable in RM because it doesn't have a generic XMP option.

Does anyone know how to set up an equivalent XMP option in protocols.ini for RM?

Also, when RM imports an "XMP (JP1)" upgrade, it doesn't capture the XMP-1/XMP-2 setting. Can that be fixed?

In KM, when you select "XMP (UEI)" for a remote that does not have the protocol installed, KM doesn't provide the protocol code. I think it should (perhaps with a notice that the JP1 version would use less memory).

gfb107 · Post by **gfb107** » Fri Jun 25, 2010 2:48 pm

I haven't followed this discussion. I'm sure I can fix the RM import problem quickly if you provide links to files that exhibit the problem, as well as a short explanation of what's going wrong.

Post by **The Robman** » Fri Jun 25, 2010 5:55 pm

You can create the files yourself using KM. KM has 3 XMP options, 2 of which import OK into RM (ie, XMP (UEI) and XMP (JP1) ) and a 3rd which doesn't.

The 3rd option is just called "XMP". If your remote has $016C built in, selecting XMP will use the built in executor. If your remote does not have $016C built in, selecting XMP will use the XMP (JP1) executor.

The problem is, if I create a KM upgrade with XMP selected, I can't import it into RM because RM doesn't have a generic "XMP" protocol listed in protocols.ini.

gfb107 · Post by **gfb107** » Fri Jun 25, 2010 6:10 pm

Sorry, I don't use KM anymore.

Post by **The Robman** » Fri Jun 25, 2010 6:13 pm

Can't or won't?

gfb107 · Post by **gfb107** » Fri Jun 25, 2010 6:34 pm

I had to uninstall my "home use" version of Excel when I lost my job a few months ago. I got a new job a month later, but there's no home use program. So my home computers are all Excel-free.

andyross · Post by **andyross** » Sat Jun 26, 2010 5:58 am

Does KM work with Open Office?

gfb107 · Post by **gfb107** » Sat Jun 26, 2010 7:02 am

andyross wrote:Does KM work with Open Office?

No. Excel only. That's one of the reasons RM was created.

Post by **The Robman** » Sat Jun 26, 2010 8:42 am

I just created a KM file that uses the generic XMP protocol.
http://www.hifi-remote.com/forums/dload ... le_id=8572

gfb107 · Post by **gfb107** » Sat Jun 26, 2010 10:17 am

Thanks

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sat Jun 26, 2010 10:24 am

The Robman wrote:The 3rd option is just called "XMP". If your remote has $016C built in, selecting XMP will use the built in executor. If your remote does not have $016C built in, selecting XMP will use the XMP (JP1) executor.

The problem is, if I create a KM upgrade with XMP selected, I can't import it into RM because RM doesn't have a generic "XMP" protocol listed in protocols.ini.

Greg, this will take some thought to solve. RM will need some way to select between two different protocols.ini entries based on whether a specific PID is present in the remote. In the case where a user chooses the "generic" XMP entry, if $016C is resident in the remote, then it would alias to XMP (UEI), else if not, it would use XMP (JP1). The "XMP" entry itself would probably be some sort of dummy entry.

Post by **The Robman** » Sat Jun 26, 2010 10:59 am

Could we do this using the variant parameter?

There's another issue with XMP and RM. I tried importing a Slingbox bin file that uses XMP and, of course, it immediately decoded as Dreambox, so I deleted the Dreambox and pid 0162 entries from protocols.ini and then tried importing it again and it caused RM to just hang. I had to go to the task list to cancel it, which is what I always have to do when RM hangs.

I have gone through all the files in the file section that use any of the variants of $016C (either as Dreambox, pid 016C or "Manual Settings") and have converted them to use XMP. I used XMP (Slingbox) for the files in the Slingbox folder and XMP (JP1) for everything else.

However, people will still have old upgrade files on their local harddrives that use the old settings. Is there a way that we could use the "old to new" features of KM and RM to have the apps automatically convert these upgrades to XMP?

gfb107 · Post by **gfb107** » Fri Jul 02, 2010 2:41 pm

From an RM perspective, we shouldn't have different names for XMP (JP1) and XMP (UEI). The name should just be XMP, with an appropriate variantName.

To get RM to use the UEI variant only when it is built into the remote is simple:

Make sure it appears first in protocols.ini, and
Don't include protocol code for that variant in protocols.ini (The protocol code may be left in as a comment for completeness if desired)

.

I'm working on the XMP-1/XMP-2 issue now.

gfb107 · Post by **gfb107** » Sat Jul 03, 2010 1:19 pm

RM v1.99preview5 has improved handling of XMP. Please try it out.