Re: [jokosher-devel] Pipeline clock problems

2007-06-19 Thread Laszlo Pandy
John Green wrote: > Attached > > John > I've committed an "Audodetect" option to the recording sample rate combo box which doesn't use caps in the recording pipeline and instead lets gstreamer do its auto-negotiation. This should get rid of a log of recording errors because using gstreamer

Re: [jokosher-devel] Pipeline clock problems

2007-06-14 Thread Laszlo Pandy
Jono Bacon wrote: On 13/06/07, Laszlo Pandy <[EMAIL PROTECTED]> wrote: That's exactly right. We hide all of the rates in the preferences dialog that your sound card has told us it won't accept. If 44100 is still an option, your sound card is a liar. I am wondering if this issue is ALSA telling

Re: [jokosher-devel] Pipeline clock problems

2007-06-14 Thread Jono Bacon
On 13/06/07, Laszlo Pandy <[EMAIL PROTECTED]> wrote: > That's exactly right. We hide all of the rates in the preferences dialog > that your sound card has told us it won't accept. If 44100 is still an > option, your sound card is a liar. I am wondering if this issue is ALSA telling lies about soun

Re: [jokosher-devel] Pipeline clock problems

2007-06-13 Thread Laszlo Pandy
John Green wrote: > 0:00:00.272167000 26312 0x804f070 WARN alsa > gstalsasrc.c:428:set_hwparams: error: Rate doesn't match > (requested 44100Hz, get 0Hz) I'm wondering if there is a way to catch this specific error and blacklist the specific audio rate. Bilboed, is that possible?