Am Mo., 17. Juni 2019 um 11:09 Uhr schrieb Mayescid Ocomance <[email protected]>:
> >> The file is fine, however, when I compare its structure using > >> AtomicParsley to a file with the same specifics but created > >> by another programm, I'm getting way too big moov atoms, > >> which seems to be caused by way too big stscm, stszm, > >> stco, (and ctts for audio) atoms in both streams. > > >How do you define "too big"? > > The files themselves are fine and work well. However, the basically same > files are created by another programm with up to 5 times smaller moov atoms. > The bigger moov atoms don't seem to add any advantage so their size seems > to be redundantly big. How do you know? > Either I need help spotting the advantages or I'd like some help reducing > the moov atom size in order to save data space. Could you elaborate on the numbers a bit? You write above that the moov atoms are five times bigger but what does that mean for the overall file size? Carl Eugen _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
