[FFmpeg-devel] [PATCH] Generic part of frame multithreading

Uoti Urpala uoti.urpala
Fri Aug 22 09:50:36 CEST 2008

On Fri, 2008-08-22 at 00:28 +0200, Michael Niedermayer wrote:
> On Fri, Aug 22, 2008 at 12:23:04AM +0300, Uoti Urpala wrote:
> > Yes you need to be more careful if you use void * with allocated memory.
> > But you do need something like that if you have more than 64 bits of
> > data per frame. And in that case not having support for void * only adds
> > even _more_ complexity. You can't make all user data fit into one data
> > type by not supporting the others. You're not helping reduce complexity,
> > you're only burying your head in the sand and denying that complexity
> > exists.
> Please dont troll.
> If you know of a specific case where the existing system is insufficient
> you can tell us so it can be considered. If not theres no point in generically
> telling us if X then Y with a X that isnt true ...

If you have any other data about the frame besides pts, so you can not
fit it all directly in the field. It shouldn't be too hard to think of
information you could have. For example coded frame size (if you want to
see how much bitrate various parts are using) or the approximate
user-timeline timetamp from DVDs.

More information about the ffmpeg-devel mailing list