From: Lennart Poettering <mznyfn@0pointer.de>
To: Ng Oon-Ee <ngoonee@gmail.com>
Cc: Raymond Yau <superquad.vortex2@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: Alsa plugin unable to be loaded by Pulseaudio
Date: Wed, 9 Sep 2009 15:59:39 +0200 [thread overview]
Message-ID: <20090909135939.GA14530@tango.0pointer.de> (raw)
In-Reply-To: <1252502217.20038.3.camel@localhost.localdomain>
On Wed, 09.09.09 21:16, Ng Oon-Ee (ngoonee@gmail.com) wrote:
> The "test" device is defined as follows (should have put it in
> initially).
>
> pcm.test {
> type plug
> slave { pcm "hw:0,0" }
> }
>
> It works with aplay. My issue is that the pulseaudio server cannot load
> alsa plugins since 1.0.20 (as far as I can tell, ubuntuforums has a
> thread which suggested as such). When I queried the pulse ML, Lennart
> posted the below reply, which I've forwarded here to alsa-devel.
>
> Basically, the issue as Lennart sees it is summarized by his last 3
> paragraphs (bottom of this mail). He specifies the difference between
> the way alsa is reacting to pulse and the way it 'should'.
After the discussion we had on alsa-devel about the ordering how buffer
size and period size are initialized i have now changed PA git to try
harder to initialize those values. Would be good if you could check if
that actually makes your problem go away.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2009-09-09 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 23:16 Alsa plugin unable to be loaded by Pulseaudio Ng Oon-Ee
2009-09-07 23:45 ` Raymond Yau
2009-09-07 23:51 ` Lennart Poettering
2009-09-09 8:10 ` Raymond Yau
2009-09-09 13:16 ` Ng Oon-Ee
2009-09-09 13:59 ` Lennart Poettering [this message]
2009-09-09 14:16 ` Ng Oon-Ee
2009-09-09 15:00 ` Ng Oon-Ee
2009-09-10 6:40 ` Raymond Yau
2009-09-10 8:54 ` Ng Oon-Ee
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=20090909135939.GA14530@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=ngoonee@gmail.com \
--cc=superquad.vortex2@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