Suvarna1488 / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

decoder: better integration with arbitrary strides #988

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
With the new VPX_CODEC_CAP_EXTERNAL_FRAME_BUFFER capability it is possible for 
the decoder to use memory allocated externally. While it allows having the 
decoder write directly to the rendering library memory, it is still missing 
more flexible stride requirements to avoid having to copy frames to different 
layouts.

It would be nice to allow not only providing memory for decoding, but also 
specifying the strides to be used (that can be obtained from the rendering 
libraries) so that decoding already writes to the rendering memory in the 
correct layout it expects.

This is also solvable (and maybe preferable as a more generic approach) by 
allowing the application to specify pointers to each plane memory to be used 
along with the strides to avoid the restriction of having to have a single 
block of memory for the whole frame.

Original issue reported on code.google.com by thiagoss...@gmail.com on 17 Apr 2015 at 6:15

GoogleCodeExporter commented 9 years ago
For example the vpx_image_t type could be reused here

Original comment by sl...@coaxion.net on 17 Apr 2015 at 6:16