Quicktime player just won't play .mov files after Mavericks update....WHY?????

Just plugged my dji MavicPro drone into my iMac to watch my flight video recordings. The files are .MOV files which are supposed to be QuickTime files but . . . no joy. The files won't play and I get a message telling me to look on the web for a solution.

As previously explained, the ".MOV" file extension refers to the file (i.e., container) format and not to the specific data compression formats actually stored within the file. Since any form of compressed data can theoretically be stored in the file container it's most likely that your drone files are recorded using a legacy, proprietary, or third-party compression format and file container combination that is not supported by the QuickTime player you are trying to use for playback. Basically, there are 2 separate QuickTime structures embedded in recent Mac operating systems. One supports the classic QT 7 Player and the other supports the newer QT X Player being developed to replace the QT 7 Player. Some files will play in either media player while other files may only play in one player but not the other.

The are two ways to "fix" your problem—depending on what you want to do. The first, as you've already learned, is to use a player that natively plays the files as they are. For instance, if the files are encoded by a "legacy" codec already supported by the "classic" QT 7 Player, then you could simply install the QT 7 Player and play the files as they are. If the files are encoded by a third-party or proprietary codec which can be installed on the Mac, then you have the option of installing the currently unsupported codec and again use the QT 7 Player to play the files just as they are. This solution normally requires a bit of work on the part of the user to identify the specific codec(s) causing the problem. On the other hand, since many users don't feel comfortably analyzing a particular playback issue and then configuring a solution, they often prefer to simply install a third-party player which contains its own "built-in" codec support. VLC is probably the most common player used in this instance.

The second solution is to convert your unsupported MOV files to file/compression format combinations that are natively supported by your current media player. I normally recommend an app like HandBrake for this purpose since it is supported by the same codec package that supports VLC. Since this workflow may require additional effort on the part of the user and has the potential for reducing visual quality of the material, many prefer the first option above.

So I plugged my MavicPro into my Windows based laptop and was able to double-click the files and watch them, no problem.

If you were using the QT Player on the Windows based laptop, it implies that the MOV files are encoded using "legacy" compression format(s) that is/are already supported by the QT 7 structure embedded in most current Mac operating systems. If you are using a different media player on your Windows platform, it is likely that you can either configure your mac to play your MOV files natively using the QT 7 Player app or have the QT X Player automatically (with a few exceptions) convert the content to play natively in the QT X Player. Again, the choice is up to you here.

Shame on you Apple, your biggest OS competitor can play your files but your QuickTime can't. How embarrassing... And Apple doesn't even seem to care.

This is a user-to-user forum. If you wish to make comments to Apple, you should file User Feedback or Developer "Bug" Reports using the appropriate form.

Just plugged my dji MavicPro drone into my iMac to watch my flight video recordings. The files are .MOV files which are supposed to be QuickTime files but . . . no joy. The files won't play and I get a message telling me to look on the web for a solution.

I did, and found this forum, which from the few pages I browsed didn't provide a solution.

So I plugged my MavicPro into my Windows based laptop and was able to double-click the files and watch them, no problem.

Shame on you Apple, your biggest OS competitor can play your files but your QuickTime can't. How embarrassing.

And Apple doesn't even seem to care.

Quicktime player just won't play .mov files after Mavericks update....WHY??????😠

So disappointed with Apple....

What compression formats? Which QuickTime player? Basically, the compressed data must be compatible with the AVFoundation structure (for the QT X player v10.3) or the 32-bit QuickTime structure (for the QuickTime 7 player). Putting data in an MOV file container only means that the file container issupported by the various QT players but does not mean that the data in the container is supported by either the associated structure embedded in the OS or the systems codec component configuration. For instance, AIC, motion PNG, DV stream, etc. files are no longer playback supported by the QT X v10.3 player but remain compatible with the QT 7 player v7.6.6 under Mavericks. Further, just because you can put WMV data or DivX/MP3 AVI data or FLV data in an MOV file container, it does not mean the file will play in a QT player without third-party codec support. In short, it is impossible to answer your question completely without more information about the file, player, and codec support in use on your system.

I am having the same issue and I think that a critical tone is fair. I have multiple important media files that I cannot access now because I upgraded to Mavericks. They played fine before and I was not warned of this issue and I had no prior experience or need to analyze codecs etc.. I upgraded to Quicktime 7.6.6 and the files still do not play. A step by step instruction for what to do would be most helpful, it is not productive to ask us non techies for general "more information about file, player, and codec support.." If you are unable to tell us what to do precisely perhaps you could refer us to a place that can.

If the file opens in QuickTime Player 7 but shows a "black" window open the Movie Inspector window to learn what codecs it uses.

A step by step instruction for what to do would be most helpful, it is not productive to ask us non techies for general "more information about file, player, and codec support.." If you are unable to tell us what to do precisely perhaps you could refer us to a place that can.

A) Download a media information utility (like MediaInfo available free online or for $0.99 at the App Store) so you can analyze your files whether or not they open in a media player.

B) Determine what kind of files will not play.

1. Open the non-opening/non-playing file in the media information utility:
2. Determine which codecs were used to create the file.
3. Post a description of your problem along with either the information learned or a screen capture of the "Information Window" image to the forum. E.g.,

etc., or search the internet yourself for the unsupported codec(s) you are missing. In most cases, posting the "simple" window's information/image to the forum is sufficient for someone here to recommend a codec package to be downloaded and installed for QT 7 v7.6.6 to play the files or, in some cases, to add support so that QT X v10.3 (or the Finder conversion service) can convert the file(s) to a QT 7/X "native" compression format/file type video. Or, if you prefer, allow someone here to recommend a free conversion application if you prefer to convert your files manually or using customized settings.

C) Download, install, and use the recommended codec(s) and/or conversion application(s) that best suit your particular needs and workflow.

Hi Jon,

I had a MOV file with details given below.

Video

ID : 2

Format : MPEG-4 Visual

Format_Settings_Wrapping : Frame

Codec ID : 0D01030102046001-0401020201201002

Duration : 2mn 28s

Bit rate : 228 Mbps

Width : 1 920 pixels

Height : 1 080 pixels

Display aspect ratio : 16:9

Frame rate : 29.970 fps

Color space : YUV

Chroma subsampling : 4:2:2

Bit depth : 10 bits

Scan type : Progressive

Compression mode : Lossy

Bits/(Pixel*Frame) : 3.671

Stream size : 3.95 GiB (98%)

QT Player version 7.7.4 (OS:: Windows 7)is not able to play.

It is showing a message box directing me to 3rd party software.

Here i choose Xvid codec package for windows to Support MPEG-4.

After install i restart my PC but QT Player show the same error message

Will i do anything special to add the 3rd party codec support to QT Player.?

or I am not correct in the 3rd Party choice.

-Thanks

I had a MOV file with details given below.

Video

ID : 2

Format : MPEG-4 Visual

Format_Settings_Wrapping : Frame

Codec ID : 0D01030102046001-0401020201201002

Duration : 2mn 28s

Bit rate : 228 Mbps

Width : 1 920 pixels

Height : 1 080 pixels

Display aspect ratio : 16:9

Frame rate : 29.970 fps

Color space : YUV

Chroma subsampling : 4:2:2

Bit depth : 10 bits

Scan type : Progressive

Compression mode : Lossy

Bits/(Pixel*Frame) : 3.671

Stream size : 3.95 GiB (98%)

QT Player version 7.7.4 (OS:: Windows 7)is not able to play.

It is showing a message box directing me to 3rd party software.

Here i choose Xvid codec package for windows to Support MPEG-4.

After install i restart my PC but QT Player show the same error message

Will i do anything special to add the 3rd party codec support to QT Player.?

or I am not correct in the 3rd Party choice.

Information is incomplete. However, reading between the lines, this file appears to have been encoded as a Level 5 (or greater) HI10P, HI422P, or HI444PP file based on the Data Rate and Bit Depth settings and was probably overdriven for the frame rate. Franky, I'm not even sure QT 7 is playback compatible with these settings and, even it it is, am not sure it could keep up with the data throughput. I.e., since this file was encoded, more or less, as a BD file on steroids (10 times the data rate of a normal MPEG-4 AVC BD file), I would normally expect the file to freeze up and not play assuming you can get it to even open in the QT 7 media player. As to a third-party add-on codec, not sure there is one as I would normally expect an MPEG-4 AVC compatible player to suppeort all standard Profile/Level combinations on its own where caveats have not been stated. On the other hand, if this is a proprietary encode supporting such data rates/bit depths with a profile/level combination less than predicted above, you would definitely require the same or similar add-on codec if available. However, once again, I know of no such animal based on my limited "prosumer" experience.

hi,

sorry, but this is ********!!

what 'layperson' really has the time to go through all this material to learn about what to do? the developeers of all this stuff really need to start thinking like average human beings (consumer), when working with these products created for the 'public'.

why is the tail wagging the dog here? is quicktime a part of the apple company? if so, why are they controlling things in such a way that makes other software apps incompatible or inaccessable? if not, why are they forcing apple users to jump through all these unessary hoops just to use a product?

~ tj

what 'layperson' really has the time to go through all this material to learn about what to do?

A "layperson" who wants to know why his or her file does not play and who has 10 seconds of spare time on their hands to examine the non-playing file.

the developeers of all this stuff really need to start thinking like average human beings (consumer), when working with these products created for the 'public'.

why is the tail wagging the dog here? is quicktime a part of the apple company? if so, why are they controlling things in such a way that makes other software apps incompatible or inaccessable? if not, why are they forcing apple users to jump through all these unessary hoops just to use a product?

A better question might be "Why would anyone use third-party software to create a file having such unreasonable settings and then expect QT to play it?" (I.e., Apple's versions of QT 7 and QT X are both context adaptive and could not even create such a file.) Basically, a user would have to go out of their way to create a file with these settings and I would normally only expect an expert user with professional software to be capable of achieving these results. In short, most of the problems to which you refer are self inflicted and the result of a user's inability or unwillingness to avoid such problems in the first place. If you want to create files that are QT X, QL, and mobile device compatible, then use software and settings that create AVFoundation compatible files. If you are creating QT 7 compatible files, then use the QT 7 player along with any required third-party codec components as needed. If you are using proprietary or hybrid third-party apps to create non-standard files that cannot be supported by either QT X or QT 7 embedded structures, then use compatible media players for playback but don't expect Apple to "jump through hoops" to support competitor file/compression formats.

hi,

at the risk of being rude... 10 seconds??? DUDE!!! what are you smoking??

Jon, I appreciate you answering my original query. For the record, QT in my last Apple ios verion prior to the upgrade to Mavericks played all of these files without difficulty, the decrease in functionality is aggravating.

Hi guys

I got a similar issue

My ProRes files won't play smoothly in QT player (10.3) anymore

I run the latest version of Mavericks on my iMac. All softwares are updated

We got another i Mac here, exactly the same, same apps except FCPX and adobe Premiere. The ProRes movies work fine with QT 10

I did unistall Adobe Premiere today but I got Same Problem

HELP please!

thanks

at the risk of being rude... 10 seconds??? DUDE!!! what are you smoking??

It only takes me about 2 seconds to double-click open a media information utility like MediaInfo, drag 'n drop a problem file to the app window, and then open the details screen allowing an additional 8 seconds to glance over the video codec/settings information to determine if there are any obvious playback problems with the target media player I intend to use with the files. The fact that it takes you longer to open a file and interpret/use the information is not my responsibility. Most QT users who do not wish to learn how to interpret or personally use the information gained from such a utility would then simply report the data in this forum and ask for further assistance from others or post a sample problem file for someone else to examine/determine if the problem is in the file itself or is a problem that is associated with the user's system or workflow.

So what are you smoking that makes such a simplistic approach so difficult, DUDE?

Jon, I appreciate you answering my original query. For the record, QT in my last Apple ios verion prior to the upgrade to Mavericks played all of these files without difficulty, the decrease in functionality is aggravating.

First of all, you comment here is a bit confusing. IOS refers to the operating systems used by Apple mobile devices like the iPod Touch, iPhone, iPad, and TV. For the most part, any file previously playback compatible with such a device should not be affected by a Mac OS upgrade to Mavericks. On the other hand, an upgrade to Mavericks could affect the playback of non-IOS compatible files played by by one of the QT player apps.

1) Under Mavericks, the QT X v10.3 and QL players are now supported by a new structure embedded in the Mavericks OS. This structure is even more limited than previous embedded structures in that it does not even support ome of Apple's own proprietary codec components (e.g., AIC, PNG, Apple Animation, DV, etc.). In addition, if supported QT X v10.3 codecs are used in file containers for which the the AVFoundation is not programmed, then even supported codec files may become non-playable. This is why it is essential to have some idea (additional information) regarding the file and compression types you are trying to play on your system and which player you are trying to use.

2) Under Mavericks, the QT 7 player is supported by 32-bit, open archetecture "classic" QT structure embedded in the Mavericks OS. This structure actively and passively still supports all Apple proprietary "Pro" codecs you may have installed on your system. Further, it passively supports all "legacy" codecs and actively supports any you wish to turn back on yourself for use. Lastly, the open nature of the the "classis" QT embedded structure means that third-party codec components can still be installed/used by the QT 7 v7.6.6 player/"Pro" player app once the required assests are installed on your system. So, once again, it is necessary to know what kind of files you are trying to play on your system.

3) Under Mavericks, The QT X v10.3 player employs increased security checks. Files that previously played under older Mac OS X operating systems may now be trapped by the player and either will not load or may become non-playable. For example, in the last few days a user complained that web site files would not play. And, while the main problem was caused by the user's browser plug-in, I, quite by accidebt, discovered that the files could not be played in the QT X v10.3 player because the software used to create the files (an older version of VLC) failed to properly identify the MPEG-4 AVC profile in the file container even though the profile and level were properly identified within the video atom. Thus, the QT X v10.3 refused to load the file even though the QT 7 v 7.6.6 Player and the QT plug-in totally ignored this file container discrepancy and readily played the content. (I.e., the file became both QT X v10.3 and QL compatible as soon as I re-muxed the data to a new, properly identified file container.) Therefore, once again it is necessary to know all you can about a non-playing file to determine why it does not work in order to find one or more solutions for "fixing" the problem.

So, yes, while the reduced functionality of QT X v10.3 can be a problem for some users (especially "pro" codec users who rely on Apple's own proprietary codec components for editing purposes), it does not mean that other playback solutions are not still available. Had you indicated what types of previously playing files no longer work "natively" under Mavericks using either QT player, we might have been able to provide more guidance at this time.

As to "not being warned" about the possible pitfalls of software upgrades, any experienced computer user can probably relate any number of "horror stories" from their own personal experience. My advice would be to pick up a reasonably good external drive and use it to create a boot system drive for the pre-testing of any major revision of OS. You can then boot such a system and test the software before making any major commitments on your main system drive. (I use a Sans Digital MobileSTOR encosure which allows me to "pop in and initialize" 1-4 TB internal enterprise drives for testing purposes, as well as, quickly and easily switch between various Mac OS X versions to run compatibility tests as needed.)