Ver Videos Avi En Quicktime Mac
Tommye Hope
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? Can't believe they would make it where previous files will not play.
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.
Thanks John for your response. I agree with you that it's good that apple is making more functional and capable software. That doesn't help me with my issue however. And no I don't think it's reasonable to expect people who go to our website to access some older software.
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. 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.
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?
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.
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.
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 Element to control browser playback of web content. (See _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.
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.
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.'
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:
d3342ee215