-
Wacky, annoying iMovie HD -> FCP issue
Hey all. So, I work on an animated show for HBO handling pretty much all the back-end tech and post stuff. We’re all Final Cut here –except for the show’s creator. Here’s how the workflow HAS to go for shows he’s the main writer on. A note: yes, I know, iMovie should be out of the question. Believe me, I have tried moving him to FC Express and some other solutions but iMovie HD is the only option he will pursue and he’s the boss. So — please, if you can, avoid telling me not to involve iMovie in the process. Believe me, I know.
Here’s how it goes. The Boss downloads audio files for the session at his home — he lives out of town. He cuts the audio together for a scene in iMovie HD. JUST the audio, no picture. Sticks this iMovie project up on the server. Now what’s supposed to happen is an editor opens the iMovie project in FCP and basically rebuilds this cut using our in-house audio, properly referenced on our SAN. In other words the iMovie projects are little more than a really dumbed-down EDL of sorts for these audio sequences, which run a couple of minutes tops. The editor knows what the timing should be and where everything should land and can dig up the original files and build a new project based on this sequence. Not pretty, but it works.
Most of the time.
We have 7 FCP systems and 5 of them have Konas; two of them are assistant stations and do not. All have the same Mac Pro config, memory, video card etc. Every setting — with the exception of course of Kona-related settings — is the same on each station.
On two stations — one an assistant station and one an editor station with a Kona — these iMovie projects open up just fine. Well, not fine, but fine enough. Everything is more or less intact.
One at least one of the stations a weird thing happens. The last 10-20 seconds — it varies — get truncated. This happens consistently on this one station, inconsistently on another and not at all on at least two — the sequence is cut off 10-20 seconds short in one case but will open totally intact on another machine.
My workaround is to open this same project in FCP on one of the workstations that “works” and simply save it as an FCP project. The editor can now open this FCP project and get to work. However, I would really like to avoid this step and figure out what on earth could be the root cause. I have done a pile of Googling to no avail. I have set up this one problem station exactly as the other ones are set up in terms of FCP prefs. All versions of everything are identical on the machines that work and the machines that don’t This annoying glitch is taking an inordinate amount of my time but the Boss wants it fixed. So if anyone has any ideas, please shout ’em out.
Thanks
Michael