Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy After Rendering All, Print to Video renders again taking the same amount of time

  • After Rendering All, Print to Video renders again taking the same amount of time

    Posted by Jack Fox on December 13, 2005 at 4:18 am

    Is this normal or is the Print to Video process confused about where to check for existing rendered files?

    jmf

    Jack Fox replied 20 years, 6 months ago 6 Members · 12 Replies
  • 12 Replies
  • Jerry Hofmann

    December 13, 2005 at 1:42 pm

    Make sure that the sequence’s render settings are all set to high. Sort of sounds like you are rendering a lower quality, and when printing to video, FCP is rendering in a high quality…? If you perform an audio mixdown before you use the print to video or edit to tape command, you shouldn’t see even that render bar when you involk either of the commands.

    Jerry

    Apple Certified Trainer

    Author: “Jerry Hofmann on Final Cut Pro 4” Click here

    Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D

  • Jack Fox

    December 13, 2005 at 2:36 pm

    If you mean the drop down menu in the left part of the sequence, it was set to “High.”

    jmf

  • David Bogie

    December 13, 2005 at 3:41 pm

    IIRC (but CouldBeWrong), Print To Video has always required the creation of a completely new media file that includes the lead-in heads, slate, countdown, program content, and tails. That’s why most of us simply roll the recorder and then hit play on the timeline.

    I haven’t bothered with Print To Tape since Apple broke the FW timecode functions for the lower-end DSR-11, those rat bastards.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Jack Fox

    December 13, 2005 at 5:33 pm

    So, for purposes of Print to Video, I really doesn’t matter if the timeline is rendered or not, true?

    jmf

  • Rick Sebeck

    December 13, 2005 at 6:07 pm

    I have found the culprit of the “re-render for lay to tape” to be clips that are disabled. I took a sequence that was fully rendered out, everything set to high, ect ect. and even made sure my lay to tape wasn’t creating bars tone or slates… and I got the wasted minutes of “building video” for EACH time I layed it off. That gets annoying when you need to make 5 masters!

    I don’t know how I figured it out.. but I went through and deleted all off my disabled (grayed out) clips. Hit print to tape.. and beleive it or not.. it just started right away!

    Give it a try!

  • Jack Fox

    December 13, 2005 at 7:31 pm

    That’s interesting. Did you find any difference in the rendering option used? Do you use “Render All” “Both?”

    jmf

  • Jeremy Garchow

    December 14, 2005 at 2:20 am

    In your sequence>render settings menu. make sure that all of the options are checked, including full. This will make sure that FCP is rendering even the real time effects. This is a good habit to get into. be sure to check the render all and render selection menus.

    Jeremy

    ———–
    G5 Dual 2Ghz <> 4GB RAM <> FCP 5.03 <> Kona 2
    ATTO 42XS <> Huge Systems 4105 Fibre
    OS 10.4.2 <> QT 7.0.3

  • Jack Fox

    December 14, 2005 at 4:27 am

    “Full” was not checked. I will try it out tomorrow. Thanks

    jmf

  • Jeremy Garchow

    December 14, 2005 at 4:32 am

    That’s probably what it is. Even though it’s full resolution, FCP likes those rendered for output to insure that it won’t drop frames. This way, FCP is actually laying off hard media instead of a real time “vapor media” effect.

    Hope it works out for you.

    Jeremy

    ———–
    G5 Dual 2Ghz <> 4GB RAM <> FCP 5.03 <> Kona 2
    ATTO 42XS <> Huge Systems 4105 Fibre
    OS 10.4.2 <> QT 7.0.3

  • Jack Fox

    December 15, 2005 at 4:20 pm

    Well it was weird. After checking “Full” in Render All and running “Print Video” it took twice as long. I did fail to render so the Print Video process went through the first time and rendered the sequence, which took a long time since it was doing a “Full” render, and then another time (even longer than the first) before it was ready to send it to the camera.

    jmf

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy