Probing for caps change

Nox Deleo noxdeleo at googlemail.com
Sat Jan 5 07:34:18 PST 2013


Tried setting 'do-timestamp' on the appsrc to true...didn't seem to make a
difference. It's an intermittent issue...like some race condition that's
stopping samples being sent. I put a print statement in every time I send a
buffer, and sometimes they just stop when I'm setting caps alongside, but
not if I do it through the event probe. Debugging doesn't seem to show
anything useful. Maybe doing this asynchronously through signals in Python
is just asking for trouble. Here's the source: http://pastebin.com/b1cbG8YC.
Appreciate the help.


On 5 January 2013 14:54, Tim-Philipp Müller <t.i.m at zen.co.uk> wrote:

> On Sat, 2013-01-05 at 14:44 +0000, Nox Deleo wrote:
>
> > That's what I was doing originally, but it was causing weird things to
> > happen. Occasionally I'd stop hearing any audio mid-track. Sometimes
> > it would stop on the next track after it changed. Sometimes I hear
> > nothing from the start. Probably something I've screwed up.
>
> That might be related to the timestamps on the buffer, which you'll have
> to adjust yourself (unless you let appsrc do the timestamping), since
> they'll start at 0 again when a new track plays (well, it depends on
> what exactly you're doing, if the streamsynchronizer in playbin kicks in
> or not etc.)
>
> Cheers
>  -Tim
>
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20130105/383e7f57/attachment.html>


More information about the gstreamer-devel mailing list