Re: [jokosher-devel] Pipeline clock problems
- From: Laszlo Pandy <laszlok2 gmail com>
- Cc: Jokosher gnome <jokosher-devel-list gnome org>, John Green <john green uk googlemail com>
- Subject: Re: [jokosher-devel] Pipeline clock problems
- Date: Fri, 15 Jun 2007 00:42:39 -0400
Jono Bacon wrote:
On 13/06/07, Laszlo Pandy <laszlok2 gmail com> 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 sound card
capabilities which GStreamer honestly reports, or whether GStreamer is
buggy. I do remember some issues with this around the 0.2 development
schedule, and I seem to remember ALSA being the source the issues.
I think changing to PAUSED might be a good test too. :)
Jono
While debugging a "The stream is in the wrong format; Check your
filtered caps, if any" using a log that gavin on IRC gave me I stumbled
across a possible bug in our audio rate detection algorithm, which could
be causing the wrong detection in the Suse on VMWare.
John, can you run the attached script on your Suse VM and email me back
the output, so I can see if they are related?
Laszlo
import gst
src = gst.element_factory_make("alsasrc")
print "STATE_READY src caps:"
print src.get_pad('src').get_caps().to_string(), "\n\n"
print "Changing state..."
print src.set_state(gst.STATE_PLAYING), "\n\n"
print "STATE_PLAYING src caps:"
print src.get_pad('src').get_caps().to_string(), "\n\n"
print "done."
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]