From: James Courtier-Dutton <James@superbug.co.uk>
To: Oliver Schinagl <oliver@schinagl.nl>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: emu10k1 mute problems.
Date: Sat, 09 Dec 2006 01:28:54 +0000 [thread overview]
Message-ID: <457A1156.4000002@superbug.co.uk> (raw)
In-Reply-To: <4579B9F8.4020109@schinagl.nl>
Oliver Schinagl wrote:
> Hi,
>
> I am wondering if there's a bugzilla or some place to drop a bugreport
> for my SBLive! (emu10k1)?
Please report this but to the ALSA bug tracker.
https://bugtrack.alsa-project.org/alsa-bug/
See the link from
http://alsa-project.org/
I think the problem you describe is that the emu10k1 has a single mute
control for both channels, so you do not have the left/right mute.
You need to do a test first to find out if the is separate left/right
mute or if they are separate. If there is only one, the
"SND_MIXER_SCHN_FRONT_LEFT" controls both channels.
Maybe it would be sensible to change the alsa-lib api so either
SND_MIXER_SCHN_FRONT_LEFT or SND_MIXER_SCHN_FRONT_RIGHT will control
both left/right is the mute control is shared.
>
> Now they both are working but there's one thing that seems to be going
> wrong. Since it only happens on the SBLive (the via onboard works as it
> should) it must be a bug in the emu10k1 driver.
>
> I use the following code to mute the left resp. right channels.
>
> snd_mixer_selem_set_playback_switch(elem, SND_MIXER_SCHN_FRONT_LEFT, 0);
> snd_mixer_selem_set_playback_switch(elem,
> SND_MIXER_SCHN_FRONT_RIGHT, 0);
>
> However, when muting the left channel, both channels get muted. When
> muting the the right channel, none get muted. It's not just my app that
> shows this behavious, gkrellm-volume plugin for instance does the same
> thing (wrong).
>
>
> Since there aren't really much mixers that do balance properly, there
> isn't much other volume controls I can test this with. I do however
> notice in alsamixer, that below the bar, it says [MM] or [OO] on the
> SBLive!, but with the Via, I get all possibilities done, including [MO]
> or [OM].
>
> Thanks,
>
> Oliver
>
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-12-09 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000e01c7165d$ceeebaf0$dedde354@dwnze>
2006-12-03 18:34 ` Reading from the output buffer Sean D'Epagnier
2006-12-08 19:16 ` emu10k1 mute problems Oliver Schinagl
2006-12-09 1:28 ` James Courtier-Dutton [this message]
2006-12-09 8:05 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457A1156.4000002@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=oliver@schinagl.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.