Maybe a way to handle this would be to have Mark's kernel be able to trap and report a 'mute input signal present' as a fake 'button code', that way we would then map it using the IR maps so that the user can decide what happens.

e.g. if I want to pause the current source then switch to the Aux in channel I can do that [and unmute that output].

Some other folks might just want to switch channels with no muting and someone else might want to switch the Preset # X on the Tuner module.

If its done via the IR maps then everyone can have it done to there liking.

the only thing is:

1. Can we map the Mute input signal to a fake button [and of course map the fake button press into a mute signal input player software in case someone needs to be able to fake the 'Mute input' via a IR remote [or eventually (nudge,nudge) a Sony Stalk Controller] button code.

2. Can we stop the mute input getting to the player software unless we want it to?

3. Does Mark have the time and inclination to put this functionality into the kernel?