Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy 8-bit, 10-bit or high-precission

  • 8-bit, 10-bit or high-precission

    Posted by Michael Harrington on August 24, 2011 at 2:01 pm

    I’m working on a 210 minute Dual 9 DVD and trying to head off what I think will be a problem when it comes time to output final QT.

    My sequence is 1920×1080 HDTV 1080i (16:9), square, upper (odd), Apple ProRes 422, 48kHz, 24-bit. Rendering in 10-bit material in high-precission YUV.

    I have several sequences to join together, for now they are individual segments. I’ve noticed when I leave several of them open to render over night I often get a Out of Memory warning, not always. I shut down, restart and continue without issue.

    In a few days I’ll need to make QT for DVD Author and another set for Broadcast and want to deal with any problems now.

    I have no large still image files, the project is XDCAM EX, HDV, AIFF and Graphics Animation files only. All graphics were generated in AE, a few are 2500×1080 PNG, all others are 1920×1080 Animation.

    Any thoughts? Deadlines looming and trying to head off problems prior to final output.

    Michael Harrington
    Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Snow Leopard, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, 1.25TB Esata, Numerous FW 800 external drives, MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors.

    Rafael Amador replied 14 years, 5 months ago 5 Members · 10 Replies
  • 10 Replies
  • Jerry Hofmann

    August 24, 2011 at 3:46 pm

    Stay right where you are and finish.. keeping the project file small will help with RAM problems. If you have to, you could export 1/2 of the movie to a self contained movie, then the other half to a movie, then import them back to FCP, and marry your “master sequence” that way, with fewer clips in it. You’ll lose no quality.

    Jerry

    Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann

    Current DVD:
    https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup

    8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.

  • Michael Harrington

    August 24, 2011 at 3:57 pm

    Thanks Jerry, so I assume all my media sizes and sequence settings are correct? I have a vague recollection of FCP limitations on still graphic size and suspected the few I have 2500×1920 was a problem.

    I’ll have no choice but to compile all edited clips into 2 new sequences for Dual Disc DVD, both will be approx 1:45:00 each. This is necessary in order to deliver for DVD and Broadcast 2 version, texted fully mixed and 4-ch unmixed textless.

    I can’t afford to wait till output time to discover problems and suffer the dreaded Out of Memory error, so needed to check on my sequence settings, etc.

    I hear what your saying about output segment, import and reassemble, this has not been my workflow so far and with all the versions I need to layout, audio channel assign, render and output will be time consuming beyond my deadline.

    In the meantime I’ll keep my fingers crossed I don’t have a piece of corrupt media or a file to large for FCP.

    Michael Harrington
    Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Snow Leopard, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, 1.25TB Esata, Numerous FW 800 external drives, MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors.

  • Jerry Hofmann

    August 24, 2011 at 4:32 pm

    FCP has a limitation of 4000 pixels in either direction, so you’ve no problem…

    Keep going, but know that you may have to put out QT’s which are sections of the movie then marry them to make your final outputting sequences.

    Out of memory errors are either files from photoshop with blank layers in them (FCP will report an error) or corrupt media, usually render files.

    Jerry

    Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann

    Current DVD:
    https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup

    8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.

  • Rafael Amador

    August 24, 2011 at 5:25 pm

    About “8b/10b/High Precision”: Set “Render ALL YUV in high precision YUV”. Other wise your 8b stuff (XDCAM, HDV,..) will be rendered just at 8b, even when the sequence codec was 10b.
    rafael

    http://www.nagavideo.com

  • Michael Harrington

    August 24, 2011 at 5:35 pm

    And what will it render at when set as you suggest. Looming deadline so I need to choose wisely and avoid hours of re-renders, but will do what it takes to keep quality and avoid the dreaded out of memory.

    Michael Harrington
    Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Snow Leopard, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, 1.25TB Esata, Numerous FW 800 external drives, MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors.

  • Michael Harrington

    August 25, 2011 at 12:45 am

    FYI, I just completed a render and out put of 1:45:00 sequence without Out of Memory issue. I kept settings as described earlier.

    yea, they oda type

  • e ths.

    Michael Harrington
    Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Snow Leopard, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, 1.25TB Esata, Numerous FW 800 external drives, MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors.

  • Neil Ryan

    December 14, 2011 at 2:58 am

    Hi Jerry,
    Came across this thread while doing research, and wanted to ask a question:
    [Jerry Hofmann] “FCP has a limitation of 4000 pixels in either direction”

    What do you mean when you use the word ‘limitation’? FCP can import larger frame sizes than 4000×4000.
    I know that a Project with many large still images can create problems and, as I’ve got another such Project coming up (hence the research) I’d like to try to avoid problems I’ve had in the past.

    And while I have your attention, can I ask your opinion about dpi in still images for FCP.
    The FCP user guide says “The dimensions of a video image are dependent only on the number of horizontal and vertical pixels used in the image. Pixel dimensions alone determine the resolution of a video image.” It goes on to demonstrate a test between 2 files; one 72dpi and the other 300dpi and how there’s no quality difference in FCP. Accepting this, I note that, in the case of the 2 files of different dpi, there is a difference in the file size. So, does it create less drag on FCP if imported graphics use a lower dpi and therefore smaller file size?

    Regards,
    Neil.

    – – – – – – – – –
    Neil Ryan
    Post Production Protagonist

    – – – – – – – – –

  • David Roth weiss

    December 14, 2011 at 9:02 am

    [Neil Ryan] “What do you mean when you use the word ‘limitation’? FCP can import larger frame sizes than 4000×4000.”

    No, FCP does not and cannot handle frames that exceed 4000 pixels wide.

    And, either forget about about DPI altogether, or set it at 72 and then set the pixel dimensions of your stills.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    Don’t miss my new Creative Cow Podcast: Bringing “The Whale” to the Big Screen:
    https://library.creativecow.net/weiss_roth_david/Podcast-Series-2-MikeParfitandSuzanneChisholm/1

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

  • Neil Ryan

    December 17, 2011 at 3:18 am

    I know that you CAN import and USE still images larger than 4000 pixels (H or W).
    I also know it causes problems, of the nightmarish type.
    But I can’t find anything in the FCP7 online user manual to definitively say, “here’s what you can or can’t do.” And therefore, while I have learnt the extreme that can cause problems, I don’t know what is the correct procedure.
    So what I’m chasing, is the actual correct procedure for using still images in FCP7.
    .
    Is it documented anywhere? Where does the 4000 px limit come from?
    I need something I can take to a team of editors, so that we all work from the same page.

    Regards,
    Neil.

  • Rafael Amador

    December 17, 2011 at 4:21 pm

    Hi Neil,
    A lot of what we know about FC has been learnt through long years of testing, making mistakes and trying again.
    Apple has been very mean on releasing accurate info about the application. For example, everybody new that QT Conversion worked in just 8b, but Apple has officially recognized that just few months ago, after the release of FCPX (and in order to dismiss FCP in front of FCPX).
    I really don’t remember now if there is any doc where Apple set a limit size for still, but the video limit size officially is 2K.

    [Neil Ryan] “But I can’t find anything in the FCP7 online user manual “
    FCP 7 manual is crap.
    Try to get FC 6 manual.
    From FC 4.5 HD till FC 6 Apple was able to put together a quite decent manual with a lot of info not just on FC but in video in general (color, formats, interlacing, compression..).
    By FC 7 they decided to get rid of it, probably thinking that the video editor of the future (FCPX) doesn’t needs to know nothing about video.
    rafael

    http://www.nagavideo.com

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