[FFmpeg-devel] [PATCH] Interlaced encoding for ProRes

[Michael Niedermayer]

On Mon, Aug 13, 2012 at 05:01:08PM +0200, Michael Niedermayer wrote:
> On Mon, Aug 13, 2012 at 11:13:46AM +0200, Boris Maksalov wrote:
> > 
> > 
> > 12.08.2012, 19:09, "Michael Niedermayer" <michaelni at gmx.at>:
> > > Hi
> > >
> > > On Fri, Aug 10, 2012 at 03:30:51PM +0200, Boris Maksalov wrote:
> > >
> > >>  Hi,
> > >>
> > >>  I've implemented interlaced encoding for ProRes.
> > >>  To activate interlaced mode, pass -flags +ildct
> > >>
> > >>  The first patch fixes a pre-existing bug where incomplete macroblocks were partially filled with memory read past the end of frame buffer. This can be verified with valgrind. The second patch actually implements interlaced encoding.
> > >>
> > >>  I do realize 'prores_kostya' encoder originates from libav and I did contact its author first, but things are moving quite slow on the libav side, so I am submitting my patches here.
> > >
> > > interlaced prores encoding support is welcome on the ffmpeg side.
> > > I would have preferred it in anatolies encoder though as i dont want to
> > > compete with kostya in maintaining his encoder but that wont stop me
> > > from applying a patch that adds an important feature.
> > I chose to modify Kostya's version as it has (some) multithreading support unlinke Anatoly's version.
> 
> hmm
> 
> ffmpeg -i matrixbench_mpeg2.mpg -y -vcodec prores_kostya -threads 1 test.mov
> results in 24fps encoding
> 
> ffmpeg -i matrixbench_mpeg2.mpg -y -vcodec prores_kostya -threads 12 test.mov
> results in 66fps encoding
> 
> ffmpeg -i matrixbench_mpeg2.mpg -y -vcodec prores -threads 1 test.mov
> results in 84fps encoding
> 
> so id say anatolies encoder does quite well without threads

ffmpeg -i matrixbench_mpeg2.mpg -y -vcodec prores -threads 12 test.mov
makes 390fps now (and same SHA1 on the output as anatolies encoder
with threads 1 before)

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored awnser#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20120813/ce18444c/attachment.asc>