On Tue, 2009-10-20 at 12:26 +0800, Ng Oon-Ee wrote:
Quick suggestion, in latest pulse and latest jack pulse will give up
control of the audio hardware when Jack starts (as informed by dbus) and
grab control back once Jack stops. Could module-jack-sink and
module-jack-source also be
'Twas brillig, and Ng Oon-Ee at 20/10/09 07:26 did gyre and gimble:
On Tue, 2009-10-20 at 12:26 +0800, Ng Oon-Ee wrote:
Quick suggestion, in latest pulse and latest jack pulse will give up
control of the audio hardware when Jack starts (as informed by dbus) and
grab control back once Jack
Hallo,
i played a bit with pa and have question:
I know pa will resample stream if my src use 44100Hz and my sink need
16000Hz, so it take some cpu (~10%) time. Why it take so mach CPU even
if src and sink are same? On play back with sink=src pa almost not use
cpu, why on record?
And one more
Ok, let see, I have finally made it work.
However, I have another drawback. Since I am using the audio stream to be
multiplexed with video with ffmpeg, I have noticed that when sending audio,
ffmpeg works at a normal codifying rate. However, when having silence, it
works at a slower rate, and
On Tue, 20.10.09 12:24, Alexey Fisher (bug-tr...@fisher-privat.net) wrote:
Hallo,
i played a bit with pa and have question:
I know pa will resample stream if my src use 44100Hz and my sink need
16000Hz, so it take some cpu (~10%) time. Why it take so mach CPU even
if src and sink are same?
On Tue, 20.10.09 12:26, Ng Oon-Ee (ngoo...@gmail.com) wrote:
Quick suggestion, in latest pulse and latest jack pulse will give up
control of the audio hardware when Jack starts (as informed by dbus) and
grab control back once Jack stops. Could module-jack-sink and
module-jack-source also be
'Twas brillig, and Leszek Koltunski at 20/10/09 16:20 did gyre and gimble:
Seems to me that 'pax11publish' disregards the screen number given in
its -D parameter and only pays attantion to the X server number.
for every N, pax11publish -D :0.N overwrites the X11 properties of
0.0.
Did you
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client libs are doing the same...)
Doesn't 0.0 and 0.1 mean there's only
'Twas brillig, and Michał Sawicz at 20/10/09 17:32 did gyre and gimble:
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client
My 2 cents. I'm a big pulseaudio fan, and I love what it gets me in my
desktop experience.
Unfortunately, the ill-informed rants are informed about their personal user
experience. There's a lot of people who were really peeved at what
pulseaudio has done to their user experience, and they see
On Mon, Oct 19, 2009 at 12:16 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
You'll no doubt be aware, but:
http://linux.slashdot.org/story/09/10/19/0155235/PulseAudio-Creator-Responds-To-Critics
It's full of the usual ill informed rants, but obviously user experience is
a tough one to judge
On Tue, Oct 20, 2009 at 3:20 PM, Jeremy Nickurak
pulseaudio-disc...@trk.nickurak.ca wrote:
Maybe the distributions broke it, and have never really fixed it (Ubuntu
certainly isn't following the Perfect Setup advice, even in karmic AFAICT.
Audio goes to pulse if and only if it the app expressly
Please fix you're broken lineends.
'Twas brillig, and Markus Rechberger at 20/10/09 21:03 did gyre and gimble:
I'm also using pulseaudio for one of my product actually (just because
the devices we ship have
to work without altering the installed system).
As I've explained on numerous
On Tue, Oct 20, 2009 at 11:00 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
Please fix you're broken lineends.
'Twas brillig, and Markus Rechberger at 20/10/09 21:03 did gyre and gimble:
I'm also using pulseaudio for one of my product actually (just because
the devices we ship have
to work
2009/10/20 Daniel Chen seven.st...@gmail.com:
On Tue, Oct 20, 2009 at 3:20 PM, Jeremy Nickurak
pulseaudio-disc...@trk.nickurak.ca wrote:
Maybe the distributions broke it, and have never really fixed it (Ubuntu
certainly isn't following the Perfect Setup advice, even in karmic AFAICT.
Audio
On Tue, Oct 20, 2009 at 14:16, Daniel Chen seven.st...@gmail.com wrote:
On Tue, Oct 20, 2009 at 3:20 PM, Jeremy Nickurak
pulseaudio-disc...@trk.nickurak.ca wrote:
Maybe the distributions broke it, and have never really fixed it (Ubuntu
certainly isn't following the Perfect Setup advice,
On Tue, 2009-10-20 at 16:45 +0200, Lennart Poettering wrote:
On Tue, 20.10.09 12:26, Ng Oon-Ee (ngoo...@gmail.com) wrote:
Quick suggestion, in latest pulse and latest jack pulse will give up
control of the audio hardware when Jack starts (as informed by dbus) and
grab control back once
Hi,
I'm not completely 100% sure about this yet (had one confirmation of it,
but waiting for two others to get back to me), but I've been tracking a
problem relating to SIMD for a while in:
https://qa.mandriva.com/show_bug.cgi?id=53870
It's hardware dependant and my hardware is not affected,
On Tue, Oct 20, 2009 at 6:16 PM, Jeremy Nickurak
pulseaudio-disc...@trk.nickurak.ca wrote:
Is this actually the case? I've always modified /etc/asoundrc or ~/.asoundrc
to get applications working as expected, but maybe that's redundant now.
Yes, it has been redundant since Intrepid/8.10 (cf.
19 matches
Mail list logo
