Custom Mapping For MUTE Function -- Redux

[NFLnut]

I tried this over in the General Discussion forum a few months back. I got a few suggestions, but I never could figure this out, and my last post never got an answer. I thought maybe THIS forum was more appropriate and I could try again:

I have a rudimentary understanding of the Default.map and Custom.map files. I want to map a button press to a MUTE function. I would like to simultaneously press on both the VOL_UP and VOL_DOWN buttons and get a volume level of ZERO (Mute). Also, if possible, I would like any subsequent press of VOL_UP or VOL_DOWN to result in the volume to return to the previous state, i.e. if volume was at 65 prior to mute, the volume would return to 65 after the VOL_UP or VOL_DOWN (second) hit.

Are either of these possible? How would I do this? Also, would the line go into the [Common] section of the .map file or another section? I would guess that I should make a Custom.map file by copying all of the Default.map file to it and adding the appropriate MUTE function line?

-----------------------------------------------------------------------------

I guess I'll try again ..

Is there ANY way to implement a "MUTE" function on the standard Squeezebox remote?

I've read the "How Do I Map a Remote Control Button" and saw THIS (when someone wanted to have date/time some up when holding the text size button):

[common]
size = dead
size.single = brightness_toggle
size.hold = datetime

I have absolutely NO idea after reading that thread or the Wiki what any of those commands mean or how to adapt them to do what I want to do.

What I DID do was add to "Custom.map" :

[Custom]

0 = Muting


and then I made certain that Squeezecenter settings were set to use Custom.map, and restarted Squeezecenter. And when I press zero it still is doing number scroll (like in the default.map settings).

Again, I want to either

(1) press both the Up_VOL AND Down VOL and get a MUTE function. I want a subsequent press of either VOL_UP or VOL_DOWN to return the volume to the previous (unmuted) state.

OR

(2) press and hold the 0 (ZERO) button and get the MUTE function and then return to unmuted state with VOL UP or VOL DOWN.

Can anyone help me do this?

Someone said the new Controller does this natively. I am not ready to buy a Controller and would like to implement this with the standard SB3 remote.

[NewBuyer]

I too would like to have this functionality. Having function-toggle in SqueezeCenter, for making one of the remote buttons (perhaps the Pause) act as "mute" instead, would sure be nice...

[NFLnut]

I too would like to have this functionality. Having function-toggle in SqueezeCenter, for making one of the remote buttons (perhaps the Pause) act as "mute" instead, would sure be nice...


Actually, PAUSE was the most often specified "remedy." But I need a separate button(s) for MUTE. Because when I listen to streaming audio, I DON'T want to PAUSE, I simply want to QUICKLY reduce the volume to ZERO, and then quickly return it when needed to the previous volume. PAUSE and MUTE should both be separately available as they perform two different functions.

[peterw]

I haven't played with custom maps, but you could certainly redefine the "0.hold" in Default.map if you wanted. You need to look at every mode in brackets that defines a function for "0" -- in 7.3, this'd be [common] and [screensaver] (you don't want to mess with the INPUT mappings, and probably don't need the mute function in [off] mode).

Or you could install ContextMenu 7a18 or newer, use the web UI to disable all but Mute Button. If you also set Mute Button to "autorun", you could invoke mute at any time by holding the right arrow (or holding the Boom knob in). If you ever enabled other ContextMenu options, you'd occasionally find yourself looking at a list and having to scroll to Mute Button and then tap the right arrow, but if Mute is the only enabled CM option and it's autorun, just holding the right arrow should do the trick.

-Peter

[NFLnut]

Thanks Peter! Your ContextMenu app did the trick. Very nice.

A minor problem though -- when I press and hold the right arrow button, I get the context menu which goes directly to MUTE. When I right arrow again (no hold), it MUTES, but then immediately unMUTES. Any idea why it's doing this?

[NFLnut]

Never mind. Just figured it out. I have Moose running on another computer in the house. When I shut Moose down, it stops the immediate unMUTE.

So .. now that I've figured THAT out .. any way to get Moose to stop "undoing" my MUTE without having to lose the functionality of Moose? Also, it would be nice not having to run upstairs just to shut down Moose on the computer up there when I'm using ContextMenu downstairs.