Hi!
If you want me to forward this bug to other FFmpeg developers, please:
* Provide sample(s) that allow to reproduce the issue
and
* The ffmpeg command line that allows to reproduce the issue together with
the complete, uncut console output
and
* explain what is wrong with the output file.
If you cannot (or don't want to) provide all three, I suggest to close
this bug because I don't see how it can be fixed without it.
(Or at least it wouldn't be known on this bug tracker if the issue ever
gets fixed.)
If the issue is not reproducible with the ffmpeg command line tool but
only for an API user, things get more complicated but in this case you
should try hard to rule out a bug in the tool using the API.
Carl Eugen
