Ryan Knight
Forum Replies Created
-
Ryan Knight
October 27, 2015 at 1:04 pm in reply to: Can AME be configured to use all the cores available in a network?Sorry for the topic typo. Brutal hahah…
-
Ryan Knight
October 16, 2012 at 3:25 am in reply to: Text & render clips show “hot pink” instead of transparency (black)I am experiencing this problem too, while trying to export a ProRes sequence to h.264 (it also happened when compressing for mpeg-2 for DVD).
I thought it was the color space options (Default for Encoder, Preserve Source, etc), but the pink remained with each color space setting.
Did anyone find a solution for this?
Thank you.
-
Ryan Knight
July 28, 2012 at 4:17 pm in reply to: FCP7: Best video processing settings for graded ProRes 4444 material/sequenceGreat question! Did you find an answer?
-
So I tried the good old Log Out and Restart again and the Capture Scratch disk error was resolved.
Any clues about the Shake generated ProRes 4444 that won’t display in FCP 7?
-
Was there a solution here?
I just encountered this same thing.
I am running a 2TB G-drive into FCP 7 on a fully updated 10.6.8 iMac 3.2GHz i3.
In FCP 7, I accidentally opened the VoiceOver Tool (by pressing some keyboard shortcut) and couldn’t close it (using the top left corner “x”). I ignored it for a moment so I could open a 2048×1024 23.98 ProRes 4444 file I created in Shake (using Best Depth and None auto gamma adjustment). The ProRes 4444 displayed as black in the Viewer and the Canvas but the Timeline shows me a thumbnail of the clip and the clip opens fine in QTP.
So I shutdown, trashed the FCP prefs with Preference Manager, ran a Verify Disk, rebooted and reopened FCP. That’s when I discovered this same error: The scratch disk is write protected or read-only… I Get Info-ed the disk image of the scratch drive and checked-on “Ignore ownership of this drive” because it was checked-off (no check mark). Still nothing. Should it be check-on to begin with?
First timer with this problem.
1) How can I get my scratch disk to work again?
2) Why is my ProRes 4444 black in FCP?Thank you all. I envy your knowledge!
-
Fantastic!
Thanks so much, guys.
A mini test went smoothly : )
-
Ryan Knight
April 27, 2011 at 9:37 pm in reply to: Weak FCS3 performance after installing new internal HDDOk so I will do the following, because there were some issues with the OS on the original drive, that I seemingly fixed with a fresh install of SL before I TimeMachined it (which I will not do again):
I will not Clone (because of above – just in case).
Format the new 750GB internal HDD.
Fresh install of SL.
Fresh install of Pro Apps.
Manually copy files, doc, projects.
-
Ryan Knight
April 27, 2011 at 9:15 pm in reply to: Weak FCS3 performance after installing new internal HDDI am not booting from a FW400.
David recommended not cloning… ?
-
Ryan Knight
April 27, 2011 at 8:39 pm in reply to: Weak FCS3 performance after installing new internal HDDNo, no trouble all along. Only after installing an upgraded HDD and restoring it via TimeMachine.
That drive was working fine; FCP, Color, REDCINE-X, Shake in HD/2K/4K, no problem what so ever!
But now the new one has problems in FCP.
I thought cloning doesn’t “bring” problems from an old drive over to the new one. Though there term cloning seems to indicate the opposite.
Perhaps I should format the new drive, complete reinstall of SL and my Pro Apps, and then manually copy over folders and files of projects and docs?
-
Ryan Knight
April 27, 2011 at 8:13 pm in reply to: Weak FCS3 performance after installing new internal HDDHey guys,
Before starting the Cloning process, I decided to test my system and FCP running off a FW400 Lacie (my MacBook only supports USB 2.0 and FW400).
To repeat quickly, in the past, I was able to edit and color correct with FCS3 on this laptop, before the internal HDD upgrade, 1080p files in various formats, including ProRes and H264.
And now FCP won’t playback ProRes or H264 sequences (even at 1280×720!) without failing. BOTH from the boot drive and on my previously successful FW400 drive. Could it be a FCP problem or do you guys still think I did something wrong when upgrading and restoring the new internal HDD?