Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Old .Mov files converting

I have old .mov files from '03. When I open them on Mavericks with the latest Quicktime, it says "converting" and it takes a very long time to convert the files. So I let it. Once the file is converted its size blows up. I believe I had a 40min .mov video tutorial that was like 200mb in size, once converted it became an 8gb file!!


I have 20GB of backed .mov files if I convert them all it will become Terabytes of data. What is the problem and how can I solve it? I opened the original files using VLC and it worked fine.

MacBook, Mac OS X (10.7)

Posted on May 21, 2015 9:30 AM

Reply
23 replies

May 30, 2015 10:31 AM in response to kingmohd

I tried the finder converter, while the size of the file remained the same the dimensions of the video has been altered. I chose 480p.

This video is an Adobe Flash Tutorial so it was captured in full screen size. Dimensions on the file says 1000X700. How can I get the correct dimensions?


Also, the codecs says : Animation, AAC


not sure if this helps

Am somewhat confused by your workflow. Can you open both the original source file and your "converted" file in one of the QT media players, capture an image of the "Inspector" window for each, and then post the images here?


If you ended up with a 480p Animation/AAC file that is the same size in terms of storage space, then it sounds as if no conversion took place. Unfortunately, Apple decided to merge the QT 7 Pro "Save", "Save As...", and "Export" File menu options into a single QT X "Save" option which may have been used by the Finder "Convert" framework. (Yet another reason I'm still using QT 7 Pro so I can manually select a specific action in such cases.) Basically, it sounds as if the the "Convert" framework simply copied the original data to a secondary file unchanged and rescaled the display. Not sure if you mean by "correct dimensions" here—i.e., rescale the dimensions back to "full screen", change the aspect ratio, or remove letterboxing or pillaring of content.


In any case, the animation codec is very fast but not efficient in terms of file storage space. If I create a Animation/LPCM 1080p24 file on my systems, let the codec run at full speed, and save the data to my internal drive, the file space required to store the content can be as high as 6 MB/min—higher targeting my Thunderbolt Pegasus RAID unit. This codec is very good for archiving/editing your source file but should not be used as the compression format for your final file. In this case, you would most likely want to convert the content to a highly efficient compression format like H.264/AAC for normal use and which would require only a fraction of the storage space required for the Animation video codec.

User uploaded file

May 30, 2015 10:41 AM in response to kingmohd

I tried hand brake, its worked perfect, the video output is even 18% smaller than the original!

That would be my optimum preference here. I normally use it to reduce 1080p 20-30 Mbps BD files to more reasonable anamorphic H.264/AAC/AC3/Chaptered 720p24 files having data rates in the 2.5 to 4.0 Mbps range (or roughly 1/5th to 1/12th their original file size) that are compatible with all my Apple OS/IOS devices.

User uploaded file

May 30, 2015 5:06 PM in response to Jon Walker

If I create a Animation/LPCM 1080p24 file on my systems, let the codec run at full speed, and save the data to my internal drive, the file space required to store the content can be as high as 6 MB/min—higher targeting my Thunderbolt Pegasus RAID unit.

Oops! The "6 MB/min" above should have read "6 GB/min" or a data rate on the order of 750 Mbps.

User uploaded file

Jun 6, 2015 7:12 AM in response to kingmohd

The screenshot are here as you requested... There is something weird that happened. Although the handbrake conversion reduced the file size sometimes down to 33% , it also looks sharper but even the colors are different. Do you know why this happens? Look at the image comparing the 2.

Not feeling my best, but I will try to answer as best I can. Basically, there are a number of different things at work here: color space, chroma subsampling, and dimension issues.


QT tracks three forms of dimensions:

  1. The dimensions at which a file is encoded,
  2. The normal dimensions at which the file opens for display, and
  3. The file's current display dimension.

These attributes can range from non-anamorphic, unscaled file in which all attributes are the same to an anamorphic file which has been manually scaled for display and in which all of the attributes are different. In the case of the Screen Capture you created a non-anamorphic file using your screen dimensions for all three settings. When you used the automatic settings in the QT X player to convert the screen capture file, it select the "Greater Quality" encode settings and the 720p dimensions setting because the 750p source was less than 1080p but greater than 720p. On the other hand, you did not reset the dimensions for either the QT 7 or the HandBrake conversions so the original 1000x750 source file dimensions were passed to the converters unchanged. As to the Finder Conversion, you did reset the dimensions (or left the default 480p setting unchanged) which scaled down the file dimensions to 640x480 and tends to sharpen the original image as blown up for full screen capture. As to the HandBrake, if you used one of the Level 4.1 presets, that could account for its improved sharpness


With regard to the color shift, your animation file was encoded in the RGB color space while I believe all of your other files are in the YUV color space with the ProRes 4444 probably using 4-2-2 chroma subsampling and all of the H.264 file probably using 4-2-0 chroma subsampling and thus probably demonstrating the most color shift. (But I can't really be certain without examining the files themselves.)


Before I can make any further recommendations I must know what the actual goals of your workflow are and in what prioritized order. Since file sized and display sharpness are directly related to the encoding dimensions, what minimum display dimensions are we looking at? How important is the color shift? Must the target output files be QT X and QL compatible? Will the final file use support an anamorphic workflow? Will you be keeping the Animation file as an Archival copy? What do you plan to do with or how do you plan to use the converted file (archival or distribution use)? etc., etc., etc.

User uploaded file

Old .Mov files converting

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.