Hello Rodolfo,
Thankyou for your fast answer, but I woud not bother to much with it,
because it is not realy neccesary
Am 2011-03-19 12:07:09, schrieb Rodolfo kix Garcia:
> You need (else, correct me) that one dock supports multiple
> soundcards, then:
right, and the commandlines I use are
wmmixer --mix-device /dev/mixer
and
wmmixer --mix-device /dev/mixer1
wmmixer --mix-device /dev/mixer2
> 1. The parameter (-m) to select the device must be changed to
> support multiple devices
Not neccesary, because I would not change the current behavoiour and use
the .wmmixerrc normaly.
> 2. Because in the configuration file you select only the channel "0"
> as a number, and not the device, the configuration file needs to be
> changed to support multiple soundcards. Then, should accept
> something like "addchannel 0,1" for the souncard "0" and the channel
> "1"
why not ler wmmixer chech for multiple config files like
1) ~/.wmmixerrc-${device}
2) ~/.wmmixerrc
where 1) can be in my case
~/.wmmixerrc-mixer1
~/.wmmixerrc-mixer2
and my "mixer" does not need one because it can use the default one.
> 3. You need to check the device list sort, because if one device was
> in /dev/mixer and now is /dev/mixer0, then the channels are
> affecting to other device.
Not neccesary
> 4. Because now you have multiple devices, the application must to
> know what device is selected, and need to have a list of devices. In
> the source, the class "WMMixer" has only one device and should be
> changed to an array. For this reason, abstraction between the
> devices and the user interfaces is needed to do that.
If wir go for something ike ~/.wmmixerrc-${device} we can change "Class"
and/or "Resource" to something like
WMMixer_${device}
and
wmmixer_${device}
which would be transparent and does not require a rewrite from scratch.
> After read the source, to do that, we need to rewrite the full application.
Urgs! Not neccesary, only some smal adds to the feading of the config
file and changing the Calass/Resource.
> Is possible to do that? probably. But the problem is that the
> current application and the new application will be completely
> different.
Eh no, this would be not in my sense.
> In my oppinion, this "bug" is not a real bug, is not a little patch,
> is a new application design, and the bug should be closed.
What do you think about my idea?
It would not change enything for existing users... but enhance the
funftionality for power users. ;-)
> Regards,
> kix.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
--
##################### Debian GNU/Linux Consultant ######################
Development of Intranet and Embedded Systems with Debian GNU/Linux
itsystems@tdnet France EURL itsystems@tdnet UG (limited liability)
Owner Michelle Konzack Owner Michelle Konzack
Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France 77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix
<http://www.itsystems.tamay-dogan.net/> <http://www.flexray4linux.org/>
<http://www.debian.tamay-dogan.net/> <http://www.can4linux.org/>
Jabber linux4michelle@jabber.ccc.de
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Attachment:
signature.pgp
Description: Digital signature