On Mo, 2010-08-16 at 07:58 +0300, Tanu Kaskinen wrote:
Correcting myself:
On Mon, 2010-08-16 at 06:42 +0300, Tanu Kaskinen wrote:
I guess the problem is that pulsesrc doesn't know
which source is going to be used before actually starts recording.
No, that's not the problem. The problem
Hi,
As some of you will have found out, there are some applications that
have problems relating to Xlib usage (XCloseDisplay() IIRC) when
combined with PA client libs (notably I've seen reports from VLC
relating to this).
I've therefore committed a patch I wrote a while back to stable-queue
that
On Mon, 2010-08-16 at 06:42 +0300, Tanu Kaskinen wrote:
I guess the problem is that pulsesrc doesn't know
which source is going to be used before actually starts recording.
No, that's not the problem. The problem is that pulsesrc doesn't use the
proper flags when creating the stream:
The next stream type should be a pulse audio internal type(s) used for
the mixing of mp3/ac3 and perhaps dts streams. It's my understanding
that ac3 uses vectors to describe 6 channels of sound much like a 2ch
mp3. If I'm not mistaken these vectors can be combined mathematically
as-is to
On Mo, 2010-08-16 at 09:06 -0500, pl bossart wrote:
On Mon, 2010-08-16 at 06:42 +0300, Tanu Kaskinen wrote:
I guess the problem is that pulsesrc doesn't know
which source is going to be used before actually starts recording.
No, that's not the problem. The problem is that pulsesrc
We had a problem with PA a few days ago which I analyzed as the following:
PA started up for the first time, i e without a .pulse directory.
Due to racy startup conditions (we're all trying to boot up as quick as
possible nowadays), sometimes the start order was as follows:
1) Sound card #2
This is a known issue with module-loopback. If you look at this part
of the log, you'll see that there's something really wrong with how
the sample-rate is set:
I: module-loopback.c: Old rate 43236 Hz, new rate 43300 Hz
I: module-loopback.c: Loopback overall latency is 99.98 ms + 806.05 ms +
'Twas brillig, and David Henningsson at 16/08/10 20:38 did gyre and gimble:
We had a problem with PA a few days ago which I analyzed as the following:
PA started up for the first time, i e without a .pulse directory.
Due to racy startup conditions (we're all trying to boot up as quick as
