Issue 191 in ffmbc: Output Quicktime Clips Have Very Small (1 Frame) Chunks, Expensive for Playback

[ff...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 191 by benjamin...@gmail.com: Output Quicktime Clips Have Very
Small (1 Frame) Chunks, Expensive for Playback
https://code.google.com/p/ffmbc/issues/detail?id=191

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.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ff...@googlecode.com]

Updates:
Status: WontFix

Comment #1 on issue 191 by baptiste...@gmail.com: Output Quicktime Clips

Have Very Small (1 Frame) Chunks, Expensive for Playback
https://code.google.com/p/ffmbc/issues/detail?id=191

Loading an entire index in today's machines is a piece of cake