-
Why is my audio hitchhiking?
First I will cut a single piece of 48k aiff audio into an FCP 5.03 timeline.
Then I will cut around it, never actually changing or affecting my original audio cut.I go to play the sequence and the audio has basically cut itself and re-arranged itself to its own desires. There are no actual cuts in the timeline for the audio, but I’ll have anywhere from 2-3 individual ghost cuts.
The only way to fix the audio so far that I’ve found is to re-cut it in.
Whats up with this? Anyone have any idea?
Thanks.
-steve -
7 Replies
-
It’s almost always a question of incorrectly captured media or creating subclips that reference each other. You may have two clips with the exact same name. It’s hard to debug from here. Try it again but unlink the audio from the video. Try it again but export a clip as self-contained and reimport the new media.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
I’m having the exact same problem. I’m assisting on a series of features, and 2 of our 4 workstations are starting to exhibit this problem. (All using the current updates of OS and FCP 5, 48khz timeline, DVCPRO HD 1080p picture).
The audio has been digitized correctly, there are no nested sequences, no effects, nothing other than a straight insert — and spontaneously, the audio recuts itself without any rhyme or reason. Basically, the clip reassigns itself a new remix of the original media, so people may repeat dialogue or spit out a series of unrelated syllables.
I have found that using render manager to delete the sequence’s render files will fix the problem, but of course I wish it wouldn’t happen in the first place. I wasn’t expecting this to fix anything, because the audio in question didn’t need rendering, but when you stumble on a solution….
Anybody have more information on this?
-karim
-
You see, I thought that too… I check every file that has an issue, and there’s nothing incorrect about them.
Then I wondered if it had to do with an incompatibility between aiff’s created under an older Quicktime, only to discover that it happens just as often, if not more often with aiff’s created in QT7.
The only other related issue that I’ve found is that FCP cannot read the waveforms of some of my older AIFF files. Anytime it can’t read the waveform I have to re-export the AIFF exactly as is with no changes and replace the “broken” one. Then FCP can read it. That leads me to beleive that there’s a major change between QT7 and the older versions in the audio realm… and if there are major changes, I’m guessing there are some sneaky bugs scampering about.
Who knows, maybe Apple is just one step closer to the “Edit” button that every new producer talks about… and they accidentally left some code in FCP5.
-
There’s something odd about your two setups and there’s something in common between them. I cannot imagine what it might be.
Have you tried to select the audio clip only and Remove Attributes?
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
thanks for responding.
>Have you tried to select the audio clip only and Remove Attributes?
There are no attributes applied… it’s just a single layer of plain clips with no effects or modifications applied.
To my lovely joy, this problem has also creeped into the picture!
-karim
-
We’re only experiencing it in a handfull of projects that were upgraded from FCP4 projects.
By chance is that where your project originated? -
No, it started in FCP 5.0.2.
In asking around, a colleague of mine mentioned that he has experienced similar problems with 20 minute (and over) sequences… he has come to expect FCP to randomly reassign footage when you’ve had the job running for a couple of months. He never found a solution for it.
Guess I’ll give Apple a call on monday… I’ll post to this thread if I get either a solution or a caveat.
-karim
Karim Zouak
Reply to this Discussion! Login or Sign Up