What steps will reproduce the problem?
1. Wrap any content in a Quicktime .mov wrapper using FFmbc.
2. Note that each chunk in the resulting Quicktime file contains only 1 frame
(this is easily seen by looking at the 'co64' atoms).
What is the expected output? What do you see instead?
Chunks in Quicktime are intended to help optimize file access, but if each
chunk only contains 1 frame then that doesn't help a parser very much. Apple
FinalCut Pro typically encodes 1 chunk per 1/2 second of content, which is much
better for helping optimize parsing. As they are currently, FFmbc-created
Quicktime files are very resource-intensive to play.
Would be nice if FFmbc defaulted to 1/2-second chunk sizes to match FinalCut
Pro, and/or provided a configuration option to set chunk size.
What version of the product are you using? On what operating system?
0.7-rc8 on Fedora 19 (x86)
Please provide any additional information below:
A number of our customers have encountered problems relating to very expensive
playback of FFmbc-created content.
Original issue reported on code.google.com by benjamin...@gmail.com on 7 Nov 2014 at 11:57
Original issue reported on code.google.com by
benjamin...@gmail.com
on 7 Nov 2014 at 11:57