From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: surround51 problems. (problem patch identified)
Date: Mon, 10 Oct 2005 13:13:34 +0200 [thread overview]
Message-ID: <s5hd5mdaald.wl%tiwai@suse.de> (raw)
In-Reply-To: <434A4C65.5000004@superbug.co.uk>
At Mon, 10 Oct 2005 12:11:33 +0100,
James Courtier-Dutton wrote:
>
> Takashi Iwai wrote:
>
> >The relevant change is only to pcm_generic.c and pcm_plug.c.
> >Others should have play no role.
> >If you don't access with plug layer, even the latter has no
> >influence. But I can't tell you exactly unless I know which
> >configuration you used. Developers are not always good bug
> >reporters ;)
> >
> >
> >Takashi
> >
> >
> >
>
> The tests I did were:
>
> speaker-test -c6 -Dsurround51
> speaker-test -c6 -Dplug:surround51
>
> Both failed as far as I can remember (I will double check tonight)
> I was using a standard Audigy2 config, with no .asoundrc.
OK, then it's very likely a problem of multi layer.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
next prev parent reply other threads:[~2005-10-10 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EBEWw-0006Qa-Li@sc8-pr-cvs1.sourceforge.net>
2005-10-08 18:30 ` surround51 problems. (problem patch identified) James Courtier-Dutton
2005-10-08 18:40 ` James Courtier-Dutton
2005-10-10 10:37 ` Takashi Iwai
2005-10-10 11:11 ` James Courtier-Dutton
2005-10-10 11:13 ` Takashi Iwai [this message]
2005-10-10 15:23 ` Takashi Iwai
2005-10-10 16:34 ` Thierry Vignaud
2005-10-10 16:38 ` Takashi Iwai
2005-10-10 19:41 ` James Courtier-Dutton
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=s5hd5mdaald.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.