Q: older videos will not play on quicktime

I have many videos on a website created with final cut express and older versions of iMovie. These movies were put in quicktime format. Only older versions like 7.5.5 will work. The newer version of quicktime will not work. It is not possible to recreate all these videos nor is it reasonable to ask any viewer to download an older version of quicktime. Is there some fix for this I can do on my end beyond redoing all the videos?

What you can do primarily depends on the codecs used for export and how you are trying to distribute/access the online content. FCE content exported using "pro" codecs will only play on systems configured with these same  "pro" codecs. iMovie files exported using legacy codecs will only play in a legacy compatible player while current QT X players will automatically attempt to convert them to more modern compression formats if possible. All MOV files are "QuickTime" files. This means that any MOV files containing WMV3/WMA, DivX/MP3, muxed MPEG2/DTS, etc encoded A/V data are still "QuickTime" files even if they cannot be played natively in a QT media player.

Basically you have two options. The first, as you have already noted, is to transcode your unsupported content to compression formats that are natively supported by the current QT X structures embedded in Mavericks, Yosemite, and (I assume) El Capitan . The second option is to play the files in their current form using a compatible media player. Most people use VLC as a free third-party legacy player (since it contains its own independent codec support) and QT 7 to access legacy and/or "pro" codecs for which the system is/can be configured. In addition, depending on how your online videos are accessed/played, you may need to do some web site recoding.

Can't believe they would make it where previous files will not play.

Contrary to what many users believe, when Apple re-wrote the QT support structures, they actually implemented an entirely new version of their media playing software along with the turning off of active support for codecs to be dropped along with the rewriting of associated core audio/video rendering support beginning with Lion and mostly completed under Mountain Lion as a prelude to the release of Mavericks and its division of QTX/QT7 into totally separate support structures which is the source of your current problem. While I agree that it might be nice to still support legacy formats even though I don't use them, I am really much more interested in QT X's potential to support transport stream files, AC3 audio (eventually DTS natively?), 2K, UHD, 4K and whatever else may follow with introduction of higher efficiency/higher definition capable compression formats. In short, Apple, like most modern multimedia purveyors, is moving to the use of a few highly scaleable codecs capable of handling multiple targeted uses rather than the support of a large number of codecs with each having a single targeted use—i.e., the consolidation of codec resources to improve the resourcing of codec support.

Having said that I would like to be able to convert these MOV files so they will play with the present version of quicktime. I do not know how to do that. Can you help me with this.

Without information regarding what codecs were used to generate the files you now wish to transcode, how efficient the codecs are, how compressed the data is, what strategies and settings were used (e.g., anamorphic/non-anamorphic, interlaced/progressive, chroma formats, frame rate, data rates, etc.), as well as, your transcoding goal priorities, it would be difficult to recommend a specific workflow and optimum encoding settings. The only thing I could do at this point is to make some general suggestions.

The first suggestion would be to transcode your older content to an open "standards-based" format like MPEG-4 AVC which is currently being used for everything form cellphone conference calls to internet streaming to Blu-ray videos. That is., to maximize playback across multiple platforms and devices, avoid the use of any proprietary or third-party codecs which might employ hybridization of profile features and target level settings or require use of a specific player or file container.

Another suggestion would be to limit the MPEG-4 AVC encode settings to maximize compatibility for targeted viewers. For instance, limiting use to Main Profile @L3.1 target encode features/settings should provide compatibility with JVT standards in use over the last decade but still easily handle content up to and including high quality 720p30 files requiring video data rates up to 14 Mbps. (I am currently re-encoding my files to 720p24 and 720p30 High Profile @L4.0 but use settings targeted for Main Profile @L3.1 compatibility for older hardware devices running current QT7/QTX/IOS player software.)

The next suggestion would be to use a file container that is compatible with your needs. I normally create 720p24/720p30 H.264/AAC/AC3/Chapter M4V files that are universally compatible will all of my devices (Mac OS X, iPad, iPhone, TV, etc. players), is managed by iTunes, and can be streamed within my home, as well as, over the Internet. The same content could just as easily be handle in an MOV file container but if limited to simple H.264/AAC files, might be more universally playable in MP4 file containers. Therefore, once again, your specific needs and requirements would likely dictate which container is best for you.

The last major consideration would be the transcoding app. If your MOV files contain "legacy" encoded data, I would normally recommend any FFmpeg-based converter software. I normally use the free HandBrake app because it includes both targeted presets for the novice user, as well as, a manual settings GUI for custom encodings by advanced users. In addition, it can be programmed to batch process files—i.e., I typically transcode 12 to 40 TV episodes every night while I am sleeping and currently (as of this writing) have 4,334 episodes that still need to be proofed. If the files are encoded with Apple "Pro" codecs not supported by the QT X player or HandBrake, then I would recommend using MPEG Streamclip or QT 7 Pro for the conversion.

I did see someone say that when you open an older file with new quicktime that it will create a new version of the MOV file that is compatible.

Once again, this depends on the codecs involved. The QT Player uses the AVFoundation structure for playback. If there is a playback problem (i.e., the codecs, file container, or combination of the two is not supported), then the data is analyzed by the Modernizer structure to determine if it can be converted to compression formats natively supported by QT X. (I.e., the Modernizer checks to see if the your system is indeed configured with the required codecs for QT 7 use). If it can be converted (the required codecs are available), then the Converter structure is called to perform the actual conversion. Unfortunately, this doesn't always work correctly. For instance, under Mavericks, QT X with not attempt to convert a file containing DTS audio if Perian is not installed but will attempt the conversion if it is installed. Unhappily, following the conversion, the DTS sourced audio is still not playable. (Have yet to see if this has been corrected under El Capitan.) In most cases, the conversion is successful. However, in some cases the resulting quality may be much lower than expected due to the absence of user control and the quality of the source file.

Here is what I just tried that strikes me as strange. I was able to open and play a MOV file with quicktime. I saved a new version of this, put it up on the website and it still does not play. Then it occurred to me - quicktime played the MOV file from my computer but cannot do so on the website. What is up with that?

Like the evolving QT playback structures now embedded the latest Mac operating systems, the media structures now supporting playback of web content is also evolving. Most browsers are moving away from the use of plug-ins and instead, using the more modern and simpler HTML5 <Video> Element to control browser playback of web content. (See http://www.w3schools.com/html/html5_video.asp) As previously mentioned above, you may need to recode your web pages for better compatibility across the various browsers currently in use. Unfortunately, as you have not provided any URLs for checking, I can only guess that this may be the source of the current problem cited above and may be yet another reason to switch to H.264/AAC content in an MP4 file container as supported by the latest versions of I.E., Chrome, Firefox, Safari, and Opera browsers.

Dear Jon (and community),

From reading your response to Michael Peterson1 I think you may hold the answer(s) to my problem. I think I am having a similar problem to Michael Peterson1, and am curious if you can help me. I am willing to pay you for your time if you can. I really appreciate any help you can offer because I'm very worried I might lose a lot of extremely sentimental videos I shot during a 2013 trip to Italy with my then fiance now wife.

I shot about 190 videos on my iPhone 4 during this trip and when I got home I exported them to my external hard drive. Then when I went to try to edit them in September 2015, I was getting errors that they would not play. At that time I was running OS X Yosemite. I contacted Apple Support and they were able to give me instructions to use 2 different versions of QuickTime (one old and one new) to basically change the codecs of the file and resave it as a new .MOV file that works. The person I spoke to noticed that when we looked at the file info for each video, the file sizes were way too small for the length of the videos...  I only made it through about 40 of the files and then got sidetracked with life.

For example, here are 2 screenshots: One is the File info for one of the .MOV files that didn't work, and then the other is the File Info after fixing it.

The reason for my post is fast forward to today and I am trying to do the same thing, but I am getting the following errors:

-When I try to open in QuickTime Player 7 (Pro) Version 7.6.6 (1709) I get this error:

-When I try to open in QuickTime 10.4 (855) it says:

Since I was able to fix all the files I did in September of 2015, but cannot now, I believe this is because of the OS upgrades (I am now on OS X El Capitan Version 10.11.5), and I do not know if the QuickTime versions have also changed. When I go into QuickTime 7, it does not even give me the option to 'Export.'

Do you have any ideas on how I can save my videos?

Thank you very much for your time.

Best,

Mike Kinsella

mkinsella7@gmail.com

For example, here are 2 screenshots: One is the File info for one of the .MOV files that didn't work, and then the other is the File Info after fixing it.

As previously stated, the first file is too small. The file size would tend to indicate it is a "reference" file while the playable file is what is called a "standalone" file. Basically, a "reference" file is a file that "points" to a "standalone" file that contains the actual audio and video data needed for playback. QT 7 Pro can save files as either reference or standalone files but reference files can only be played if the original standalone resource file is still available AND its path unorphaned. For example:

At this point it is difficult to tell if you have two separate issues or just one. If all of the non-playing files are small (measured in KBs instead of MBs or GBs), then they are all probably "Reference" files. If the original "Standalone" files are still available, then the videos can probably be "recovered" for use either directly or indirectly as long as they are not corrupted. Depending on the compression formats and/or settings used in the original files, you may or may not have to recompress the data as you did in your example to ensure the data is playable directly in the QT X player. Basically, you need to check the data resource to be sure the standalone data files are still available. You can do this using QT 7 Pro if still available to you. For example:

As you can see above, the "Reference" MOV file points to an MP4 resource file that contains the actual video data to be played back. If this resource file is missing or has been moved to a different location other than the path indicated, then the reference video cannot be played or recovered. On the other hand, the original MP4 "Standalone" file contains a resource reference that points to itself as seen below:

Based on the information provided in your post, I suspect you may have accidentally created "Reference" files during your external storage copy workflow. The main question is whether or not you still have copies of the original  standalone files containing data.

Jon, thank you for your response.

Unfortunately, your thoughts do not account for why I was able to open the small "Reference" files in QT 7 Pro in September of 2015, and now it no longer allows me to do so. Nothing else has changed since that time. The point that, "you need to check the data resource to be sure the standalone data files are still available." is not applicable, because I did not change anything Re: the standalone data files from September 2015. To recap, in September 2015:

1. I was able to open any of the small "Reference" files in QT 7 Pro.

2. Then I was able to export each of those files as what you are calling "Standalone" files (MBs or GBs).

The only reason I did not finish this process then was because it was time-consuming. 

This is what leads me to believe the reason QT 7 Pro will no longer let me open the "Reference" files is because Apple changed what Codecs it supports since then and now QT 7 Pro will not even allow me to open these "Reference" files, whereas before it did.  Does that make sense?

Unfortunately, your thoughts do not account for why I was able to open the small "Reference" files in QT 7 Pro in September of 2015, and now it no longer allows me to do so.

As previously pointed out, a "Reference" file will continue to play normally as long as the QT 7 player can continue to locate the source data contained in the original 190 iPhone 4 video files. (I.e., I am referring to your very small videos such as your 8 KB (12 KB) example above.) Obviously if this file played when you created the "Reference" file back in September of 2015, the video data was both available AND accessible at that time. This may or may not be the case now and is why you need to actually look at the file internals to determine where the original files are supposed to be located and then check to see if they are still actually there. On the other hand, if the 8 KB (12 KB) file was the original iPhone 4 source file and you created a playable 18.1 MB file from it, then the original file problem was likely a "security" issue that came up due to a software update between the time you originally recoded the videos and the time you decided to edit them. In this case my guess would be that QT 7 could not read the video's eof (End of File) marker and considered the file to be corrupted. (I.e. QT 7 is a "Program Stream" player and will only play files if it knows where the file ends while third-party "Transport Stream" players might ignore the original problem and allow you to read and save or read and convert the supposedly "corrupt" no eof file to a new MOV file container which QT 7 no longer considered to be corrupt. (I.e., the description of your actual workflow and the relationship between the two "1654.MOV" examples listed above was not overly specific.)

Nothing else has changed since that time. The point that, "you need to check the data resource to be sure the standalone data files are still available." is not applicable, because I did not change anything Re: the standalone data files from September 2015. To recap, in September 2015:

 

 

1. I was able to open any of the small "Reference" files in QT 7 Pro.

2. Then I was able to export each of those files as what you are calling "Standalone" files (MBs or GBs).

 

 

The only reason I did not finish this process then was because it was time-consuming.

Until you can confirm that the "reference" files still point to resource files containing "standalone" data and that the target files are accessible, then there is always the possibility that the "resource" file has been deleted, moved, or located on a drive that is unavailable/not connected to your system when needed. (I.e., this is not a question of whether or not the small reference file has been changed but whether or not the path in the reference file is still valid when it comes to reading and playing data stored elsewhere on your system.

1) A user decides to use the QT 7 Pro "Save As..." option and must choose to save the file as a "Reference" or "Standalone" file.

Since "Reference" files are much smaller than "Standalone" files, many users opt for the smaller file without considering the consequences of their choice—namely that they must keep both copies of the file for the smaller file to continue to play correctly.

2) Unfortunately, once the user sees that the smaller file plays exactly the same as the larger file, he or she may decide to move/keep the small file on the startup hard drive and delete or move the large file on an external drive which may or may not be permanently connected to the system. Under older operating systems, the small reference file becomes unplayable if the larger file is deleted or if the files are separated/moved to a new location. Luckily, the latter no longer seems to be a problem on a Mac under the latest operating system. (I.e., older systems would ask the user to locate the orphaned data file and manually re-establish a valid path between the two while El Capitan now performs an extensive but automatic search of all connected drives to re-link the data.) Since you previously indicated you moved/exported files to an external drive, it is unclear if they are still available/connected to the startup system for "Reference" file playback. Unfortunately, the 8 KB file size example implies your "Reference" file was created under an older operating system and does not contain the ancillary data needed for a system-wide, automatic search. (E.g., compare my 63 KB "Reference" file example with its 15 MB "Standalone" resource file example above.)

3) Using the QT 7 Pro "Properties" window (if files will open) or a utility like MediaInfo (if files won't open in the QT 7 Player) allows users to determine the resource file path embedded in "Reference" file. If the target resource file is not located at that location, then you know why your "Reference" file no longer play and how to fix the problem if you still have a copy of the "missing" file.

4) Most experienced users employ "Reference" files for non-destructive editing or telling the QT 7 Player how to play media. For instance, you can use a "Reference" file trim the playback of video contained in the "Standalone" file without physically alternating it. In a similar manner, a "Reference" file could be used to sequentially play several "Standalone" files (or segments thereof) without physically merging the data together into a single, huge file. Reference files are also frequently used to move "edited" data between applications such as a video editor and a DVD authoring app without having to create a "Standalone" intermediate file.

This is what leads me to believe the reason QT 7 Pro will no longer let me open the "Reference" files is because Apple changed what Codecs it supports since then and now QT 7 Pro will not even allow me to open these "Reference" files, whereas before it did.  Does that make sense?

Unless you used some third-party recording application, all iPhone 4 "native" recordings should have used the H.264 video codec with AAC encoded audio. These files (H.264/AAC MOV files) are natively compatible with all QT 7 and QT X based apps. If such files don't open then they are corrupted recordings, have a "security" update issue, or were incorrectly transferred between Apple devices. If you had a security update issue, then converting the original H.262/AAC MOV data to an H.264/LPCM MOV file only served to create a new MOV container which did not have this issue and thus, fixed the problem in the same manner as you might have done by simply saving the original data to a new file container. (Do you still have all, some, or any of the original iPhone 4 recordings that can be uploaded for analysis?)

You sound like Sheldon. English, please.

How do I transfer an old Quicktime which plays in an old operating system so that I don't lose it and can play it in a new operating system and share it. I'm not going for another degree.

Thank you

Beth M.

You sound like Sheldon. English, please.

How do I transfer an old Quicktime which plays in an old operating system so that I don't lose it and can play it in a new operating system and share it. I'm not going for another degree.

There could be many reasons why an old file may not play on a "new" system. You basically have three options:

1. Provide sufficient information about the non-playing file so that someone here can respond with a specific solution. (E.g., open the file on an older operating system and capture an image of the "Inspector" window for posting here.)
2. If you cannot provide the required information, provide a sample file or file segment that can be examined by someone here in order to provide a specific solution. (E.g., upload a copy of the file to an online server for download and analysis.)
3. Use a third-party player and/or sharing app that is compatible with your files as they are if such is available. (E.g., try using a third-party player like VLC. If the file is not corrupted, not protected, and/or not encoded with unsupported proprietary codecs, most files will play.)

Without sufficient information, it is impossible to say if it is best for you to covert the file, modify the file container and/or data, copy the data to a new file container, use a third-party player, add codec support so that a Mac can "modernize" (natively convert) the file, etc.

Saying that a file won't play is like saying that your car won't start. It provides little or no specific information regarding what may or may not be wrong with either. Is the car out of gas? Is the fuel line or filter clogged? Is the battery dead? Has the ignition fuse blown? Is a cable loose or corroded? Or any of dozens of other problems. In a similar manner, video files can have dozens of issues which, in turn, may have multiple solutions depending on your specific needs or workflow requirements.