#include <hallo.h>
* Takashi Iwai [Thu, Jul 27 2006, 01:12:34PM]:
> At Mon, 24 Jul 2006 14:40:12 -0400,
> Lee Revell wrote:
> >
> > On Mon, 2006-07-24 at 20:30 +0200, Eduard Bloch wrote:
> > > Hello,
> > >
> > > I try to make my 5.1 speaker set work properly on an SB Live! Player
> > > with Alsa from kernel 2.6.17. Most things work well, but there is
> > > something that feels like a bug or inconsistency in user interface:
> > >
> > > The volume for rear speakers, center, bass speakers seem to behave
> > > indepently from any other controls. When I adjust "Master" setting, it
> > > does not act like master. It is only applied on the front speaker pair,
> > > all others are not changed. I need to go to the particular control
> > > setting in alsamixer and tune them independently. Every time.
> > >
> > > That does not make sence. I expect Master to behave like Master, a
> > > factor which is applied to all available speaker volumes and playing
> > > input sources.
> >
> > This bug has been known for years. STILL no solution.
> >
> > Takashi-san, didn't someone (Mikael Magnusson?) post a patch that fixed
> > this? What happened to it?
>
> That patch did too many things. It added not only yet another master
> but also more new controls, which leads to confusion, IMO.
>
> A simple solution would be an additional DSP-based master that
> replaces the current ac97-master, and rename ac97-master as front.
Could I get a copy of that patch?
Honnestly, the current set of mixer controls is cumbersome. $user can
hardly understand what all the controls are good for, and mixer software
is not user-friendly either. The Live! mixer from Creative gives you a
"joystick" control where you can move the marker around until you feel
beeing in the middle of the room.
And ALSA controls, ie. using alsamixer or even worse, alsamixergui? Lots
of settings, some with discrete values, some with analog, with
foo/foo-LFE/foo-Center/foo-Surround mixer per input source and lots of
other things that are either not sufficiently described trough, or that
I would hardly use, or which are just not working (showing no effects),
all mixed together in one GUI without good visible structure, etc.
Yes, I talk about useability which just sucks. I imagine a more clear
frontend/backend infrastructure, an ultimate solution:
- access to all backend settings is exported with consistent, fixed names
(keywords)
- a wrapper in the library has a database of sound cards and of
applicability of particular controls to it
- an UI control layer would have a database of possible
"end-user-to-control-setting" wrapper. There may be different schemes
of such kind, where compatibility with drivers is documented as well.
- HMI related issues like the grouping hints for the particular
controls in the schemes, the kind of control (binary/discrete/
stepless)
This way, a "new style" ALSA mixer could simply offer different user
models: "simple", "advanced", "full control". Depending on the mode and
on the soundcard (to be controlled), the UI would select a control
scheme. Eg. a set of the most common controls and the "joystick"
mentioned above for "simple" user. A similar things with "advanced" but
more controls, eg. extra joystick per input source attacheable, and
"full control" would be similar to the current chaos.
So far from my imagination...
Eduard.
--
(... diverses rot13 Zeug...)
<+unterfrankendOt> ich bin schwer am zweifeln das diese zeichenfolgen eine
bedeutung haben sollen ...
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
