Suggestion for RM

Post by **The Robman** » Tue Jul 19, 2005 9:35 am

gfb107 wrote:We dont' have to worry about RM selecting the 601x instead of the 881x and this causing a loss of button assignments. In Rob's example we were worried about functions assigned to the macro buttons. The 6012 still has the macro buttons, it's just that they are phantom buttons. This isn't anything we have to worry about. This is the case for all remotes that share an RDF. One RDF means one set of buttons.

Actually, the URC-6012 and URC-8011 only have 1 macro button and no learning buttons, whereas the URC-8811 has 4 macro buttons and 4 learning buttons. There's also the case of the URC-7070 and the 15-1918/1919/1925 which all share the same signature and have very different button sets, but fortunately I don't think you're going to find too many upgrades where one of these is the selected remote.

Nils_Ekberg wrote:Remember that it will not be an upgrade based on an extender RDF since KM does not allow that.

Except for the URC-6131, but that's just to allow keymoves, it doesn't allow you to program any of the extender-specific buttons.

gfb107 · Post by **gfb107** » Tue Jul 19, 2005 10:02 am

The Robman wrote: Actually, the URC-6012 and URC-8011 only have 1 macro button and no learning buttons, whereas the URC-8811 has 4 macro buttons and 4 learning buttons.

Yes, but for the URC-601x and URC-801x, RM treats the "missing" macro and learning buttons as phantom buttons. To RM, a phantom button is a button defined in the RDF that doesn't have a corresponding entry in the .map file, and the only place the user can tell it's a phantom button is on the Layout tab, 'cause they show up outside the image of the remote. You can still assign functions to them. So even if RM incorrectly selected the URC-601x, the user wouldn't be warned that functions assigned to the macro buttons were lost, and if (s)he then switched the remote to the URC-881x, the functions assigned to the macro and learning buttons would still be there. The thing here isn't that these remotes share a common signature, it's that they share a common RDF. They have exactly the same set of buttons.

The Robman wrote:There's also the case of the URC-7070 and the 15-1918/1919/1925 which all share the same signature and have very different button sets, but fortunately I don't think you're going to find too many upgrades where one of these is the selected remote.

Since both KM and RM treat the URC-7070 as distinct from the 15-1918/1919/1925 (they have different RDFs even though they have the same signature), I don't see how RM would ever choose the URC-7070 instead of the 15-1918/1919/1925, or vice versa.

Post by **The Robman** » Tue Jul 19, 2005 10:48 am

Cool, sounds like we're in good shape then.

gfb107 · Post by **gfb107** » Tue Jul 19, 2005 1:15 pm

See how you like RM v1.28.

mtakahar · Post by **mtakahar** » Tue Jul 19, 2005 9:11 pm

RM picks up DTiVo remote (RM-Y809) when I open a KM file created for the TiVo remote (like this one), then I lose a few buttons assignments when I choose SA TiVo remote (RMT-V303).

One problem is RM incorrectly picking up the DTiVo remote.

Losing the button assignment is actually a bigger problem. It can also happen if you accidentally click on the Remote selection drop down list, and it's too late when you see the "Lost Function Assignments" window. On this one, KM is more forgiving against a user error.

Hal

Post by **The Robman** » Tue Jul 19, 2005 9:49 pm

Just FYI, this upgrade was created with an older version of KM where the 2 Sony remotes where simply called:

Sony Tivo and
Sony DirecTivo

The current names are:

Sony Tivo RMT-V303 and
Sony DirecTivo RM-Y809

There is a hidden sheet in KM called Old2New which ties old versions of remote and protocol names back to the current names.

Greg, I don't know if you went with my idea of having an *.ini file that you could use to tie the various KM names to the RM/RDF names, but if you did you might want to pre-load it with all the remote names from that sheet.

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jul 20, 2005 6:12 am

If I were a betting man my guess would be that Greg is taking the name of the remote that is in the KM file and searching the RDF names list that RM builds from the directory and uses the first match.

I am guessing this because RM will pick the extender version of the RDF if it is sorted ahead of the regular RDF by signature name.

Would have been much easier if the KM file had the signature but no going back now.

mtakahar · Post by **mtakahar** » Wed Jul 20, 2005 8:52 am

Nils_Ekberg wrote:If I were a betting man my guess would be that Greg is taking the name of the remote that is in the KM file and searching the RDF names list that RM builds from the directory and uses the first match.

RM takes only the first word and consider it a match if it finds the word anywhere in a RDF name. Any remote model that has some others starting with the same prefix and not the first one in alphabetical order can potentially hit this issue.

But to me, RM's behavior of removing assignments (instead of retain them and disabling them) a LOT more annoying.

Hal

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jul 20, 2005 9:10 am

mtakahar wrote:But to me, RM's behavior of removing assignments (instead of retain them and disabling them) a LOT more annoying.

Hal

Maybe there is something I can do with the RDF names to make it a cleaner sort. Let me think about this a little.

I didn't think RM was discarding the functions just either assigning them to a semi random button or just not assigning them. In other words I thought all the functions from the KM functions tab was retained in the RM functions tab.

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jul 20, 2005 9:47 am

I did some minor renaming of a few RDF's to better suit the sort order and it seems to work better. What I did was change some of the names on the right side so the base would sort in front of the extenders.

An ex. is the 6131 extender RDF had:

PVR0PVx1 (URC-6131(Old)_6131nwB00 Extender1 2K).rdf

And I changed it to:

PVR0PVx1 (URC-6131(Old)_6131nwB00 PVR Remote Extender1 2K).rdf

This change forced it to sort after the base which has the "PVR Remote" in the name. And yes, I did use the RM list as the guide which ignores the signature.

gfb107 · Post by **gfb107** » Wed Jul 20, 2005 10:47 am

It probably makes sense to revisit some of the RDF names, to make them more consistent across the entire set, and to make them more consistent between RM and KM.

That however, just causes RM to have issues with loading upgrade files that were created with the old RDF names. So, I will be adding support for a .ini file to map old/KM remote names to (new) RDF remote names.

It occurs to me that it might be best if this file were distributed with the RDFs rather than with RM. What should we call this file?

In any case, this file will be a text file.
Comment lines begin with # or !
The format for the data will be old Name=new name
For example:

Code: Select all

# This file is used to remap remote names.  This is useful for two things.
# 1. When an RDF is renamed
# 2. To map KM remote names to RDF remote names.
#
# The format for this is <old name>=<new name>
#
15-1925 / 15-1918=RS 15-1925
15-1925=RS 15-1925
15-1994=RS 15-1994 6-in-1 Smart
15-1995=RS 15-1995 7-in-1
15-2103=RS 15-2103 2K Version
15-2104=RS 15-2104 6-In-One AV
15-2107=RS 15-2107 8-In-One Touchscreen
15-2117 / 15-2116=RS 15-2117

Note that the new name must me one of the names RM displays in the remote drop-down box. It is not just the raw name portion of the RDF file.

Post by **The Robman** » Wed Jul 20, 2005 11:07 am

gfb107 wrote:It occurs to me that it might be best if this file were distributed with the RDFs rather than with RM. What should we call this file?

That makes sense, just be sure to have RM look in the RDF folder for it then.

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jul 20, 2005 11:24 am

Greg, I see no problem distributing the file with the rdf's. If you are building it now I will hold off on distributing the updates I just finished so I can compare the names before we send it out since I did change a few in this distribution.

By name I assume your are talking about the name inside the () on the actual file name not the name inside the RDF correct?

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jul 20, 2005 11:27 am

Oh yeah, how about "RDF_Names.ini" or "KM-RM_Remote_Names.in"

gfb107 · Post by **gfb107** » Wed Jul 20, 2005 8:06 pm

Here's what I've got so far.

Note that I've explicitly included those cases where RM picked the correct one anyway, just for completeness. There seem to be some remotes supported by KM that don't have RDFs?

How about OldRemoteNames.ini?

Code: Select all

# This file is used to remap remote names.  This is useful for two things:
# 1. When an RDF is renamed
# 2. To map KM remote names to RDF remote names.
#
# The format for this is <old name>=<new name>
#
15-1925 / 15-1918=RS 15-1925
15-1925=RS 15-1925
15-1994=RS 15-1994 6-in-1 Smart
15-1995=RS 15-1995 7-in-1
15-2103=RS 15-2103 2K Version
15-2104=RS 15-2104 6-In-One AV
15-2107=RS 15-2107 8-In-One Touchscreen
15-2117 / 15-2116=RS 15-2117
15-2133 (Kameleon)=RS 15-2133 Kameleon 2k
15-2133 (RS Kameleon)=RS 15-2133 Kameleon 2k
15-2138 (RS Kameleon 8-in-1)
Atlas 4-Device=Atlas 4-Device
Atlas DVR=Atlas DVR-PVR 5-Device
Atlas DVR Extender=Atlas DVR-PVR 5-Device
Balboa Dolphin=Balboa Dolphin
DRC-400=DRC400 Motorola
DirecTV v1=DirecTV Version 1
DirecTV v2=DirecTV Version 2
Dreambox=Dreambox - 1k version
Dreambox v2=Dreambox V2
Intuitive=Intuitive URC-31XXXB01
Maestro II=Maestro II
Millenium 4=Millennium 4-B00
Millennium 4 BJ8=Millennium4-4MXXXBJ8XXX
Millennium 4=Millennium 4-B00
Navigator URC-43000=Navigator URC-43000-B01
Navigator URC-44000B00=Navigator URC-44000-B00
Navigator URC-44000B02/B04=Navigator URC-44000-B02
Navigator URC-44000B02=Navigator URC-44000-B02
Navigator=Navigator URC-43000-B01
Outlaw Audio=Outlaw Audio
RCU810=RCA RCU810
REM400 b00=Philips REM400
REM400 b01=Philips REM400
REM400=Philips REM400
Replay 5000=Replay 5000
Replay remote=ReplayTV Version1
ReplayTV (version 1)=ReplayTV Version1
ReplayTV (version 2)=ReplayTV Version2
Scientific-Atlanta AT2000
Scientific-Atlanta ER1 3-Dev=Scientific-Atlanta ER1 (Explorer 3-device)
Scientific-Atlanta Explorer 3=Scientific-Atlanta ER1 (Explorer 3-device)
Scout=Scout 2K
Sky Digital 3=Sky Digital
Sony DirecTiVo RM-Y809=Sony DirecTiVo RM-Y809
Sony DirecTivo=Sony DirecTiVo RM-Y809
Sony TiVo RMT-V303=Sony TiVo RMT-V303
Sony Tivo=Sony TiVo RMT-V303
Topline 5/8=URC-8550 Topline
Toshiba CT-90047=Toshiba CT90047 2k
URC-4080=URC-4080 Video Expert
URC-5650
URC-6011/8011/8811=URC-881x
URC-6131 PVR=URC-6131 PVR Remote
URC-6131 PVR Extender=URC-6131 Extender1
URC-7070=URC-7070 Pro Producer 7
URC-7200 / 5650=URC-7200 Cinema 7
URC-7200=URC-7200 Cinema 7
URC-7540 / 7542=URC-7540 One for All 4
URC-7541 / 7544=URC-7544 2K Version
URC-7541=URC-7544 2K Version
URC-7560 / 7562=URC-7550 One for All
URC-7560=URC-7550 One for All
URC-7800 / 6800=URC-7800 Cinema
URC-7800/6800=URC-7800 Cinema
URC-8060 (Euro Kameleon)=URC-8060 Kameleon
URC-8060 (Kameleon)=URC-8060 Kameleon
URC-8090 b00/1=URC-8090-B00 Producer 8
URC-8090 b02=URC-8090-B02 Producer 8
URC-8090b00/1=URC-8090-B00 Producer 8
URC-8090b02=URC-8090-B02 Producer 8
URC-8550 / 5550 (Topline)=URC-8550 Topline
URC-8780=URC-8780 Producer 8
URC-881x / 801x / 601x=URC-881x
URC-8910/9910=URC-9910(New)
URC-9800 / 8800=URC-9800 Producer 8
URC-9800/8800=URC-9800 Producer 8
URC-9910 / 8910 / UEI HTPro=URC-9910(New)
URC-9910 / 8910=URC-9910(New)
URC-9910 / 8910=URC-9910(New)
URC-9960 (OFA Kameleon)=URC-9960 One For All Kameleon