RDF Development and Maintenance Process

If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
Capn Trips
Expert
Posts: 3989
Joined: Fri Oct 03, 2003 6:56 am

Post by Capn Trips »

What's PM?
Beginners - Read this thread first
READ BEFORE POSTING or your post will be DELETED!


Remotes: OFA XSight Touch, AR XSight Touch
TVs: LG 65" Smart LED TV; Samsung QN850BF Series - 8K UHD Neo QLED LCD TV
RCVR: Onkyo TX-SR875; Integra DTR 40.3
DVD/VCR: Pioneer DV-400VK (multi-region DVD), Sony BDP-S350 (Blu-ray), Toshiba HD-A3 (HD-DVD), Panasonic AG-W1 (Multi-system VCR);
Laserdisc: Pioneer CLD-D704.
Amazon Firestick
tape deck: Pioneer CT 1380WR (double cassette deck)
(But I still have to get up for my beer)
vickyg2003
Site Admin
Posts: 7104
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

PM is a master list of supported protocols. Protocols.ini and KM keep track of the various protocol versions and how to build upgrades for them. KM has this data hard coded for each remote that is supported. RM picks up this information from the RDF. The thing is, a lot more protocols have gained support over the past 2 years. This is the cause for so many "my RM protocol" doesn't work problems. It was kind of like playing russian roulette. You never knew when RM was going to be wrong because the RDF was out of date. I think there were 107 RDF's with the out-of-date protocol information in the last RDF release. So this will be a big help for RM users.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Post Reply