Problem with the same custom element multiple times
swestrup at gmail.com
Mon Jun 29 14:09:21 PDT 2015
I can't really help without knowing any more about the APIs involved than
you've mentioned. Basically, it looks like you are using a badly-built
commercial library, and i would look for something less badly built.
On Fri, Jun 26, 2015 at 10:35 AM, Totoketchup <anthony.damato at hotmail.fr>
> Hi, thank you for your detailed answer.
> The main problem is that I can't modify what the module entry is, so I
> can't send my GstBuffer to it. This eliminates the a) solution. Secondly, I
> can't modify what this module is doing with the raw data. This eliminates
> the b). The c) is the solution I was thinking about yes :)
> But when I have the timestamps information how can I give it to the new
> GstBuffer ?
> Le 26 juin 2015 16:38, "Stirling Westrup [via GStreamer-devel]" <ml-node+[hidden
> email] <http:///user/SendEmail.jtp?type=node&node=4672479&i=0>> a écrit :
> On Thu, Jun 25, 2015 at 4:29 PM, Totoketchup <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4672473&i=0>> wrote:
> Hi !
> My element (TetrysElement) adds redundancy (linear combination between
> packets) and adds a header (to distinguish each packet during the
> But, I have to "break" the structure of the GstBuffer in the chain loop to
> send the data to another module. When the module has finished, he sends
> in a callback function the data with header and the redundancy packet. Then
> I create a new GstBuffer that I fill with this and I send it to the next
> element. But during this 'travel', I have lost the timestamps information.
> Do you know how can I have it back ?
> I don't see how this is even a problem. You can solve this any number of
> ways, by just including the timestamp data in the round trip. This could be
> any one of
> a) Send the GstBuffer to the redundancy module, and it builds and
> returns a GstBuffer with the new data and timestamps transferred over.
> (this is what I would do).
> b) Include the timestamps in the raw data you send to the redundancy
> module, and have it return them in its callback.
> c) Hold onto the original buffer and its data until the callback,
> associate them somehow, and build a new GstBuffer using the saved data and
> the callback data. I would only recommend this if the redundancy module is
> an opaque library with a bad interface (ie, no round trip of user data).
> Stirling Westrup
> Programmer, Entrepreneur.
> gstreamer-devel mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4672473&i=1>
> If you reply to this email, your message will be added to the discussion
> To unsubscribe from Problem with the same custom element multiple times, click
> View this message in context: Re: Problem with the same custom element
> multiple times
> Sent from the GStreamer-devel mailing list archive
> <http://gstreamer-devel.966125.n4.nabble.com/> at Nabble.com.
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel