Help on some issues / Porting Flumotion

[Max Sarajlija]

Hi Tim,

If you want a GstEvent, you can get it from the probeinfo (after checking
> that the type is actually an event).


How can i get a GstEvent from probeinfo?

Thanks,

Max


On Sun, Jul 21, 2013 at 8:44 PM, Tim-Philipp Müller <t.i.m at zen.co.uk> wrote:

> On Sun, 2013-07-21 at 16:25 +0200, Max Sarajlija wrote:
>
> Hi Max,
>
> > I'm porting Flumotion for the new GStreamer (in PyGi) and i stumbled
> > upon some things i can't resolve on my own. I've posted more about
> > this here: http://portingflumotion.blogspot.com/
>
> About http://portingflumotion.blogspot.co.uk/2013/07/analyzing.html :
>
> First of all, calling a GstProbeInfo structure 'event' is a very bad
> idea, and makes everything even more confusing than it already is. Call
> it probeinfo instead. If you want a GstEvent, you can get it from the
> probeinfo (after checking that the type is actually an event).
>
> Then pass the *event* to event_is_flumotion_reset(), not the
> *probeinfo*.
>
> (python 0 : C 1 ;))
>
> 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/20130722/77362934/attachment.html>