Le mercredi 13 janvier 2016 à 16:04 +0100, Sebastien LEDUC a écrit : > Hi all > I have seen on the linuxTV web site that there were some on-going > discussions related to the Codec API. > > In our SoCs, it is the HW encoder that is outputting both the slice > data and the headers/metadata, but it does it using separate buffers. > > So we are looking at how to expose that using V4L2 APIs. > > We were thinking that we could use the MPLANE apis to achieve that, > where one plane would contain the header/metadata and another one > for the slice data. > > Any opinion on this ? Discussion I had regarding this kind of integration, whether it was about non-parsing decoder or slice encoder, is that two planes shall be used (mplane API will allow seperate allocation of those planes). About slice encoder, a lot of specification work is needed. I believe the hardest part and what no one could agree on, is the data structure standard that would be used to represent the required metadata and headers. In the end, libv4l should probably have some new feature to transform slice encoded data into byte-stream so existing software can use those encoder without porting. cheers, Nicolas
Attachment:
signature.asc
Description: This is a digitally signed message part
