Is there a workaround with FCP, When I hit the capture button and the length is longer than 20 minutes the audio and video drift apart not in sinc. This is only when I hit the capture button not batch capture.
Most common reason for audio drift is capturing with your capture preset looking for audio at a different sample rate than the camera recorded it at.
For example, if you set the camera to record 48kHz sound, and capture it as 44.1kHz sound, you'll get drift.
Turn on your camera and go into the record settings and see what sample rate you have it set to record the audio at. Verify that the capture preset is set for this same sample rate.
Your welcome, but did that help? This is one of those few specific issues that always peaks my interest in some really unhealthy, obsessive way. I'm recovering from a very long week of shooting, and a very long 12 hour drive home yesterday. All of which are very strong indicators that I'm broken for the moment. But a little Beam and a good book, I'll mend. So then I can show up for work tomorrow and not be forced to fire myself...
Let me know if this helps, let me know what you find.
FYI, the "Sync audio capture to video source" option in the User Preferences won't help. That only tells FCP that you're in a film type hardware set up. That your video and audio are coming from two different hardware sources that are (supposedly) sync'ed. It has no effect when working over Firewire with digital video. I mention this cause often someone suggests turning on that option to cure audio drift. But it doesn't.
I checked out my settings and they all matched , This is going to be a big concern for my wedding projects (ceremonies) which are on the average about 45 minutes
I guess I can always break them down if I have to .
You should not be getting any audio drift at all. If the camera and FCP are all set up for the same audio settings (48kHz sample rate), there should be no drift at all. Keep checking your settings. Something is off somewhere. This is not normal behavior for FCP, nor is it a known bug.