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

Quick Look doesn't work for .mov files in 10.9

I can no longer view .mov files in Quick Look mode after installing 10.9. Can anyone verify this?

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 24, 2013 3:17 PM

Reply
57 replies

Oct 24, 2013 5:29 PM in response to JimInAnnArbor

I can no longer view .mov files in Quick Look mode after installing 10.9. Can anyone verify this?

I can't. My files continue to play fine in preview. However, that is likely because nearly all of my files were made using compression formats which are natively edit-compatible with QT-based apps and Apple IOS devices. Since you did not indicate what compression formats are contained in your MOV files, it is impossible to tell if this is your issue here.


User uploaded file

Oct 25, 2013 7:35 AM in response to JimInAnnArbor

I can no longer view .mov files in Quick Look mode after installing 10.9. Can anyone verify this?

Based on you initial comments and my inability to duplicate the problem with my iTunes/Mobile device files, I spent much of the evening running a series of tests on other file/compression types. It does appear that the QL has been modified to more closely mimic media app playback—i.e., the system routine now appears to look at both the file extension and compression formats in deciding how to handle QL. While I have mapped out a number of QL workflows (primarily for Apple supplied codec components), I do not have the time to dedicate days (or even weeks) for the examination of all possible permutations, let alone third-party possibilies. However, is a quick summery of some of the "generalizations" observed:


1) QL playback/lack of playback is not limited to just MOV file types/file extensions.


2) If QL/Maverics does not recognize the file extension/file type, the system Finder icon will display as a generic document icon and not allow QL playback.

e.g., User uploaded file


3) If QL/Maverics recognizes the file extension/file type but does not support QT for the specific compression format(s) contained within the file, then the system Finder icon will display as a generic or content specific document icon and not support QL playback.


e.g., User uploaded file


4) If QL/Mavericks recognizes both the file type/extension type and the compression format(s), then the system Finder icon will display as a QL preview capable file icon but may or may not actually play the file. Unfortunately, this is an area where things can get really confusing. Here is just one example:


If I take an unencrypted muxed MPEG2/AC3 in a VOB file container, it's Finder icon displays as a genereric ducument file that cannot opened in QL or QT X v10.3 but will open and play without audio in the QT 7 player with the Apple QT MPEG-2 Playback component installed. If I take this file and change file extension to MPG, MPEG, or TS, then

a) QL will open the file but not play it,

b) QT X v10.3 will open and play the file but the video on my system is not smooth, and

c) QT 7 with MPEG-2 component will play the MPG and MPG file video smoothly but not the audio and the TS file will not load because QT 7 will only open/play program stream content.


If I take the same VOB file and move the muxed MPEG2/AC3 data to a real TS file container, then the TS file will open in QL, plays the MPEG-2 video (again not smoothly), but won't play the AC3 audio at all.


If I take the same VOB file and remux the MPEG-2 video with MP2 audio to TS file, then QL opens and plays both the video (not smoothly) and the audio.


if I take the same VOB file and remux the MPEG-2 video with MP2 audio to an MPEG file container, then QL, QT X v10.3, and QT 7 with MPEG-2 component all play both audio and video but video playback reamians "unsmooth" in QL and QTX and smooth in QT 7 on my system.


If I take the same VOB file and remux the MPEG2/AC3 data to an MKV file container, then the MKV file is incompatible with QL, plays the video smoothly in QT 7 with Perian installed, and forces QT X v10.3 to convert the data to an H.264/AAC MOV file. Unfortunately, the resulting H.264 video contains incompatible AAC audio (insufficient bandwith of only about 1 Kbps per channel) but the video plays smoothly in QT, QT X v10.3, and QT 7.


In any case, it is this playback inconsistancy based on file type and compression format that is causing problems in mapping what has changed under Mavericks. At this point, it appears the QL may now be sharing some of the "playback" routines originally developed/programmed into QT X v10.1 and v10.2 and is now placing restrictions on how the QL feature functions. Recommend other interested parties make similar tests on their own systems and share what they learn. For instance, it appears that neither QT X v10.3 nor QT natively support legacy formats like AIC/PCM MOV, Animation/PCM MOV, or PNG/PCM nor DV/DV content in a DV file container but continue to support DV/PCM in MOV, H.264/AAC in MOV/MP4/M4V, MPEG4/AAC in MOV/MP4, HDV/PCM in MOV, ProRes422/PCM in MOV, etc. And, while my iTunes manged H.264/AAC/AC3/Chapter M4V file library remains compatible with QL, QT X v10.3, and QT 7 playback, I was disappointed to note the current QT embedded structure now reflects my inactive secondary AC3 sourroud sound audio tracks as having a zero data rate which I suspect may be the reason I've lost the ability to switch to AC3-optical decoder playback on my system. In short, it looks like it will take some time and a lot of man hours to properly figure out all of the changes made to Mavericks so I recommend QT users be sure to share any QT related information you may recover in the near future.


User uploaded file

Nov 20, 2013 6:35 PM in response to Phillip297

I am having the same problem after upgrading to 10.9, can't open .mov file sent to me from my son. i updated all my Aplpe devices, ipad, iphone. macbook, and imac..... no success. i don't have time to research this anymore.

If you post the specific codecs contained in the MOV, we may be able to tell you how to play the file in a different player. In most cases, if the codecs are QT native, an app like QT 7, MPEG Streamclip, VLC, MPlayerX, etc. will play the file. The problem is that any codecs compatible with your son's system can be placed in an MOV file container and, if they are codecs which are not also on your system, could present other playback issues.


User uploaded file

Feb 17, 2014 12:57 AM in response to JimInAnnArbor

To be short, MOV is a container format and the MOV video can be encoded with different codec, if one of the codec (video or audio) is not compatible with QuickTime, or both are not native to QuickTime, the playback may be not smooth. But this problem can be resolved if you can install some codec to your QuickTime. If you cannot find proper codec, you can simply convert videos to QuickTime MOV using this software:


https://itunes.apple.com/us/app/mov-converter/id688038462?mt=12


Good luck🙂

Feb 17, 2014 7:23 AM in response to sueanncoopel

I understand that there are different codecs, the question is why Apple included the codec previously and now has removed it from Quicktime. I shouldn't have to search out another codec for something that worked in the last release. At this point I can't see any reason to use the .mov format or use Quicktime tools for any video if I can't be guaranteed that it will play easily in the future. If VLC can play any video, why can't the company that created Quicktime provide the same set of codecs from one release to the next?

Feb 17, 2014 11:17 AM in response to zampino

I understand that there are different codecs, the question is why Apple included the codec previously and now has removed it from Quicktime. I shouldn't have to search out another codec for something that worked in the last release. At this point I can't see any reason to use the .mov format or use Quicktime tools for any video if I can't be guaranteed that it will play easily in the future. If VLC can play any video, why can't the company that created Quicktime provide the same set of codecs from one release to the next?

Your statements imply a somewhat flawed understanding of the situation.


1) VLC does not have the capability to play "any" video compression format. (E.g., try playing an MOV file with AIC encoded video.)


2) In April of 2005 Apple released QT 7 which had been delayed pending completion of negotiations for rights to the H.264 (MPEG-4 AVC) codec as Apple's choice for a "default" (general use) codec which opened the door to Apple's release of the 5th Generation iPod later that year, as well as, the basis for the current QT modernization program. (I.e., the H.264 codec is highly efficient and scaleable for everything from cellphone conferencing to 4K (2160p) and 8K (4320p) ultra high definition video use planned to evolve over a decade-long program of development.) Many consider this evolution of QT the equivalemt of Microsoft's multimedia modernization project begun 11 years ago which traded general codec use in the AVI container for proprietary, more modern home and commercial applications of Windows Media.


3) Nothing has yet been removed from the Mavericks OS and there isn't any real need to "search out another codec." While embedded support for the QT X player has switched to the new AVFoundation which does not support most legacy codecs, these legacy codecs are still supported by the QT 7 32-bit support structure which is still embedded in Mavericks. (I.e., if you wish to continue viewing legacy files, then download and use the QT 7 (v7.6.6) media player which is still available from Apple for use on QT X capable systems and which still works with both legacy and third-party codecs even under Mavericks.)


4) Whether or not you use the generic MOV file container is strictly up to you. You do, however, need to use codecs which are compatible with the support that is available for the particular media player you elect to use. For instance, as noted above, if you wish to play your "legacy" codec files in a QT player, then use the QT 7 player. On the other hand, had you read the "handwriting on the wall" 8 years ago and switched to Apple's default H.264 video codec, then you would not now have a problem with QT X, QL, and/or IOS player software but would likely be complaining about the requirement to continuously upgrade your video files to match the ever increasing higher definition capabilities of evolving QT software and IOS device hardware. (E.g., I still have some QVGA 5th Generation iPod files yet to be updated if/when content is re-released on higher definition/re-mastered optical media.)


It is virtually impossible to please everyong all of the time. In short, software and hardware is continuously being improved and someone will complain about the process of evolution which either limits the playback capabilities of older formats or fails to keep pace with new ones constantly being added. For most users it comes down to a matter of what is most important to them. For instance, would it be more important for you to be able to play AVI files or AVCHD files? The latest versions of QT X support AVCHD while QT 7 can support multiple AVI file formats but neither player supports both. Thus, having both players installed is a viable solution for many users—but will probably not satisfy everyone.


User uploaded file

Feb 17, 2014 12:36 PM in response to Jon Walker

Thanks for the detailed explanation, providing much more information than Apple has provided. While I respect the need to keep current, the Finder's Quick Look feature is hobbled and of little use to me under Mavericks, and nothing you wrote makes me believe that I will be able to use the feature for the large legacy of movies I have on my hard drive.


In particular, your statement "(I.e., if you wish to continue viewing legacy files, then download and use the QT 7 (v7.6.6) media player which is still available from Apple for use on QT X capable systems and which still works with both legacy and third-party codecs even under Mavericks.)" reminds me that Apple has indeed taken something away from me, and complicated my and other customer's lives because of the changes in Mavericks. Most of the videos I'm viewing are from a GE camera that generated Quicktime Movies, I had no choice in the codec they chose. Clearly I can still view my movies in different ways, but that doesn't quell my frustration after the Mavericks upgrade.

Feb 17, 2014 2:54 PM in response to zampino

Clearly I can still view my movies in different ways, but that doesn't quell my frustration after the Mavericks upgrade.

To each his (or her) own. As previously noted, no matter what Apple does, someone is going to compain. I personally have (as of this writing) 1358 movies and 124 TV shows containing from a minimum of 1 to a maximum of 26 seasons of from 3 to 39 individual season episodes stored on a single iTunes managed 12 TB RAID. Since these files (collected over the last eight years) are all compatible with QL, QT X, QT 7, iTunes, and 720p IOS mobile devices, I had virtually none of the Maverics associated problems of which you (and others) currently complain. Clearly, if Mavericks is so frustrating for you, then you should probably revert to an older operating system as many other users (including myself but for a system corruption reason) have done.



While I respect the need to keep current, the Finder's Quick Look feature is hobbled and of little use to me under Mavericks, and nothing you wrote makes me believe that I will be able to use the feature for the large legacy of movies I have on my hard drive.

Since QL is limited to the preview of single file at time and I am in the habit of previewing and/or comparing multiple files simultaneously, this feature is of little or no use to me whereas I can scan, preview and/or compare multiple files simultaneously using the mutithreaded capbilities of the QT 7 player.



In particular, your statement "(I.e., if you wish to continue viewing legacy files, then download and use the QT 7 (v7.6.6) media player which is still available from Apple for use on QT X capable systems and which still works with both legacy and third-party codecs even under Mavericks.)" reminds me that Apple has indeed taken something away from me, and complicated my and other customer's lives because of the changes in Mavericks.

I fail to understand your logic here. Mavericks employs a totally new (i.e., different) support structure for QT X. To me your logic is the equivalent of saying, "I bought a new car with a diesel engine in addition to my old gasoline powered car and now have lost the ability to run the new vehicle on gasoline." Which, in fact, is a capability the new vehicle never had and completely overlooks the fact that the older car still runs on gasoline.



Most of the videos I'm viewing are from a GE camera that generated Quicktime Movies, I had no choice in the codec they chose.

Unfortunately, as always, it is difficult to make any definitive comment here without actually knowing what specific codecs are involved. A quick look at a number of sample GE cameras seems to indicate that most current models employ either MPEG-4 AVC (H.264) or Motion JPEG video in the MOV file container—both of which should remain QT X and QT 7 compatible. However, under Mavericks, an unexpected audio compression format can trigger QT X v10.3 to convert the file whether the video track is converted or is simply "passed through" in its current compression format. (Strangely enough MJPEG video with Integer audio AVI files remain QT X v10.3 player and QL compatible under Mavericks.)



In any event, as previously stated, if QT X and QL compatibility is most important to your workflow, then your best option would be to revert to a previous OS like Mountain Lion. If you can live without QL and prefer the Mavericks OS for everything else, then use an alternative player for your GE camera videos and/or QT 7 for Apple proprietary (and/or "legacy") codecs no longer supported by the QT X v10.3 player.


User uploaded file

Quick Look doesn't work for .mov files in 10.9

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