But when you export a clip, the software has to decode it and then re-encode. When QuickTime Player and other software plays back a video, it decodes the compression, and modern iOS and Mac (and other makers’) devices have built-in chips that handle that decompression for real-time playback, rather than handling it in software. The higher fidelity you want, the more tonal and motion variations are preserved, and the bigger the file.
If a large area of an image or frame is more or less the same blue, with a high level of compression, it becomes all blue and takes just a few bytes to store. In compression, algorithms scan regions of an image or both regions of frames and differences between frames in video to find patterns or approximations. Rob then imported his file into iMovie, chose the lowest resolution of 540p, and got an estimate that the output file would be even bigger: 166.8MB! He asks, “Surely, there must be some catch I don’t know about…” This seems counterintuitive, but it comes from how video files are stored, played back, and export. Rob notes he exported his 720p file at 480p, and got a larger file in result. It’s hard to tell whether this is a bug or an unexplained “feature.” (Apple’s QuickTime documentation is scant.)īut the more significant issue here is what’s missing entirely: export options. Even saving the file immediately and opening that resulting file still shows Save, so I cannot test passthrough trim changes.
#Eyeframe converter files too big movie#
On my Mac, every movie file in any format I open only presents me with File > Save, which indicates the movie has been imported in some form.