On Wed, 07.05.08 07:43, Tomas Carnecky ([EMAIL PROTECTED]) wrote:
>
> Lennart Poettering wrote:
> > On Wed, 07.05.08 00:43, Tomas Carnecky ([EMAIL PROTECTED]) wrote:
> >> As the chances of including a native PA driver in Wine are zero, the
> >
> > Why are those chances zero? I mean, is there an
Lennart Poettering wrote:
> On Wed, 07.05.08 00:43, Tomas Carnecky ([EMAIL PROTECTED]) wrote:
>> As the chances of including a native PA driver in Wine are zero, the
>
> Why are those chances zero? I mean, is there any reason besides that
> noone bothered writing a native driver?
I've heard that
eOn Wed, 07.05.08 00:43, Tomas Carnecky ([EMAIL PROTECTED]) wrote:
>
> Lennart Poettering wrote:
> > I could repeat here what I wrote in response to Nick
> > Thompson. Complaining about Free Software is nothing that makes you
> > any friends in the community.
>
> Fine. I'm complaining. But let m
Lennart Poettering wrote:
> I could repeat here what I wrote in response to Nick
> Thompson. Complaining about Free Software is nothing that makes you
> any friends in the community.
Fine. I'm complaining. But let me tell you this. I dug through the Wine
alsa driver, the alsa pulse plugin and the
On Sat, 03.05.08 15:05, Tomas Carnecky ([EMAIL PROTECTED]) 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'l
On Sun, 04.05.08 14:15, Tanu Kaskinen ([EMAIL PROTECTED]) wrote:
>
> 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 det
On Sat, 03.05.08 23:55, Tanu Kaskinen ([EMAIL PROTECTED]) wrote:
> > Phew. Anyway the second question was not really answered fully. It
> > might be my imprecision in stating the problem so let me try to
> > distill it to the bare bones: For pulseaudio I'd like to know how or
> > if a vir
On Sat, 03.05.08 11:48, Nick Thompson ([EMAIL PROTECTED]) wrote:
> fully accept that my use of pulse might be somewhat unorthodox since
> it is in a speciailsed embedded system, however I also think that
> multiple device support and routing is of great interest, especially
> to the music co
On Fri, 02.05.08 11:27, Matt Patterson ([EMAIL PROTECTED]) wrote:
> So I think what I would do is make a "combined" sink for each class of data
> that routes all audio to all sources. If you disable the module to gets rid
> of idle streams this will leave you with active but corked streams to al
On Fri, 02.05.08 11:01, Nick Thompson ([EMAIL PROTECTED]) wrote:
>
>
> Awesome Matt, if you can share your source I would love to see it.
>
> What you are doing sounds interesting.
>
> For my app I'd like to have two classes of data. For arguments sake
> these are "normal" and "alert". Nor
On Fri, 02.05.08 10:37, Matt Patterson ([EMAIL PROTECTED]) wrote:
> I do agree that coding for pulse can be a steep learning curve, which is
> why I opted to build all my solutions by simply connecting to the text mode
> control socket and sending commands/parsing text output. I have built what
On Fri, 02.05.08 10:20, Nick Thompson ([EMAIL PROTECTED]) wrote:
> OK so I figured out the error of my ways, but I have to say this list is
> pretty unresponsive in helping the community so I have to ask myself "is
> pulse is a sensible choice for audio development today"? Particularly
> sinc
Nikolai Beier wrote:
> 2008/5/4 Tomas Carnecky <[EMAIL PROTECTED]>:
>> Nikolai Beier wrote:
>> > Perhaps Winealsa (the output driver for ALSA) needs direct hardware
>> > access? Or it is/was just coded that way, but does not need to be. Or
>> > it was never a problem?
>>
>> Wine should not need
2008/5/4 Tomas Carnecky <[EMAIL PROTECTED]>:
> Nikolai Beier wrote:
> > Perhaps Winealsa (the output driver for ALSA) needs direct hardware
> > access? Or it is/was just coded that way, but does not need to be. Or
> > it was never a problem?
>
> Wine should not need hardware access. Maybe it mi
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
2008/5/4 Tomas Carnecky <[EMAIL PROTECTED]>:
>
> 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
> >> >>>
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
Thank you, Tanu.
I'll take a look at this way. No doubt I'll have lots of questions
once I get into it.
Regards
Nick
On May 4, 2008, at 4:15 AM, Tanu Kaskinen wrote:
> On Sat, May 03, 2008 at 04:48:05PM -0700, Nick Thompson wrote:
>> Given what you say (above) about per device routing not b
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
> comment
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 slavishl
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
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 mailing
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
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
Hi Tanu,
On May 3, 2008, at 1:55 PM, Tanu Kaskinen wrote:
On Sat, May 03, 2008 at 11:48:04AM -0700, Nick Thompson wrote:
I fully accept that my use of pulse might be somewhat unorthodox
since
it is in a speciailsed embedded system, however I also think that
multiple device support and routin
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 couple weeks, b
On Sat, May 03, 2008 at 11:48:04AM -0700, Nick Thompson wrote:
> I fully accept that my use of pulse might be somewhat unorthodox since
> it is in a speciailsed embedded system, however I also think that
> multiple device support and routing is of great interest, especially
> to the music com
Hi Colin,
On May 3, 2008, at 5:53 AM, Colin Guthrie wrote:
> From what I can tell you've posted a couple questions but answered
> them
> yourself within a day! It's not really fair of you to answer your
> questions yourself so quickly without giving anyone a chance to try
> and
> be helpful :
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 couple weeks, but generally does respond to
Nick Thompson wrote:
> OK so I figured out the error of my ways, but I have to say this list is
> pretty unresponsive in helping the community so I have to ask myself "is
> pulse is a sensible choice for audio development today"? Particularly
> since there is little in the way of useful setup doc
Thanks Matt,
it can wait a day or so!
Nick
On May 2, 2008, at 11:27 AM, Matt Patterson wrote:
> I'm not at home right now, but I will try to remember to forward my
> code tonight or tomorrow morning. If you really can't wait I sent an
> older version to the mailing list a while back, it sho
So I think what I would do is make a "combined" sink for each class of
data that routes all audio to all sources. If you disable the module to
gets rid of idle streams this will leave you with active but corked
streams to all output devices from each sink. You can then update which
streams are
Awesome Matt, if you can share your source I would love to see it.
What you are doing sounds interesting.
For my app I'd like to have two classes of data. For arguments sake
these are "normal" and "alert". Normal audio (mp3, wav, application
data) needs to be routed to the currently select
I do agree that coding for pulse can be a steep learning curve, which is
why I opted to build all my solutions by simply connecting to the text
mode control socket and sending commands/parsing text output. I have
built what is essentially a multiplex audio switch allowing any of x
number input
OK so I figured out the error of my ways, but I have to say this list
is pretty unresponsive in helping the community so I have to ask
myself "is pulse is a sensible choice for audio development today"?
Particularly since there is little in the way of useful setup
documentation for actual
Hi there,
I have a system where I need to move sources to different sinks
according to a policy. I thought I'd try this out using pacmd before
I start trying to code this up with pulse, put pacmd does not behave
as expected (by me :).
I tried the following command in pacmd:
>>> move-si
36 matches
Mail list logo