Noah Weisel
Forum Replies Created
-
Guess I understand now, though I still think it’s silly. The only offense I take is the continued offense at the hands of Apple for having royally screwed over everyone who shelled out a lot of money for a G4. Their inability to make things backwards compatible for even the most basic standards of video playback (I mean common’, a DV quicktime file? Doesn’t get much simpler than that) just further serves to convince me that FCP is an overrated piece of Bloatware (as I believe Scott Billups originally and correctly called it) that neither offers the professional tools of Avid nor the simplicity and sheer horsepower-per-dollar of Premiere. If the industry weren’t so gosh-darned in love with the thing, I’d drop it like a hot tamale.
Hope that didn’t offend anyone.
-
Thing is (and maybe this is where my PC logic is being flumoxed by the bizarness that is the way Final Cut handles media), the footage wasn’t captured with Quicktime. It was captured from within Final Cut. Are you saying that the version of the Quicktime Player installed on the capturing computer actually effects the structural encoding of footage as it streams into the computer from a deck? Doesn’t Final Cut natively work with Quicktime (that is, .mov) files regardless of whether a Quicktime Player is installed on the computer at all? Wouldn’t these elements then be mutually exclusive?
Regardless, I fixed my problem by cheating. I ponied up for a Quicktime Pro registration code that let me strip the audio out of the clip and export it as an AIFF file, which then played fine in my timeline. I have to say that I think it’s absolutely ridiculous that this was necessary, though.
-
Not sure I understand how the Quicktime version would matter. The footage was not captured on this computer at all. It was a straight FCP capture that generated an .mov file for each clip. If an .mov file generated by a later version of FCP won’t play on FCP 4, well that’s one thing, but it seems a little ridiculous.
I’m unable to upgrade to FCP 5 because I’m running a PPC-chipped Mac G4. 4.1 is the best I can do. But shouldn’t a DV/DVCPro codec’d .mov video/audio file play in any version of FCP, regardless? It’s not like it was captured using some weird Avid codec or anything.
-
OSX 10.4, Quicktime version 7. But the audio works in Quicktime…it doesn’t work in FCP.
-
I just tried creating a completely new Premiere project with generic DV settings, setting the project audio at 16bit 48k. I then used a 16bit 48k PCM wav file, a completely different piece of audio than anything I’ve used so far. I made copies of the file on my local hard drive and on my external media drive. I imported both files.
Both exhibited the error on playback in the timeline.
So the error now affects ALL of my Premiere projects, not just the one I’ve been struggling with.
The only other thing I can think of that happened between when the audio worked fine and when it stopped working (besides closing Premiere and re-opening it), is that I updated my Quicktime software.
Is it possible that upgrading to the latest Quicktime version had some impact?
-
Hey, that was an awesome tip. The file size is virtually the same as my original clip, and the quality, except for some additional bluriness during quick motion, looks almost as good to the eye as the Uncompressed 8-bit clip I made!
I’m going to be using an old Mac version of Premiere 6.5 to do the offline…it shouldn’t have a problem eating the Photo-jpeg clips, should it?