From: Tejun Heo <teheo@suse.de>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: tiwai@suse.de, linux-kernel@vger.kernel.org, greg@kroah.com,
fuse-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] OSS Proxy 1.2 using CUSE
Date: Wed, 29 Apr 2009 08:35:01 +0900 [thread overview]
Message-ID: <49F792A5.2070202@suse.de> (raw)
In-Reply-To: <E1Lytf8-0005LD-HJ@pomaz-ex.szeredi.hu>
Hello, Miklos.
Miklos Szeredi wrote:
>> For example, if you start aplay with -v option, it'll show the plugins
>> to use.
>
> OK, it doesn't. So I have to tweak some config files to make it use
> this plugin...
>
> ...done. Well, now things do work, but the sound quality is very
> crappy when PA is mixing two or more streams together (loud cracking
> that maybe sounds like integer overflow).
Which version are you using, it got better and then worse and then
better again IIRC. Yeah, it's still in the process of maturing.
>>> What is the disadvantage of non-native ALSA vs. native ALSA?
>> Well, the question is rather whether you need PA or not...
>
> Yes, OSSP needs it. So the question (to Tejun) is why does OSSP use
> libpulse API instead of libalsa API?
>
> The former seems to be much more mature and easier to configure than
> the latter.
On default installation of any recent major distros, PA is the default
and ALSA via PA is the default too, so the configuration doesn't
matter at all. I think PA is the way to go (all other guys are
already there) && we're past the point of no return at this point &&
it's nicer to program to and has some features I wanted (per-pgrp
volume for example), so...
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-28 23:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:05 [ANNOUNCE] OSS Proxy using CUSE Tejun Heo
2008-08-28 20:01 ` Adrian Bunk
2008-08-28 22:18 ` Greg KH
2008-08-28 23:05 ` H. Peter Anvin
2008-08-28 23:14 ` Greg KH
2008-08-28 23:38 ` H. Peter Anvin
2008-08-28 23:32 ` Alan Cox
2008-08-29 1:33 ` Tejun Heo
2008-08-29 6:50 ` Adrian Bunk
2008-08-29 7:26 ` Tejun Heo
2008-08-29 8:09 ` Miklos Szeredi
2008-08-29 8:21 ` Adrian Bunk
2008-08-29 8:28 ` Tejun Heo
2008-09-02 15:25 ` Pavel Machek
2008-11-27 20:59 ` Jan Engelhardt
2008-11-28 2:23 ` Tejun Heo
2008-11-28 11:35 ` Jan Engelhardt
2008-11-28 12:02 ` Tejun Heo
2008-11-28 12:56 ` Jan Engelhardt
2008-08-29 10:40 ` Takashi Iwai
2008-08-29 10:47 ` Tejun Heo
2009-04-14 2:46 ` [ANNOUNCE] OSS Proxy 1.2 " Tejun Heo
2009-04-22 19:58 ` Miklos Szeredi
2009-04-22 23:59 ` Tejun Heo
2009-06-20 6:13 ` Tejun Heo
2009-06-20 6:37 ` Tejun Heo
2009-04-28 16:01 ` Miklos Szeredi
2009-04-28 16:42 ` Takashi Iwai
2009-04-28 17:17 ` Miklos Szeredi
2009-04-28 19:32 ` Takashi Iwai
2009-04-28 20:12 ` Miklos Szeredi
2009-04-28 21:34 ` Takashi Iwai
2009-04-29 7:13 ` Miklos Szeredi
2009-04-28 23:35 ` Tejun Heo [this message]
2009-04-29 7:20 ` Miklos Szeredi
2009-04-29 7:46 ` Tejun Heo
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=49F792A5.2070202@suse.de \
--to=teheo@suse.de \
--cc=fuse-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tiwai@suse.de \
/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.