...
|
...
|
@@ -252,7 +252,8 @@ See also the @ref{framemd5} muxer.
|
252
|
252
|
The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
|
253
|
253
|
file has all the metadata about all packets stored in one location
|
254
|
254
|
(written at the end of the file, it can be moved to the start for
|
255
|
|
-better playback using the @command{qt-faststart} tool). A fragmented
|
|
255
|
+better playback by adding @var{faststart} to the @var{movflags}, or
|
|
256
|
+using the @command{qt-faststart} tool). A fragmented
|
256
|
257
|
file consists of a number of fragments, where packets and metadata
|
257
|
258
|
about these packets are stored together. Writing a fragmented
|
258
|
259
|
file has the advantage that the file is decodable even if the
|
...
|
...
|
@@ -310,6 +311,10 @@ more efficient), but with this option set, the muxer writes one moof/mdat
|
310
|
310
|
pair for each track, making it easier to separate tracks.
|
311
|
311
|
|
312
|
312
|
This option is implicitly set when writing ismv (Smooth Streaming) files.
|
|
313
|
+@item -movflags faststart
|
|
314
|
+Run a second pass moving the moov atom on top of the file. This
|
|
315
|
+operation can take a while, and will not work in various situations such
|
|
316
|
+as fragmented output, thus it is not enabled by default.
|
313
|
317
|
@end table
|
314
|
318
|
|
315
|
319
|
Smooth Streaming content can be pushed in real time to a publishing
|