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
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:
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
Hallo all,
i hacking currently on cheese and noticed one more performance issue.
i use web cam with sample spec: s16le 1ch 16000Hz, if i start
gstreamer pipe it will get float32le 1ch 44100Hz. I do not see match
sense to upsample stream and than get bigger file size and cpu load.
Especially on
On Sun, 2010-08-15 at 19:30 +0200, Alexey Fisher wrote:
Hallo all,
i hacking currently on cheese and noticed one more performance issue.
i use web cam with sample spec: s16le 1ch 16000Hz, if i start
gstreamer pipe it will get float32le 1ch 44100Hz. I do not see match
sense to upsample
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 is that pulsesrc doesn't use the
proper flags when creating
