[FFmpeg-devel] [PATCH] CrystalHD decoder support v2

Philip Langdale philipl
Fri Jan 7 17:32:09 CET 2011


 On Fri, 07 Jan 2011 15:23:01 +0100, Vladimir Pantelic 
 <vladoman at gmail.com> wrote:
> Vladimir Pantelic wrote:
>
> so, you pass a timestamp here:
>
> ret = DtsProcInput(dev, avpkt->data, len, pts, 0);
>
> and you get it back (hopefully unchanged) from here:
>
>  	output->PicInfo.timeStamp
>
> right?
>
> so, you have a way to identify a returned frame from this value
> which means you have a way to return the value of reordered_opaque
> as well. And as said, you cannot assume that reordered_opaque is
> a timestamp, it could be anything:
>
>     /**\
>      * reordered opaque 64bit (generally an integer or a double
> precision float\
>      * PTS but can be anything). \
> ...
>
>
> btw, does the decoder actually use the "pts" value you pass? does it
> break decoding
> if you pass e.g. 1, 2, 3, 4, 5 etc?

 I implemented a remapping mechanism last week:

 https://github.com/philipl/ffmpeg-crystalhd

 This does work - it's just that you have to use units of 100000 rather 
 than
 1,2,3,etc.

 Thanks,

 --phil



More information about the ffmpeg-devel mailing list