Weird bug in FCPX 10.0.3

B

Brian@202020

Veteran
So I just got done editing a short for a local film festival and I think I found 2 separate bugs at the same time. The film is 8 minutes to the frame exactly, festival rules is it can not be over 8 minutes, and the last 3 seconds of audio is clipped on export. Even tho I couldn't (due to time limitation) I decided to do a test and trouble shoot by adding slug, but for some reason the audio still clips 3 seconds earlier than it's supposed to. In FCPX there is no way to add 3 seconds of audio slug so I just put 3 seconds of another audio clip and linked it to the new ending video slug clip. The additional audio clip was ignored as well as the last 3 seconds of audio from the main clip again. Then I remembered that when I exported the FCPXML to Resolve the first 3 seconds of slug from the film was ignored in Resolve and when I exported the FCPXML from Resolve back to FCPX it came in starting with a 3 second timecode. I than changed the timecode to start at zero again. I figured this 3 second clipping of audio and the 3 second timecode change can't be a coincidence. I started the timecode at 3 seconds again, the audio clipping disappeared, and I had a successful export. So the 2 separate bugs are listed below.

Bug 1: When exporting and Importing an FCPXML to and from Resolve, any beginning slug is ignored and in the round trip, and you'll get a timecode change in the amount of the missing slug. If you try to change the timecode back to zero, it will clip the last non slug attached audio clip in the amount of the original missing slug.

Bug 2: If you attach audio to slug at the end of a project it get ignored on export.
 
There's a problem with the XML generated from Resolve, I think. I had the same problem, except audio didn't export for the last minute of a 4 minute project - very frustrating. I ended up going back to the original (ungraded) project, exported the audio separately, then exported the video from the project from Resolve, and stitched both together.
 
Found another weird audio related bug. When tweaking keyframes adjusting the audio levels the built in keyboard on my Macbook Pro will stop working. It doesn't do that with any other programs. I've had to restart my computer 5 time in the last hour.
 
You must log in or register to reply here.
Back
Top