feeding images to imagefreeze
Brian McKeon
brian.dev.address at gmail.com
Wed Feb 6 06:15:20 PST 2013
Hi Tim,
My pipeline is very basic at the moment because I wanted to start with a
proof of concept.
It looks like:
appsrc ! decodebin ! imagefreeze ! autovideosink
And let me restate my goal to try to add clarity:
My code is sent a jpeg image every so often. (i.e. the input isn't
continuous. New images can arrive at any time.)
I need to take this single image and create a continuous output stream
with it. Very much like what imagefreeze does.
This approach is currently working, but only for the very first image I
receive.
Every image after that gets enqueued into the appsrc element, but those
buffers never get pulled into the output stream. So the output just
keeps showing the first image.
I was really hoping there was a simple way to trigger the imagefreeze
element to tell it to pull the next buffer from appsrc.
Hopefully that makes more sense. But if not, please let me know and I'll
provide more info.
Thanks!
Brian
On 2/6/13 8:46 AM, Tim-Philipp Müller wrote:
> On Wed, 2013-02-06 at 07:25 -0500, Brian McKeon wrote:
>
> Hi Brian,
>
>> I'm hoping someone with more experience can point me in the right
>> direction.
>>
>> I'm trying to push jpeg images into a gstreamer pipeline. When an
>> image gets put into the pipeline, I want it to stream that image until
>> I signal the pipeline to pull the next image, and so on.
>>
>> My python code copies each image into a gstbuffer and pushes that into
>> an appsrc element. The appsrc element then feeds into a decoder and
>> then into an imagefreeze element.
>>
>> It works fine, except that I can't make the imagefreeze element pull
>> additional buffers from appsrc.
>>
>> As soon as it has one buffer, it doesn't pull any others. The buffers
>> just queue up in the appsrc element with nowhere to go.
>>
>> Ideally I'd like to be able to send a signal to imagefreeze to tell it
>> when to pull the next image buffer from appsrc. But I haven't been
>> able to find anyway of accomplishing this.
>>
>> It occurred to me that maybe imagefreeze wasn't designed for this
>> purpose and that I may need to go into the source code and add this
>> feature myself.
>>
>> But I first wanted to check with everyone to see if there's an easier
>> way of accomplishing this.
> What's your whole pipeline like? (Since you say "stream" the image)
>
> Cheers
> -Tim
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
More information about the gstreamer-devel
mailing list