Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Normal? Can’t Play ProRes HQ on MacbookPro 2.66 wo rendering

  • Jeremy Garchow

    July 30, 2009 at 7:06 pm

    [Jeff Coleman] “Do you all have the latest software and MBP firmware?”

    Yes. Can you do me favor and choose a new easy setup that mathces your format/frame rate with a codec of ProRes HQ, make a new sequence and try again?

    Jeremy

  • Jeff Coleman

    July 30, 2009 at 7:17 pm

    [Jeremy Garchow] “Can you do me favor and choose a new easy setup that mathces your format/frame rate with a codec of ProRes HQ, make a new sequence and try again?”

    Did it. Same thing. Red bar with RT Video Playback Quality set to “High”. You get gray bar?

  • Jeremy Garchow

    July 30, 2009 at 7:38 pm

    Okay, one more thing. Make sure your prefs are set for an external scratch drive, then quit FCP.

    Go to your User > Library > Preferences > FInal CUt Pro User Data folder and delete the:

    Final Cut Pro Obj Cache
    Final Cut Pro Prof Cache files

    Relaunch FCP.

    Yes, I get rt playback.

    Jeremy

  • Jeff Coleman

    July 30, 2009 at 8:50 pm

    Just finished with AppleCare folks.
    Problem SOLVED.
    Apparently a corrupt preferences file in the user’s Preferences folder.
    This was more than just trashing FCP prefs. I took out all the preference files from that folder and relaunched FCP again. This time it played those clips with NO red render bar.

    Now I’m off to trying it with the IO HD attached.

    Thanks for your help.

  • Jeff Coleman

    July 30, 2009 at 10:59 pm

    Hmmmm I spoke to soon.

    Connecting the IO (no new software added since previous test) I do notice even with external video turned off that I get jittery playback.

    And after playing the clips for about 15 minutes with the IO HD active, now the red render bars are back on my HQ clips and will not play without being rendered.

    Strange.

    I’ll get back as soon as I know something. If not sooner. 😉

  • Chris Poisson

    July 30, 2009 at 11:34 pm

    Yes David, thanks for a bit of sanity.

    Have a wonderful day.

  • John Pale

    July 31, 2009 at 5:29 am

    Turn off real time scopes, if you have them turned on.

  • Andy Mees

    July 31, 2009 at 5:47 am

    Hey Jeff

    >This was more than just trashing FCP prefs. I took out all the preference files from that folder and relaunched FCP again

    For your future reference, that process is exactly what it referred to as “trashing your preferences” … there are number of helper apps around, both free and commercial, that make the process a breeze, plus add a lot of extra features (like backup and restore). My favorite is the excellent (and free) Preference Manager from Jon Chappell of Digital Rebellion:
    https://www.digitalrebellion.com/pref_man.htm

    Hope it helps
    Andy

  • Ben Holmes

    July 31, 2009 at 9:23 am

    I would have thought for a laptop system running ProRes, the drives he is using were totally sufficient. I use FW800 drives like the G_Drive often, and have never had any problems.

    Whatever his problems are, they are not drive related. My creaky ol’ 2.33Ghz MBP will play ProRes, HQ or otherwise, just fine in real time. Time for a system reinstall methinks…

    Edit Out Ltd
    —————————-
    FCP Editor/Trainer/System Consultant
    EVS/VT Supervisor for live broadcast
    RED camera transfer/post
    Independent Director/Producer

  • Jeremy Garchow

    July 31, 2009 at 3:24 pm

    [David Roth Weiss] “Read Gary Adcock’s white paper on ProRes. HQ is essentially overkill unless you are working with 2K files. “

    …and (this is often forgotten) any material that natively originates in 10bit quality or higher, including AVC-I. If you notice the new FCP7 has native AVC-I ingest, but when you put the AVC-I file in a timeline, FCP changes the timeline to ProRes HQ since there’s no AVC-I decoder.

    Jeremy

Page 2 of 3

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