| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.txt | 2026-01-19 | 1.6 kB | |
| RMIR.v3.2.15-bin.zip | 2026-01-19 | 41.8 MB | |
| Totals: 2 Items | 41.8 MB | 12 | |
The package RMIR.v3.2.15-bin.zip is a full installation package for development build 15 of RMIR v3.2. To install it, unzip it into an empty folder that is not read-only. It is not recommended that you replace RMIR v3.2.11, the current official release, with this development build but instead maintain both separately in case issues arise with this build. This build fixes an error in RDFs for remotes HUD0HUD0 and related files that causes spurious error messages when importing certain files from KM. Build 14 treated protocol Sony Combo (12/20) as a special case when importing from KM, as without this change it fails to open KM files with this protocol. Build 13 fixed an issue that when using RMDU to load successive upgrades, it could give a message "Upgrade <none> has inconsistent command lengths.". This is caused by currentSize not being reset to 0 on start of loading each upgrade. Build 12 addressed an issue that occurs in XSight Touch and related remotes when a device upgrade, and so corresponding device, is deleted. This may leave a system macro representing a key move to that device that is now an orphan. Not only does this occur when using RMIR to delete the upgrade, it also happens when using the remote itself to delete the device. This appears to be a firmware issue in the remote that we can do nothing about. RMIR build 12 deletes such a system macro when the device upgrade concerned is deleted with RMIR. It also deletes the orphan when downloading from the remote after such a deletion performed on the remote. This is my best attempt at present to handle this situation.