Re: [GnomeMeeting-list] [PATCH] No audio feedback in 0.98 config druid!!!

[Chris Rankin <rankincj yahoo com>]

 --- Christopher Warner <zanee kernelcode com> wrote:
> > d) The OSS interface was adjusting the completely
> > wrong mixer device anyway. The correct one was
> > actually "AC97 Capture", not "MIC".
> 
> Which is incorrect.. "AC97 Capture" is Alsa..
> Earlier you mentioned you had an SBLive card using
> OSS emulation mode. Obviously that's not the
> case, if AC97 was the correct interface. Siply
> because it's not an OSS interface. So in all reality
> it was adjusting the right interface and before you
> test you can make sure that devices and interfaces
> are set correctly.

<Extreme Patience Mode>
Yes, "AC97 Capture" is an ALSA mixer device. The OSS
emulation layer works by mapping these ALSA devices to
their OSS equivalents, so that there is an effective
OSS "MIC" setting available. And not unreasonably,
this maps to the ALSA "MIC" device. So when
gnomemeeting ramps the OSS "MIC" to 100, it *really*
sets the ALSA "MIC" to 100 instead. However, this is
the *wrong* ALSA mixer device to use. Under ALSA (with
the SB Live! anyway), it is best to leave the "MIC"
device muted and push the "AC97 Capture" to 100
instead. Unfortunately, the "AC97 Capture" has no OSS
equivalent.

Yes, I know that you can't possibly cater for every
conceivable mixer device mapping, some of which may or
may not even be wrong. That is precisely why you
should LEAVE THE MIXER SETTINGS ALONE, and allow the
user to adjust them him/herself. 

And if you are about to explain to me that the
SB-Live!'s OSS-to-ALSA mixer mapping is "obviously"
wrong, then I suggest that you present your case to
the ALSA developers instead.

So if you've QUITE finished calling me a liar and
lecturing me about how my own Linux box is
configured...
</Extreme Patience Mode>

> > Since you've obviously never experienced this
> problem
> > for yourself, let me suggest what the only real
> > solution can be:
> > 1) Rename the "OK" button to "End Test". Do not
> > disable it.
> 
> It's disabled initially because it's a procedure. If
> you want immediate abort, then an abort button would
> have to be added which 5 seconds later would be
> useless if you could End Test... So if anything it
> should be renamed to End Test.

These are implementation details. I am giving you the
"end user" perspective that intuitively there should
be ONE button, and it should ALWAYS end the test
immediately. And thereby not FORCE the unluckier of
your users to endure 5 seconds of LOUD FEEDBACK!

I neither know nor care how best to achieve this.

> > 2) Add a MIC mixer control to the test dialog, and
> > invite the user to adjust if if s/he cannot hear
> > anything (your third suggestion). Show the user
> > the current setting, and leave it there.
> 
> Adding to the test dialog seems like a good idea.
> Send the patches..

I've already sent a patch that meets my needs, thanks.
However, you might want to consider the plight of the
rest of your poor users.

Sincerely,
Chris


________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk