[FFmpeg-devel] API for CrystalHD

Gwenole Beauchesne gbeauchesne
Fri Mar 26 15:14:56 CET 2010


Hi,

Le 26 mars 10 ? 14:05, Luis Moreira a ?crit :

> I am working on the development of an API for CrystalHD. Could someone
> describe the main purpose of each of the functions start_frame,  
> decode_slice
> and end_frame in hardware decoding? It would much easier if
> someone described that for me.

Some quick notes.

1) Use/fix/improve the v2 proposal:
<http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-January/080487.html 
 >
While looking for the link, I noticed I missed some comments from  
Michael, so you could have a look a it too.

2) Some NV12 fixes:
<http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-February/083566.html 
 >
IIRC, Stefano committed the GRAY8 change, so we probably can just use  
the usePal() as Michael suggested.

3) Extend the v2 API with another hook to notify the HWAccel about  
extra information. e.g.
int (*header)(AVCodecContext *avctx, const uint8_t *buf, uint32_t  
buf_size);

This is needed to pass on H.264 PPS/SPS bits for example. CrystalHD  
wants the whole bistream, it's not frame based. If you want to add  
Crystal HD support to your application quick, just use the FFmpeg  
demuxers and send the result to the HW. i.e. have a look at the XBMC  
code.

4) Implement Crystal HD support. That should be simple with the things  
mentioned above.

Regards,
Gwenole.



More information about the ffmpeg-devel mailing list