[Mitchell Goldman]

I had this problem and it made me nutz! By the process of elimination I discovered that the issues was a voiceover track that had been recorded at 441.kbps. Check your audio files! If one or more are recorded at 44.1 then either transcode it before you put it in your sequence or do the following after picture is locked (your audio will no longer be editable):

1. export either a .wav or .aif file of the entire sequence of your audio at 48k 16-bit stereo or whatever your sequence settings say.

2. import that .aif or .wav file and lay it on a new, clean, unused audio track

3. turn off all your other audio tracks

4. check for A/V sync

4. export media.

Good luck!

[Mitchell Goldman]

I have bad news for you, Anthony: Apple stopped supporting that deck years ago (I want to say around the time of FCP 5 or maybe 6) and I don’t think it will ever work for you.

I was a confirmed FCP/DVCPro enthusiast, then I upgraded FCP and all of a sudden the deck stopped working. I tried every possible permutation of ports and cables and those cockamamie menu settings and re-booting and re-plugging but nothing worked. I asked around (as you have) but no one seemed to know.

I Finally started going through all the boilerplate documentation and, sure enough, I found a table somewhere of the hardware that Apple does support and my beloved 230H was conspicuously absence. Someone at Apple ultimately confirmed that it was a lost cause.

I was mad. How could they do that? It’s a great piece of gear and I paid some big bucks for it. I ended up selling it to a buddy of mine who had an Avid and he was very happy with it but that did not eliminate the sting of getting screwed by Apple.

I hope for your sake that I’m wrong (but I’m not).

[Mitchell Goldman]

That did the trick! big thanks–