Print To Video Error

[Thaxter Clavemarlton]

Try re-connecting your set-up by NOT sending the FW to the VCR looped through the HD.
That can create for some serious data-routing bottle-necks.

Connect the DV recording device directly to a FW port on the Mac.

Also, external FW HD’s are NOT “reccognised” by Apple for use with FCP (although a LOT of editors use them very successfully).

Lastly:
There is a function in FCP that is often overlooked… and it can help with many audio and video “skipping”, “sticking” and “missing” problems.

You should “Mixdown” the Audio for playback before you dub out of FCP, or during the edit, if you have audio/video stuttering, drop-outs or freezes.

NOTE: Mixdown has even been demonstrated to help with slipping, skipping problems (or “missing” audio clips) for files being EXPORTED as QT (or similar) files out of FCP.

First, SELECT ALL of your audio tracks (highlight them) on the timeline, then:

Sequence Menu > Render Only > Mixdown.

You should see a dialog box telling you its rendering.

It might seem to make little sense that “Mixing down” even simple audio tracks will “fix” complex video “freezes” or random audio dropouts to tape or export, but it CAN.

NOTE: It does not matter of you only have one audio track, if there are random freezes during output, you should try the Mixdown.

[Jeff Lazzarino]

I tried the mixdown but no luck. It played for about 40 seconds then crashed.

I’m using an external hd for the first time and I think this is the problem. Can some one tell me how to get my project off the ext hd and on to my video drive?

Thanks

[Rick Dolishny]

Exit the FCP app.

Copy your capture scratch folder from your ext. HD to any other drive you think might work better.

Unmount the suspect drive.

When you relaunch the FCP Project it will complain about missing media… or maybe not. If it does, relink it by telling it the drive you have moved to media to. There is a check button to link all missing media the the new folder you specify.

You will likely have to re-render your renders, otherwise you’re on the new drives so go for it.

Good luck!

– R

[Debe]

You can also try exporting the timeline to your internal hard drive as a self-contained QT, then reimport back in and play that new clip that is generated back to tape. However, the problems you are having may persist in an export. The only way to know is to try!

If any of the advice here works, for next time, you may want to consider upping your RAM. 512 is just barely enough to keep FCP breathing. If this is a complex timeline super-low RAM may be adding to your issues.

A gig of RAM is recommended, and 2 is better. I’ve ever heard some say that 2.5 has some magical properties.

Just a thought…

debe

[Andy Mees]

yeehah! THREADJACK ON!

you’re right 2.5 Gb is kinda magical in that FCP can’t address more than 2.5 Gb of RAM
i’d give 3 Gb the truly magical nod tho … that gives FCP all it can use and still leaves 512MB for the OS

ok, threadjack off … sorry debe 🙂

[Debe]

Maybe FCP can’t see it all, but when you’ve got FCP, Motion, LiveType and Photoshop all open….

debe