Colin Guthrie wrote:
Tomas Carnecky wrote:
Colin Guthrie wrote:
I disagree that this community is unresponsive. You just have to be
patient. Lennart is the main developer but he does not sit slavishly
reading the mailing list and responding immediately. He'll usually have
a big purge every
Colin Guthrie wrote:
When I last looked at the wine alsa layer it was *really* nasty. It
didn't even open the default device, it would instead try to open
default:0 I think it was cleaned up a bit, but it should be very
simple for someone to rewrite it or write a direct pulse driver. The
On Sat, May 03, 2008 at 04:48:05PM -0700, Nick Thompson wrote:
Given what you say (above) about per device routing not being possible I
think the area I'd like to concentrate on is figuring out how a module
can detect streams as they are being created. That way it could get the
call in to
Nikolai Beier wrote:
2008/5/4 Tomas Carnecky [EMAIL PROTECTED]:
Colin Guthrie wrote:
Tomas Carnecky wrote:
Colin Guthrie wrote:
I disagree that this community is unresponsive. You just have to be
patient. Lennart is the main developer but he does not sit slavishly
reading the
Tomas Carnecky wrote:
Colin Guthrie wrote:
What are the bugs in the pulse alsa plugin you refer to? There are some
feature limitations but they are typically down to what any ioplug
plugin is capable of.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 (see the
comments made by
Colin Guthrie wrote:
Tomas Carnecky wrote:
Colin Guthrie wrote:
What are the bugs in the pulse alsa plugin you refer to? There are some
feature limitations but they are typically down to what any ioplug
plugin is capable of.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 (see
Nikolai Beier wrote:
Oh, now I looked at the bug reports and got confused again. Is this
the key points? (Ses below:)
== Wine and the alsa plugin for PulseAudio (alsa pulse plugin) ==
PulseAudio normally takes control of the hardware through the device
driver/ALSA. Thereby the hardware
