More corruption with ARRX18G

madbrain · Post by **madbrain** » Thu Oct 05, 2023 1:36 am

Folllowing the previous corruption thread, I redid my entire remote from scratch in RMIR 3.03 . Unfortunately, I got into a different corruption situation, one where the remote stops sending any IR codes, but there is still (misleading) feedback on the touchscreen that something is being sent. This happens when I select the "Watch PC" activity and the volume up key for example. The only fix I have found is to open the battery compartment and remove/reinsert the battery. But as soon as I try that sequence again, it'll get into the same state. I have posted the .rmir file on my google drive at https://drive.google.com/file/d/1PRB5J7 ... sp=sharing .

Post by **The Robman** » Thu Oct 05, 2023 7:13 am

Moved to Diagnosis Area:
https://www.hifi-remote.com/forums/dload ... e_id=26782

Post by **mathdon** » Sun Oct 08, 2023 6:40 am

The problem lies in your settings, not in RMIR. On the General tab you have used Volume Lock to redirect the Vol+, Vol- and Mute keys for all devices to Marantz audio. On the Activities tab you redirect these buttons for the Watch PC activity to PC. That results in a double redirection, first to PC and from there to Marantz audio. The remote does not support such double redirection and it appears that it causes it to lock up.

My testing showed that changing the Watch PC setting for this button group to Marantz audio, so avoiding a second redirection, resolved the lockup issue. Some of the other activities need a similar change.

madbrain · Post by **madbrain** » Wed May 14, 2025 3:29 pm

mathdon wrote:The problem lies in your settings, not in RMIR. On the General tab you have used Volume Lock to redirect the Vol+, Vol- and Mute keys for all devices to Marantz audio. On the Activities tab you redirect these buttons for the Watch PC activity to PC. That results in a double redirection, first to PC and from there to Marantz audio. The remote does not support such double redirection and it appears that it causes it to lock up.

My testing showed that changing the Watch PC setting for this button group to Marantz audio, so avoiding a second redirection, resolved the lockup issue. Some of the other activities need a similar change.

Thank you for your reply, and sorry for for doing so years later ! That had resolved the problem. I am not sure if it's really within the purview of RMIR, but knowing that the remote will lockup if someone does this, perhaps RMIR should give a warning or error if this particular configuration is attempted. Of course, there are probably other sequences that cause this, possibly with other remotes.

Regardless of whether the remote locks up or not, it's an invalid configuration - even if it didn't lock up, the behavior would be unpredictable as to which configuration it honored for those buttons - the volume lock, or the one from the activities tab. Maybe the volume buttons in the activities tab could be greyed out if there is a volume lock in place.