This discussion is locked
B. Leathers
Level 1 (0 points)

Q: ProRes renders out as noise

I am currently working with 4K 4444 footage. It reads just fine, but once I try to write out in either 422 or 4444 I get noise. This only happens on my laptop.
MacBook Pro
2.4 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3
OSX 10.6.5

My desktop writes it just fine
MacPro
2 x 3 GHz Quad-Core Intel Xeon
5GB 66.7 MHz DDR2 FB-DIMM
OSX 10.5.8

Shake 4.1


I'm going to be travelling and will not be able to lug the 8-core around.


-Bob

MacBook Pro, Mac OS X (10.6.5), Dual 2.4 GHz; 4GB RAM

Posted on Dec 31, 2010 2:01 AM

by Patrick Sheffield,Solvedanswer
Patrick Sheffield Patrick Sheffield
Level 7 (29,175 points)
A:
Yeah - I'd contact Apple - My FCS3 serial doesn't work either. And I have no idea where my FCS2 serial is...

Patrick

Posted on Jan 4, 2011 12:05 AM

Close
B. Leathers

Q: ProRes renders out as noise

  • All replies
  • Helpful answers

  • by Patrick Sheffield,

    Patrick Sheffield Patrick Sheffield Dec 31, 2010 10:50 AM in response to B. Leathers
    Level 7 (29,175 points)
    Dec 31, 2010 10:50 AM in response to B. Leathers
    Didn't 4.1.1 fix this?

    Patrick

  • by stuckfootage,Helpful

    stuckfootage stuckfootage Dec 31, 2010 11:28 AM in response to Patrick Sheffield
    Level 4 (3,040 points)
    Dec 31, 2010 11:28 AM in response to Patrick Sheffield
    Patrick Sheffield wrote:
    Didn't 4.1.1 fix this?


    Yep. Bob, try dragging your copy of 4.1.1 from your desktop to your laptop.

    If you can't get it to work, you can always use a Bytes node to force it to 8-bit before the FileOut.

  • by B. Leathers,

    B. Leathers B. Leathers Jan 2, 2011 12:21 AM in response to stuckfootage
    Level 1 (0 points)
    Jan 2, 2011 12:21 AM in response to stuckfootage
    Hm, I'm now away from my desktop (in fact, 1000 miles away) so I don't have access to 4.1.1. I looked at some earlier posts and someone requested a stand-alone 4.1.1 update. Apparently one of the pro apps update included 4.1.1, however I'm up-to-date on my updates. Is there any other way I can obtain it? I'd personally like to see if I can get 4.1.1 to render it out before I force it to 8-bit.

  • by stuckfootage,Helpful

    stuckfootage stuckfootage Jan 2, 2011 10:48 AM in response to B. Leathers
    Level 4 (3,040 points)
    Jan 2, 2011 10:48 AM in response to B. Leathers
    Bob, I would love to upload it, but I don't think Apple would like that.
    If you have your FCP serial, you can use this link:
    http://support.apple.com/kb/DL756

  • by B. Leathers,

    B. Leathers B. Leathers Jan 2, 2011 3:20 PM in response to stuckfootage
    Level 1 (0 points)
    Jan 2, 2011 3:20 PM in response to stuckfootage
    I tried my FCP Studio 2 registration code to no avail. So I tried my FCP Studio 3 registration code and that also didn't work. It claims it's "not valid," which I checked and double checked for errors while typing. Could it possibly be because I registered it under Robert instead of Bob and my mac.com address is under Bob?

  • by Patrick Sheffield,Solvedanswer

    Patrick Sheffield Patrick Sheffield Jan 4, 2011 12:05 AM in response to B. Leathers
    Level 7 (29,175 points)
    Jan 4, 2011 12:05 AM in response to B. Leathers
    Yeah - I'd contact Apple - My FCS3 serial doesn't work either. And I have no idea where my FCS2 serial is...

    Patrick

  • by B. Leathers,

    B. Leathers B. Leathers Jan 4, 2011 6:05 PM in response to Patrick Sheffield
    Level 1 (0 points)
    Jan 4, 2011 6:05 PM in response to Patrick Sheffield
    I just contacted Apple and he verified a weird issue that may also be prohibiting my ability to update to 4.1.1. OS 10.6.5 doesn't seem to recognize Shake as an application, that would make sense why my pro updates are up to date while Shake isn't. I'd have to downgrade to OS 10.5.8, but I really don't want to have to do a complete wipe right now. My client seems to be okay with an 8-bit 4x4 at the moment. So, that's the route I'll be taking for now.

    Not quite a "solved" issue yet, since I'd still like to be able to output at >8-bit but I know what to do now to solve it. So, it's solved enough, hah hah. I'll probably reinstall some day later. If that doesn't work look forward to my return!

    Thanks everyone for the help.

    Message was edited by: B. Leathers