Strange FCP7 VO tool problem

[Ann Clark]

I’m curious how FCP7 runs for you on Yosemite. Are you also using Motion? 4 GB of memory sounds kind of small for FCP7, IMHO.

I don’t doubt Dave’s sage advice about translating audio to 48kHz, as it’s probably best to use the native sample rate. I’ve successfully used other sample rates, with rendering.

If you used the FCP voiceover tool to capture the audio, it would seem very odd if FCP couldn’t play back its own recording.

Let everyone know if you see the issue again, or if your recording turns out to be something other than 48kHz.

[Steve Dann]

Thanks for input. Definitely using 48kHz audio and can’t provoke fault with 44.1 set in VO tool. Never had a problem with 4gb ram, I rarely do anything that needs rendering. Might wind back to 10.8 as a precaution though.

[Steve Dann]

FCP seems fine on Yosemite with 4GB RAM Didn’t think FCP addressed more than 2.5GB anyway and I rarely do stuff with lots of rendering. Of course this problem may be the first indication it’s not … and this us why I have a backup Mac book running 10.8 …

[Steve Dann]

Hi Dave, Thanks once again for the ideas. I’ve decided that Yosemite is an unknown and therefore risky and reverted to !0.8 which I’ve used incident free for a couple of years.
Trouble is I’m always editing to deadlines in the next few minutes so there’s never time to ponder and try one potential solution at a time, so I’m unlikely to find out exactly was the cause was assuming it doesn’t happen again of course. I’ve taken to trashing prefs and repairing permissions as preventative maintenance … we’ll see …..

Thanks again

Steve.

[Andrew Johnstone]

I have just had exactly this problem with FCP7 on Mac OS Sierra.

We had a new temporary edit suite set up for a film I am working on in Bristol. When we cam to record the VO on a 1920/25 ProRes timeline, the audio (set to 48khz/16bit) played back at Mickey Mouse speed. Neither the editor nor the engineers at Auntie could work it out.

I brought the project file home to continue rough cutting on my system – where I have never had this problem – and the VO issue replicated itself on my system, to the answer is that it was simply a bug in the project preferences.

The solution I found was to set the VO tool to record at 44.1 khz (you can toggle this setting in the VO window in FCP7), record a test, render it, then reset the VO tool to record to 48khz. This fixed my problem…

HTH

Andy

Andy Johnstone
Wild Dog Limited
film & multimedia production
http://www.wilddogworld.com

[Steve Dann]

My solution was to reselect input even if its already selected and then never close vo tool. Minimising is fine, closing will require input to be reselected.