Once again, you are providing little or no real information regarding what you are doing and how you are doing it.
If I take video from an iPhone, for instance, what possible issue could there be with a codec if I'm going to a Mac? Because I'm pretty sure sure I've seen this with iPhone video as well.
What model iPhone? DO you pre-process your iPhone clips in any apps before transferring to a computer. How are you transferring the content to your Mac? Does the same problem exist on all computers or devices—i.e., have you uploaded any of your files for issue comparison and/or analysis?
Some users have complained that files transferred from older iPhones stopped playing when Apple issued certain software security updates. In most of these cases, there was nothing really wrong with either data in the file or the file container but the security update did trigger trapping of the file during opening and a modal message indicating something was wrong with file even though it will still play normally on systems without the software security update. In many of these cases, a user could simply re-save the H.264/AAC data to a new MOV file container.
Another problem reported by some users is the failure of some files to open on a computer after they have been modified by certain third-party apps on the iPhone. So this brings up the question of any pre-processing of clips before transfer from the iPhone.
Some people use iCloud to transfer content or email videos to transfer them. Others use a digital camera app like iPhotos, Photos, Aperture, etc. or a video editing app like iMovie or FCP to import iPhone video content. Still others "Drop Box" their content as a form of shared-transfers. I sometimes use Image Capture or PhoneView to copy iPhone content to a dedicated target folder. Each method may have a potential for problems.
It is often a good idea to check your content on a different system and/or device to see if the issue is with the content or your system.
Granted, I could see that if going from the Sony but I get varied results from the Sony clips. Sometimes they're fine other times not. That said, both versions of QT will play the Sony files fine.
Your statement is somewhat confusing. What does "I get varied results from the Sony clips. Sometimes they're fine other times not. That said, both versions of QT will play the Sony files fine." mean? (I.e., how do varied results differ from playing fine?) Again, it would be nice to know encoded formats and file types we are talking about here—MPEG-1, MPEG-2, DV, HDV, H.264, AVCHD, etc? Are they anamorphic or not? (I.e., display aspects handled differently by QT X and 7.)
All I'm doing is clipping the file with QT-Pro. Nothing more. So it's the save out from QT-Pro that seems to jack it up. If it were a codec issue or format issue it would be consistent. Codec A is not compatible with version B so it won't play it. That's not what is happening. I'm seeing different results at times. Sometime it saves out and can be played back in QT-X and other times not. I'm not using any different hardware than other times. No different camera settings. Not changing anything from the defaults.
Again, not much information here. What is "jack it up" supposed to mean here? What do you mean by "Codec A is not compatible with version B?" You say you are seeing different results but not telling us what results you are seeing. Based on "hints" previously provided, I assumed you were using QT 7 Pro to trim content and then save the edited version to a new file container using the "Save As..." option. This workflow should save the edited content in its original compression format in a new MOV file container. However, since you do not indicate the source or output compression format, I cannot confirm this. In addition, since you do not describe your specific workflow, it is impossible to determine if you are saving all of the original data with editing pointers applied or saving just the trimmed portion of your original data. It is also unknown if there if there is an aspect ratio playback issue, a non-playback issue, or a non-playback issue in just one of the QT players. In short, you keep saying there is a problem but have not described what that problem is or how it affects players—i.e., new file won't load, plays with black screen, plays without audio, plays with incorrect aspect ration in one or both QT players. If cannot provide such information, then I would normally recommend you upload a copy of the problem file for analysis by others who frequent this forum—especially since you indicate file will sometimes "not save out" using your workflow.
What I think the issue is that when you edit clips in Pro it somehow either distorts the file or perhaps it doesn't really clip them so much as marks them? I don't know. I readily admit my lack of knowledge of codecs and the underpinnings. But basic troubleshooting would seem to pan out that using the exact same cameras and formats should beget the same results.
Again, what does "distorts the file or perhaps it doesn't really clip them so much as marks them" mean to you? Are we talking about an anamorphic file losing a PAR setting or an trimmed file displaying with its original, unedited duration? What "troubleshooting" have you done and what were its results?
I don't know. I readily admit my lack of knowledge of codecs and the underpinnings. But basic troubleshooting would seem to pan out that using the exact same cameras and formats should beget the same results... An obvious work around is to pull the original videos into iMovie (shudder). But QTPro is so much simpler to use. I'd rather get the basic stuff done there before pulling them into iMovie to titling.
Codec configurations basically determine an application's ability to read and write data. However, the workflow used when employing the software package can be equally important to achieving the result you seek. For instance, if you are using a Sony DV camcorder to record anamorphic widescreen recordings but then use QT 7 Pro to "trim" content before editing in iMovie, the workflow normally drops the "widescreen" setting and reverts to a distorted "full screen" display. E.g., Sony SD DV is encoded to a 720x480 storage matrix whether it is to be displayed as an 853x480 widescreen or 640x480 full screen clip. In a similar manner, file trimming results differ depending on the specific workflow used. For instance, 1) If you set in an out points, fail to use the "Trim to Selection" option and then "Save" the result, then the markers are saved to the original file which continues to display in it entirety. 2) If you set in and out points, use the "Trim to Selection" option and "save" the results, then the markers are saved along with all of the original data but the file only displays the "trimmed" portion of the file in players that recognize the edit markers while other players display the entire file. 3) If you use the "Trim to Selection" option and the use the "Save As..." option to write a new MOV file, then only the "trimmed" data is copied to the new file container as can be verified by checking the size of the new file.
With regard to your iMovie workaround, iMovie (like the QT X Player) now uses the PAR setting to display a scaled video width based on its current height—unlike QT 7 which uses the "Current" height and width display settings at virtually any user specified aspect ratio. In addition, iMovie edits video content using fixed project aspect ratios and is an NLE by reference editing app unlike QT 7 Pro "physical" edits.
