From: Takashi Iwai <tiwai@suse.de>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Why analog loopback of sigmatel devices got removed?
Date: Fri, 19 Jun 2009 10:23:15 +0200 [thread overview]
Message-ID: <s5hfxdweioc.wl%tiwai@suse.de> (raw)
In-Reply-To: <1245399701.8549.2.camel@localhost>
At Fri, 19 Jun 2009 11:21:41 +0300,
Maxim Levitsky wrote:
>
> On Fri, 2009-06-19 at 08:32 +0200, Takashi Iwai wrote:
> > At Fri, 19 Jun 2009 02:50:35 +0300,
> > Maxim Levitsky wrote:
> > >
> > > Hi,
> > >
> > > Due to lack of time, I didn't update kernel on my desktop system.
> > > Now I notice that analog loopback go removed. Why?
> >
> > Because it harms than helps more often. I've got tons of bug reports
> > and been upset just because users blindly set "Analog Loopback" mixer
> > switch and lost their sound output. This is no mixer element that
> > behaves intuitively -- it shuts out PCM output instead of adding the
> > analog loopback like other hardwares.
>
> Here it doesn't shut PCM.
> I just hear input in headphones, mixed with output.
> I suspect that this feature might not work correctly on newer devices
> that ones I have added.
Possibly...
Takashi
next prev parent reply other threads:[~2009-06-19 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 23:50 Why analog loopback of sigmatel devices got removed? Maxim Levitsky
2009-06-19 6:32 ` Takashi Iwai
2009-06-19 7:27 ` segfault when setting swparams! help Guilherme
2009-06-19 7:31 ` Takashi Iwai
2009-06-19 7:43 ` segfault when setting swparams! help - SOLVED Guilherme
2009-06-19 8:21 ` Why analog loopback of sigmatel devices got removed? Maxim Levitsky
2009-06-19 8:23 ` Takashi Iwai [this message]
2009-06-19 11:36 ` Maxim Levitsky
2009-06-19 12:50 ` Takashi Iwai
2009-06-19 14:55 ` Maxim Levitsky
2009-06-19 18:18 ` Maxim Levitsky
2009-06-19 18:44 ` Takashi Iwai
2009-06-19 21:05 ` Maxim Levitsky
2009-06-20 7:11 ` Takashi Iwai
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=s5hfxdweioc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=maximlevitsky@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox