FCP "bug" to watch out for...

[Kris75]

OMG!!! I had this happen to me and it just caused me a week of HELL!!! My final solution was to export a file at =.1% from 24. Everything than would be in sync. (This was before I knew of this bug)

After I learned about this bug, I tried to talk to the editor about it but he refused to believe it existed.
Thank you so much for this thread. I am not crazy! YAY

[panamajack]

24fps FCP Sebsky QT workaround . . . .

[Cheesehead]

Just wanted to update this thread as this bug is still happening and I know when it first happened I thought I was losing my mind.

It seems Sebsky tools no longer works with Lion, so I've come up with another workaround for Lion and Mountain Lion users.

After exporting your Wavs from PT (multichannel or mono), drop them into Wave Agent, which is a free multichannel playback tool available from Sound Devices website, (the people that make the location recorders).

When you drop it in you'll see that PT has not assigned a frame rate to the file.

You can edit the metadata in Wave Agent and force the file to be read as the frame rate of your project. You can also add a start TC if you wish and then save it back to the file.

Since using this method I've had zero problems with files sent to FCP editors.

The only problem is when you forget to do it!

[Leverson]

Just wanted to extend my thanks to Cheesehead for the Wave Agent tip, and to confirm that using Wave Agent to stamp the files as 24fps fixes the problem and they import into FCP perfectly after that.

This has caused me much grief in the past and the Sebsky tools no longer exist, but using Wave Agent is a quick simple solution to a really pesky FCP problem.

Thank you for posting it.

[mgoorevich]

May be we need to ask Avid why the PT wave files are not time code stemped? If it supports bwf format, it must contain fps metadata.