I have been using a URC-7960 for years - I wish they were still available!
A few days ago I bought a URC-7140 (R04) things were going well, I could load my previous device upgrade .rmdu files, perform a few tweaks to map to a few different buttons on the new remote... then I ran into a problem. It seemed that Stop button was not working. This was common to both a Panasonic blu-ray and a Humax PVR when I was test playing media.
I thought I would try learning the stop from the original PVR remote onto the 7140 remote's stop button. When I downloaded into RMIR I could see that the "Learned signals" tab showed the stop command as the expected protocol and OBC, but the "Key" column showed it to be assigned to the 'Record' key.
To do a more thorough test I decided to work through all of the 8 transport controls. I can see that my Humax PVR OBC codes for the digits 1-8 are in a nice sequence of OBC codes from 3-10, so I worked through the 8 buttons sequentially learning digits 1-8.
I can confirm that my remote matches the picture in <installation folder>/Images/URC-7140.jpg (other than my remote being a 4-device version)
When I look at RMIR's "Learned signals" tab lists (displaying in OBC order) my eight learned commands are listed on the left against keys:
Rewind
Play
Pause
FastFwd
SkipBack
Record
Stop
SkipFwd
But that is not quite the order that I programmed the keys. Referring to the JPG of the 7140, I programmed the keys in normal L-R top to bottom order and stop and record have been transposed.
I was obviously hesitant to think that the keys are wrongly defined in the .rdf because this remote has been around a while, so I expected users to have identified this sooner. As it happens I also bought a 3-device controlling URC-7130 (also an R04) in order to set it up for an elderly father-in-law who is perpetually getting into trouble by fumbling the numerous small keys on his Humax remote control and requiring telephone support!
Having had a look at the RDF structure I thought I might get away with just transposing the Record and Stop keys, but I thought I'd find out if my experience with the 7130 matched the 7140. Having read a lot more about how new remotes have their keys identified by users for the experts on the JP1 project, I could see that the preferred approach is to use the remote to assign macros to keys and then download the result. So this time, with a freshly unwrapped 7130 R04, I used the SimpleSet approach to get a working code for a Samsung TV, then I programmed Stop to be TV numeral key 1 and Record to be "2".
When this is downloaded by RMIR it shows the macro "TV;1" assigned to Record and "TV;2" assigned to Stop - they are swapped.
As I was now more confident that the RDF was incorrect, I coppied the RDF "366801 (URC-7120_7130_7140 OFA Essence R04).rdf" to another directory as a backup and made a copy with the modification of swapping those two keys in lines 78 & 79. I replaced the version in the RemoteMaster/RDF folder and relaunched RMIR and re-downloaded from the remote. Now the macros are displayed on the correct keys.
So two things I'd like to clarify:
(1) Have I "done good" - Is what I've done something which will work or have I broken anything with this hacking with the RDF?
(2) Do you think this is a valid change to make to the RemoteMaster distribution? I must admit that I'm surprised that I'm the first to notice, but perhaps other users haven't been so interested in the media transport controls. I can confirm that all other keys function normally.
It seems such a trivial change to make, but in case it helps, here's a diff:
Code: Select all
~/Documents/JP1$ diff 366801\ \(URC-7120_7130_7140\ OFA\ Essence\ R04\).rdf 366801\ \(URC-7120_7130_7140\ OFA\ Essence\ R04\)_Original.rdf -u
--- "366801 (URC-7120_7130_7140 OFA Essence R04).rdf" 2020-09-07 09:42:28.435007000 +0100
+++ "366801 (URC-7120_7130_7140 OFA Essence R04)_Original.rdf" 2020-03-24 14:20:05.000000000 +0000
@@ -75,8 +75,8 @@
Pause,
"Fast fwd":FastFwd,
"prev track":SkipBack,
-Stop,
Record,
+Stop,
"next track":SkipFwd,
TV=$79:groupDevice,
STB,