When using RMIR v2.14.3, with remote URC-7955 (604803), if I try setting up a controlled DSM bound to a shifted key, and then save the file, then RMIR can no loader read the file: "Error loading file". If I set the DSM to a non-shift key, or delete the DSM, then the problem disappears.
I have attached a minimal test case. The attached file was a download of the remote after a factory reset, and a single DSM set up with a shifted key (no upgrades). The file cannot be loaded by RMIR.
Also: if I upload such configuration to the remote, then I can no longer download the remote.
seems this is still a bug in 2026 on the latest dev RMIR. hopefully it gets fixed one of these years.
Last edit: Donald K 2026-04-21
If I read the original message correctly, RMIR is supposed to throw an error upon loading the attached file. For me, using version 3.2.15, this does not happen; it loads without problems. The Special Function tab however shows the entry in purple, so there appears to be something fishy; probably it is considered invalid for some reason.
It might be better to ask in the forum.
If you open test.rmir in a recent RMIR version, the latest release being v3.2.16 but I think any v3.2 build will do, it will open and you will see that the DSM in test.rmir is NOT a controlled DSM, it is a real-time DSM. The only valid key that you can assign a real-time DSM to is NetTV. It is possible for testing purposes to turn off the validation by selecting the menu item Advanced > Disable Upload Restrictions. If you do so, create an entry and then deselect this item, the created entry will be highlighted in purple. By using an old version of RMIR you have managed to assign a real-time DSM to Shift-Play, which is why it now gets highlighted in purple. If you create a real controlled DSM then you CAN assign it to a shifted key with v3.2.16 or other recent builds.
To be honest I don't completely remember the context anymore after all this time. I think my intent back then was to create a controlled DSM and RMIR was misbehaving for some reason, but as previous comments stated this is a real-time DSM (unsure what is the actual difference in practice between them in this particular remote); I am not sure if the use of real-time here was my mistake or a genuine bug in RMIR. Anyhow, the fact that RMIR can open the file now and warn about it indicates to me that the original problem of not being able to load the file was fixed.