[Andrew Fettis]

UPDATE
The compressor solution only seemed to work once, then not again. The real solution to this is from posts elsewhere on creative cow. My computer and most of it’s programmes (including Compressor) is set to work 25P (British standard). So actually what’s happened is the some of the sound was imported when the project (easy setup) was set to 25P and some when is was set to the new frame rate I’m working with for this project only, which is 24P. Hence the different durations. WAV files don’t inherently come with a frame rate attached, they change according to environment. So what I’ve had to do is make sure easy setup is 24P, then re-import all wavs at 24P, then where necessary re-sync the sound. It’s easyset up which determines which frame rate WAV (and other) sound files are imported as.

So I suspect that all those having problems have changed their easy setup and forgotten not realised, which is why the sound goes all over the place.

[Andrew Fettis]

Hi

I’ve been having same problem and have found a solution.
So I’m using last released version of FCP 7.0.3, working on H264/ 23.98 Video (naughty naughty no transcoding) with audio 48Mhz 24bit. My audio was recorded separately to video recorded on a 7D. I’m not sure what the sound recording device was, since I received the files by online transfer in 2 batches. All was fine until I had to move the media onto another drive, both were FW800. Then when I try and relink I get Attributes of original don’t match. Strangely one set of audio was fine, and the other not only has slightly different time-codes but different durations. I try re-importing the offending sound files, (not relink) to see what duration FCP thinks they are now. It’s consistent with its new duration. I try stripping off timecode in QT pro. No good. Try changing all the easy setup etc, no change.

SOLUTION
I take all the audio into compressor, it thinks it’s the original duration, and so I export all as a aiff, same bit rate as original, relink the new files and all is back to normal, phew. It’s probably a error with how NTSC assigns frame rates to audio. I’m in the UK so normally everything is 25 and we don’t get this problem, even audio is all 25 fps. This was all media from the US, and at 23.98. Because of the variable frame rates employed in the US I believe frame rates are more flexible on the audio?