Benedikt Bär wrote:
> Hi Duncan,
> 
> I just solved this by changing the alsamixer2 code. It's not very
> generic, but it works for my setup.
> 
> Basically, what I did was changing the volume change function to iterate
> through the controls list, and applying the volume.

It may be a general solution.

> Maybe in future releases it is possible to have some more configurations
> in alsamixer, to satisfy such set-ups.
> 
> Also, an option to mute the channel by turning the volume 0 would be
> nice, as the "PCM" control on my card doesn't have a mute switch.

Freevo normally sets the volumne to zero, may be the alsamixer2 plug-in 
does not conform as it should.

> I've also solved the problem with the idlebar volume plug-in, by
> changing the plugin.getbyname argument to "ALSAMIXER2" instead of
> "MIXER". Maybe the volume plug-in will be able to automatically detect
> this in the future.

Should be the default:

Index: src/plugins/alsamixer2.py
===================================================================
--- src/plugins/alsamixer2.py   (revision 10460)
+++ src/plugins/alsamixer2.py   (working copy)
@@ -105,7 +105,7 @@
          Initialise the Alsa Mixer 2 plug-in
          """
          plugin.DaemonPlugin.__init__(self)
-        self.plugin_name = 'ALSAMIXER2'
+        self.plugin_name = 'MIXER'

          #
          # Set the main and mute mixer control names


You can raise a bug report for this problem it you like.

Good to hear that it now works correctly.

Duncan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to