Couldn't care less about Wondershare. I brought that up so who ever read this would know that Wondershare has no problem and converts the file from mp4 to mov the problem was why Quicktime Pro which is supposed to do the same is not converting it.
Frankly, I am still trying to figure out what the things you've already said are supposed to mean.
When I try to convert an .mp4 to an .mov in QTPro the converted file only has the audio portion.
First off, MP4 and MOV are file containers--not compression formats. If the compressed data in the source file is already QT compatible, then there is no need to "convert" anything. If you want the data in an MOV file container, you simply use the "Save As..." option to copy it from the source file container to the MOV file container. If the compressed data is not, already compatible with QT, then you would need to ensure you system is configured with the proper component to allow you to "Export" (i.e., convert) the incompatible compression format to a QT "edit" compatible compression format for editing. Unfortunately, you never mentioned whether or not the files "play" in QT 7 Pro. Some compression formats are "playback" only compatible. Others may be "playback" and "conversion" compatible but not "edit" compatible while "fully" QT compatible files play, convert, and are editable natively.
Good question, I have a video project to do in Final Cut Pro. I was given various .mp4 videos and a .m4v intro. In FCP I was going to import all the files, edit the intro and the main video together and they want the final file as an .mp4 But FCP does not play .mp4 files so I have to convert to .mov.
Since you indicate the MP4 files will not "play" in FCP, the implication is that the video compressed data is not QT compatible. Unfortunately, QT and apps based on it are very "standards" conscious and may not be compatible with proprietary files or files encoded with hybrid profile/level standards which was why QTKirk asked about codec specifics and the source of your files. (The latter of which you failed to answer and which could be key to your problem.)
Isn't AVC the same as H264?
MPEG-4/AVC is the same as H.264 but AVC alone could simply refer to a proprietary or hybrid Advance Video Coding third-party codec.
Now for argument sake I took the original.mp4 file, opened and edited down in a trial of Wondershare Video Converter. It saved the file
Was this really a "Save" action or an Export/Conversion? If a simple save, then it implies the original data was QT compatible which may indicated it is the file container that is giving you problems and may either contain improper headers (which QT checks) or is not properly terminated. On the other hand, if the action was an export/conversion action, then that would imply the source data was not QT compatible. For instance, the Wondershare Video Converter appears to support XviD MP4 which would require a third-party component for use with QT apps.
I imported that file into FCP and it plays fine. But the file extension is still.mp4 so I changed the file extension to .mov, imported that into .fcp and That plays fine as well
Why would you think this would make a difference? QT looks at both the file internals, as well as, the extension. Any supported third-party compression format can be placed in a "real" MOV file container and will play just as well in either container. Changing the file extension normally has no effect on whether or not the file will play since the QT app will check the file "internals" whether or not there is an extension. However, changing the extensions can effect both the display of the finder icon and/or which application will try to open the file which, in turn, could determine whether or not the file will open in the called app. That is why QTKirk stated "We don't change a file extension just so it can 'work' with our apps."
Couldn't care less about Wondershare. I brought that up so who ever read this would know that Wondershare has no problem and converts the file from mp4 to mov the problem was why Quicktime Pro which is supposed to do the same is not converting it.
I doubt QTKirk cares about Wondershare either. What he would likely care about is actually seeing a sample snippet of your source file in order to run independent tests on the problem.
