vaapidecode to xvimagesink

Nicolas Dufresne nicolas.dufresne at collabora.com
Tue Jan 28 11:06:14 PST 2014


Le mardi 28 janvier 2014 à 08:48 -0800, rrazavi a écrit :
> I have written a small code and up to derive image everything is fine but the
> data that I receive for each frame is :
> Width= 1920 Height=816  Data size 2396160---video/x-raw, format=(string)NV12
> 
> The data size is bigger than it should be and it's for a 1920X832 video
> which looks like hardware limitation for lintel GPU.
> When I pass these frames to another pipeline with apsrc the output is not
> correct.

This is fairly common. The output of a decoder is often bigger then what
should be displayed. If downstream sink supports it, you shall attach
crop meta to you buffers (1.X). videoparse won't handle that, so I doubt
it's the ideal solution.

There used to be vaapidownload element to do what you are trying to do.
If that still exist, it would prevent having two pipelines, and also
make sure all caps and meta are passed correctly.

Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140128/6013c6e9/attachment.pgp>


More information about the gstreamer-devel mailing list