Sent on the go...

> On 19 Feb 2015, at 18:35, Michael Niedermayer <michae...@gmx.at> wrote:
> 
> theres no encoder, the data could instead come from another mov
> file or a binary encoder used by some user application with
> libavformat

Michael,

Thanks for your response, I must be confused then. What I thought was based on 
the following.

I have say a set of image files that I want to encode as dnxhd in QuickTime, so 
ffmpeg sets up the encoder, and during each image's encoding the encoder needs 
some information such as if the movie is encoded with interlaced fields, and 
also the specifics of the resolution and bit rates there's a codec/compression 
Id associated with those settings. When writing the avid atoms, they also 
should have those same values encoded in them.

This is important as if instead of starting from image files we start from an 
existing movie with the atom present, we would not want to use values based on 
that atom, which is what s currently done, I wanted to find the dnxencoder 
structure to correctly populate the atom.

Kevin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to