Newsroom Update

New features come to Apple services this fall. Learn more >

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

QuickTime convert .avi to .mov with OS X Mavericks

Hello! I used QuickTime for watch any videos on OS X Mountain Lion, but now, I'm passed to OS X Mavericks and QuickTime, when I open an .avi file, convert this in a .mov file. I'm sorry for my English, I'm French and I don't know speak English very well, but what can I do for QuickTime opens on .avi and doesn't convert to .mov?

MacBook Pro (13-inch Early 2011), OS X Mavericks (10.9), QuickTime Player X

Posted on Oct 23, 2013 3:57 PM

Reply
167 replies

Oct 29, 2013 6:04 AM in response to Deborah Terreson

Hi. Can anyone confirm what Deborah wrote? Specifically, her experience in owning QT Pro allowing her to avoid this God-forsaken ridiculous waste of my time moving backwards? This is the first thread I came across in what has become the beginning of my "Crusade", so I haven't had a chance to see if any other similar threads have produced a quick and easy fix.


If someone could please confirm what Deborah wrote earlier, please tell! I have no problem scrounging up the pennies in my Rainy Day fund and tossing them at this rotten apple- money comes and goes, but my time is the one resource that no one can return back to me.


Thanks!

Oct 29, 2013 6:32 AM in response to michaelshim

Apparently if you use QuickTime Player 7.6.6 in Mavericks and have any required codecs installed and open the videos in QuickTime Player 7.6.6 then you can still play them as before without being nagged to convert them.


The issue only arises if you open them in QuickTime Player X.


Therefore for .avi, .wmv, .mkv, etc. i.e. non-Apple formats set them to always open in QuickTime Player 7.6.6


You can still use Perian with QuickTime Player 7.6.6 but not QuickTime Player X.

Oct 29, 2013 7:49 AM in response to michaelshim

Hi. Can anyone confirm what Deborah wrote? Specifically, her experience in owning QT Pro allowing her to avoid this God-forsaken ridiculous waste of my time moving backwards? This is the first thread I came across in what has become the beginning of my "Crusade", so I haven't had a chance to see if any other similar threads have produced a quick and easy fix.


If someone could please confirm what Deborah wrote earlier, please tell! I have no problem scrounging up the pennies in my Rainy Day fund and tossing them at this rotten apple- money comes and goes, but my time is the one resource that no one can return back to me.

Not exactly sure which aspect you and/or Deb are referring to. As John indicated, QT 7 Pro continues to work normally under Mavericks as far as AVI playback is concerned. That is AVI, FLV, MKV, DV stream, and MOV fils containing AIC, Animation, or PNG encoded video. However, since MPEG Streamclip also performs normally, my assumption is that this is due to the QT classic 32-bit structure still embedded in the Mavericks OS and not due to the presence of the "Pro" key. (Unfortunately, if I remove my purchased "Pro" key, then QT reverts to my FCP "Pro" key and I am unwilling to uninstall that key just to test one possible interpretation of Deb's comment.) In short, neither the QT 7 Pro player nor the MPEG Streamclip media apps seem to be plagued by the QT X player's attempt to convert or not convert a particular compression format or compression format/file format combination—including formats like AIC in MOV, DV in DV, PNG in MOV, etc,


On the other hand if you are interpreting the comment to mean that the presence of a QT 7 "Pro" key will prevent QT X v10.3 from attempting to perform a conversion, then I would tend to disagree with that generalization. The only AVI file QT X v10.3 has not tried to convert only my system is one containing Motion JPEG video with DVI ADPCM audio—i.e., an old digital camera file someone sent me for analysis years ago which is still on on system. In addition, the question as to whether or not QT X v10.3 will "passthrough" a particular compression format also seems to depend on the container involved. Based on these two observations, it appears that the AVI container, in and of itself, is not what is forcing QT X v10.3 to transcode files since the container itself still seems to "QT" compatible.


Therefore, as John stated, the decesion as to whether or not to invest in a QT 7 Pro key really depends on the work flow you wish to adopt here. If all you want is playback, then the QT 7 player with the appropriate QT codec component configuration can play your files. If you also want conversion and some limited editing features, then install the free MPEG Streamclip app along with the required codec components that work for the QT 7 app. But, if you require a more advanced conversion, compositing, and masking workflow along with access to built-in editing filters, then by all means go with a QT 7 "Pro" key here.


User uploaded file

Oct 29, 2013 9:05 AM in response to GalaxieMusique

Not sure if this has already been mentioned, but apparently due to issues with sandboxing (now required for apps offered in the App Store) MplayerX is discontinuing offing its latest versions through the App Store. I just tried using the version of MplayerX in the App Store and it crashes every time. I am about to test the latest MplayerX binary from the developer's website. You can read the developer's assessment here: http://mplayerx.org/leave-mas.html

I will chime in with previous comments in saying that it is unacceptable for Quicktime to force file format conversion. Also, I am finding that some mpeg4 files neither play or convert. They are treated as unreadable. Furthermore, an mpg video file plays the video portion, but I get no audio!


This is nuts!

Oct 29, 2013 12:58 PM in response to miles_lane

We did not even try to offer our applications (nessMediaCenter, nessViewer) in the App Store because of sandboxing. Both applications need free access to folders - for example the media server (which allows it to stream media to nessViewer for iOS) needs access to the folders the user adds and all of its subfolders. And this is impossible. Same for the media center, which needs access to the iPhoto & iTunes library and folders like the picture & movie folder (and all of its subfolders).


As already mentioned, it is not QuickTime which force file format conversion, but AV Foundation. AV Foundation comes from iOS and it can read and play only a few video formats.


But conversion is not the only problem. If you want to edit a movie (cut, copy, paste), it is much more complicated (or even impossible) with the new "QuickTime Player" (which is based on AV Foundation). We are working since Mac OS X 10.7 on 64 bit versions of our applications to bring back the simplicity of the old "QuickTime Player" and FrontRow. We still hope that Apple will extend AV Foundation and its supported movie formats, but guess that this will not happen.


One reason for AV Foundation on Mac to support only MPEG4 and H264 might be iCloud - it makes no sense to synchronize movies to iOS if iOS can not play these movies.

Oct 29, 2013 1:12 PM in response to nessviewer

One reason for AV Foundation on Mac to support only MPEG4 and H264 might be iCloud - it makes no sense to synchronize movies to iOS if iOS can not play these movies.

I think you might be right with that. Which leads me to the conclusion that Apple is forcing us to use iCloud, whether we like it or not (synching Calendars and Contacts from iPhone to your Mac is not possible anymore without iCloud – before Mavericks, you could do it by USB-cable).


What about those people who do not want to sychronize movies on all of their devices? Who want to keep part of their files (such as movies in older codecs) just on the mac and want to use them as before?? Why is Apple not giving us a choice?

Oct 29, 2013 4:45 PM in response to Jon Walker

Jon Walker,


I appreciate the effort you put in your post, which I found informative and helpful. Just to be clear, it was never my intention for anyone to put Deborah's experience to the test and delete any app or program, especially one that has been paid for!


Not to personalize this as every user's experience is unique, I believe I am one that others can relate to. Just to break it down:


Experienced Mac user for several years

Need-to-know basis for learning video formats and editing (learned just enough to make things play)

Pre-Mav:

Installed Perian, Flip4Mac, ffmpeg

Played most videos using QT X

Played the few that didn't with VLC

If the rare conversion was necessary, MPEG Streamclip


To be brutally honest, I care nothing for understanding the logic and reasonings of Apple's decisions (as of late, especially), and leave that discussion for the more intellectual of our community.


The search is for the easiest and quickest work around fix, allowing both:

1. QT to stop converting automatically nearly every video opened, and

2. Return previewing functionality via Quicklook (spacebar play), as well as playing the video in the preview pane of Finder windows

3. Very basic video editing functions, like those found in QT (clip, split, etc.) - but easily given up for the first two goals


From your post and related discussion, it appears the options thus far are:

1. Use the older QT 7 (32-bit) for playback, no need for installation of any additional apps/codecs than already was installed, understanding the possibility of some performance issues (slow, laggy, choppy playback, delay, unresponsive/crashing of app); no Quicklook functionality or Finder preview

2. Convert all videos, whether in batches prior to playback or as a single conversion on a needed basis, understanding the possibility for converted formats inflating to a minimal increase in size, to more than double the original size (depending on containers and such); Quicklook/Finder previewing functionality restored for converted videos; extremely time- and CPU-resource demanding

3. Reassign all video formats to be played strictly using VLC, MPEG Streamclip, and possibly other 3rd-party apps, or a combination thereof; no Finder/Quicklook functionality

4. Purchase a key for QT 7 Pro; practically no forced conversion and playback functionality restored with no real added performance issues, plus more video editing options; understanding monetary cost and possible discontinuing support, Finder/Preview functionality unknown?

5. Revert the OS to a state prior to updating to Maverick OS using a saved previous session backed-up via Time Machine, requiring backing-up of the system prior to the update


Are those the main options? Depending on whether or not I can restore Finder/Quicklook previewing functionality with a QT 7 Pro key, I have what I need to decide my next step.


I apologize for the long post... in my attempt to help others in a similar situation as myself, and trying to do so typing on an iPhone, I might have produced a hard read.


Thank you, Jon (and John), and anyone else for your time!


Michael

Oct 29, 2013 6:57 PM in response to michaelshim

Michael.. don't bother with a Pro key. I was throwing out ideas before I had sussed out that it was in point of fact QuickTime Player 7.6.6 that is the solution, and NOT the Pro key itself.


I've NEVER liked or used the QTX and from Day 1 just installed the QuickTime 7 and put in my Pro key.


To get around al the reconversion nonsense and have the widest support for all the old file formats you use, here is a cut-and-paste of the list I've compiled - with installation instructions - to get everything running.


The QuickTimePlayer X that comes with your system is trying to reformat - there is NO way to get around it as the instructions are nested down in the libraries for the application - in the QTKit.framework. It's an instruction-set that you can't get out unless you know how to program code. (I think it's in Objective C)


With that as a given, what is left to do is download and use the last available version of QuickTime Player 7 and get the codec packs you need - all of this is the 32-bit code and it's days ARE numbered so fair warning.


Here is the quick list I've built as a workaround to keep your files unsullied.



Start with QT 7.6.6. - http://support.apple.com/kb/DL923


Get Perian, and install it. - http://perian.org


then VLC, - http://videolan.org


DivX - http://divx.com - and the


Flip4Mac package from Telestream - http://www.telestream.net/flip4mac/


A52/AC3 downloader: https://www.macupdate.com/app/mac/21875/a52codec - In this installer package there is an audio A52Codec.component. DO NOT USE IT! Throw it out and use the one that is linked below.



This is what I've put into my system and so far I've gotten every file to run fine, even my oldest videos.


These are codecs you should see.


In System/Library/QuickTime

AppleIntermediateCodec.component

AppleMPEG2Codec.component* (*optional if you've bought it)

DivX Decoder.component

Flip4Mac WMV Advanced.component

Flip4Mac WMV Export.component

Flip4Mac WMV Import.component


In your Home/Library/QuickTime/

AC3MovieImport.component (you may or may not want this component, in some instances it causes conflicts. In my system, it doesn't. Who knows why? I don't.)

Perian.component


For AC3 sound that is in most .mkv files, you need the A52Codec.component, this is the one you want, here:https://dl.dropboxusercontent.com/u/34821905/A52Codec.component.zip - unzip the file and put the component into the System/Library/Audio/Plug-ins/Components


Go back to your Perian settings and in the Audio Output button, set it to 'Multi Channel Sound' - Ignore the message Perian puts up and select it.


By doing a 'Get Info' on your files and where it says 'Open With' - default them to the QuickTime 7 program. Perian no longer will work with QuickTime Player so you must have QT 7.6.6 and set it so it is the default for all the filetypes you use.


It works perfectly with QT7. So far I've gotten ALL my old videos to play.


.avi, .mov (with the AC3 sound), .wmv, .flv, .mp4 and .m4v. all run fine as do all the older formats.


Deb.

Oct 29, 2013 7:46 PM in response to michaelshim

Are those the main options? Depending on whether or not I can restore Finder/Quicklook previewing functionality with a QT 7 Pro key, I have what I need to decide my next step.

Not quite as stated.


1) Use of QT 7 (classic 32-bit QT structure embed) may require additional codecs or file support to handle file/compression types not supported but the basic host OS codec component configuration. To actively use (encode) legacy compression formats turned off by default under Mac OS X v10.7, v10.8, and/or v10.9 will require the user to manually re-activate the desired codecs. Performance issues normally depend on the harware capabilities, compression formats involved, and/or encode settings used to create the files. (E.g., it is hard to smoothly play a file having a data rate greater than the throughput of your hard drive or greater than your media player can render without droping frames.)


2) Agree.


3) Basically agree but stress that QL Finder/preview remains whatever the host OS supports—something that remains to be fully mapped under Mavericks. (E.g., I have a Motion JPEG/DVI ADPCM AVI file that is still compatible with QT X playback and QL Finder/Preview under Mavericks. However, this appears to be an exception to the general rule for file content support under this OS release.)


4) QT 7 Player and QT 7 Player Pro playback capabilities are the same—only dependent on the system's QT codec component configuration. Keying the app for "Pro" use has no effect on performance issues or QL Finder/Preview cabilities. It is however, the only standalone, non-professional video editing utility with track level compositing and masking capabilities built in so I consider it well worth the price until such time as support may be discontinued.


5) Would generally agree with your statement here but personally prefer creating pristine boot drives and either reinstalling or migrating apps as needed. (I.e. I normally keep at least two standalone external drives with basic OS software for current, as well as, previous major Mac OS in case of catastrophic main startup drive failure, and bare drives with older major Mac OS versions for use in a removable HD case for testing purposes, as well as, four RAID assemblies totalling 41 TBs for content/project storage which represents my personal home, non-business system. It may sound like overkill, but I have a basic philosophy that states that if anything bad can happen, it will, and usually at the worst possible time.)


User uploaded file

Oct 29, 2013 8:14 PM in response to Jon Walker

It may sound like overkill, but I have a basic philosophy that states that if anything bad can happen, it will, and usually at the worst possible time.


User uploaded file

LOL! Oh do we think on the same lines!


Though not as much data, I still have many, many escape options available. As it stands, this latest upgrade was put on my uber-partitioned MacBook Pro - and am not at all interested in "keeping up with the Jobses" to the point where certain wired functionality is lost to the 'cloud'.


Suffice it to say, the Mavericks upgrade was an interesting side diversion and yep, call me unimpressed as it's offering less and less that is relevant to my needs out of a computer.


(I am a digital artist and work with a photographer and a videographer)


I'll toss out what help I can, but I can see my days are numbered with Mac OS if it continues to expect or *insist* that users live on social networks or store their personal data on 'clouds' - which at a time in the not-too-distant future may very well present too much of a fat, juicy target for inspired hackers to resist.


Yeahhhh.. I don't think I'll be putting anything up there..


At the point where I still cannot outdraw a 7 year old MacPro with a Wacom attached to it, why jump through the hoops or dance to Apple's tune on this? We're at the cusp of what I see will be many profound structural changes to what computing is and how users interact with their devices and even whether they'll always have access to their data.


Everyone is going this way, not just Apple and as vjPulp asked, why they are pushing this on users.. simply it is because for many - those who HAVE to 'keep up' - well, they *can* push - and that is the majority of users that just want their shiny toys to bring them the stock reports or weather or their grandkids pictures.


The pro user/content creators aren't Apple's targets anymore - if they ever really were.


I'm quite content to work on my now 7 year old relic and stay with a fully functional Snow Leopard. (Heck, I even worked out with the xCode Tools how to install Sun Java..)


For now, Mavericks.. is well.. meh, with a boatload of issues for content production that doesn't bode well in the short term.


Regards,

Oct 30, 2013 8:31 AM in response to Deborah Terreson

(Chuckling with a smile to match...) We do think quite alike!

I'll toss out what help I can, but I can see my days are numbered with Mac OS if it continues to expect or *insist* that users live on social networks or store their personal data on 'clouds' - which at a time in the not-too-distant future may very well present too much of a fat, juicy target for inspired hackers to resist.

Totally agree. Decided to opt out on my own with the demise of MobileMe. Purchased a server configured MacMini and my own domain name for personal content I didn't mind exposing to the public via the internet and have been satisfied ever since. Am now testing a LaCie 3 TB CloudBox for password protected content area shared exclusivly between local user group members. (Not as happy with this as it is much slower but does provide dedicated plug-in and play, bi-directional browser access to non-DropBox user group members while remaining under my own physical control.) As to "fat, jucy targets," another philosophical "rule of thumb" is to never put anything on a computer or storage device that can't be disconnected from the internet, can't be replaced, or you can't afford to have compromised.


User uploaded file

Oct 30, 2013 9:18 PM in response to Jon Walker

For those complainers,


If you don't like what Apple has done/is doing/would like to do, quit complaining and move on to other platforms. And I wish you all the luck in the world.


There are too many who complain and holler that Apple is doing this or doing that. Remember, Apple is doing what it considers is good for the many. It couldn't care less about your piddling singular existence.


So for those who think that digging deeper into the nuances of a certain app, as many have shown in this particular app forum, just to sound off as very knowledgeable to others who have a desire to look for problem solutions, we don't need you in this forum. Get a life. You are just wasting good space. We need people who can provide solutions and work-arounds to specific problems.

Oct 31, 2013 1:23 PM in response to GalaxieMusique

This is truly disgraceful from Apple. I thought breaking Preview was one thing but now Apple are taking a leaf out of Win"those" book!

On Windows 8 X64 bit for example you cannot see thumbnail previews for any Adobe Products anymore unless you now BUY an app that was previously free in Windows 7 to render them - ie Mystic Thumbs! Pretty Bad......
On Mac however if you are into making movies, editing etc thumb views are invaluabe and a neccessity... Lack of them is like a blindfold to visual artists!
Not only have apple not built this ability into the operating system but now they have changed the architecture so we cannot now avail of the solution previously employed...(ie the now similarly defunct Perian... and flv.qlgenerator).

Please apple - rethink this... a huge part of your loyal customer fanbase are Visual Artists, designers and Movie makers.. You are now taking away our toys... soon there will be nobody interested in designing anymore... then...good luck to your iOS devices as they too will be too drab to entice buyers anymore!
I can live without Quick Look Previews perhaps,,, but thumbnail previews....most definitely not!

QuickTime convert .avi to .mov with OS X Mavericks

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