Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

My RED footage is Green in Final Cut Pro

M

marcdcx

Banned
Joined
Sep 30, 2008
Messages
2
Reaction score
0
Points
0
I have the latest codec from the RED website installed but I continue to have issues editing my footage in Final Cut Pro (latest version). While I'm trying to edit the footage I've been having major problems. The footage looks green and is split down the middle. I have a picture link to show what I'm talking about.

http://tinypic.com/view.php?pic=20kda4o&s=5

Does anyone have a clue what's going on? Google inquiries were of no help.

Thank you!
 
RED footage Green in FCP

RED footage Green in FCP

When rendering proxies, I found that the Sequence settings for video processing, when switched to 8 bit, rather than 10 fixed my green problem. The green problem reared it's head up once using Prores, I restarted FCP and the problem went away.
 
Having the same problem.

I have a sequence given to me that was cut with proxies (I usually bake ProRes Quicktimes), and maybe half of the clips in the sequence are green and pink, with tiny vertical lines in the image, exactly like the screenshot marcdcx posted.

I went to change the video processing setting to 8-bit, except it's already on 8-bit. Funny thing is when I change it, the image is fixed for a split second, then changes back to green. What codec should the sequence be set to? It's set to ProRes 422 (HQ), and changing it to REDCODE doesn't seem to do anything, but I didn't think it would fix it anyway.

The frames aren't rendered either, so this isn't during playback. I'm manually reconnecting the clips, and the frames are green as I scrub around the sequence. Not sure what's going on.

Edit:
Ok, this is just weird. I went back in to FCP, and ALL the clips were green. I switched to another sequence tab and came back, and now they're all displaying correctly. ::shrug::
 
Hi there,

Has anyone happened to figure out a solution to this problem? I am having the same issue - prores files brought in through FCP's log and transfer, and when I dump the render files it helps, and if I switch sequences it helps, but moments later, the problem returns.
 
In canvas monitor you can check the "show excess luma" and i think it will solve the problem. That worked for me.
 
This is very easily fixed. Just go back to redalert and make new proxies. This sometimes happen when you move your sorce files around.
 
Not sure if this helps you, but I have a similar problem where the clips PLAY fine, but when paused are all green, same thing when scrubbing through the timeline.

Found this thread: http://reduser.net/forum/showthread.php?t=25929

They said it was a problem with older graphics cards (I have a Mac Pro with an Nvidia 7600GT), so I just ordered the 8800GT upgrade from Apple.


Bye,
Christian
 
Christian Foerster said:
Not sure if this helps you, but I have a similar problem where the clips PLAY fine, but when paused are all green, same thing when scrubbing through the timeline.

Found this thread: http://reduser.net/forum/showthread.php?t=25929

They said it was a problem with older graphics cards (I have a Mac Pro with an Nvidia 7600GT), so I just ordered the 8800GT upgrade from Apple.


Bye,
Christian
Click to expand...

Hi, just wanted to say that it worked for me.


Be,
Christian
 
The image linked above has long since been taken down, but by the sounds of it, I am experiencing a similar problem...

http://assaultonmountfuji.com/uploads/green.png

Below is FCP's crash report:


Process: Final Cut Pro [5348]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.2 (7.0.2)
Build Info: FCPApp-000000000~8
Code Type: X86 (Native)
Parent Process: launchd [183]

PlugIn Path: /Library/QuickTime/REDCODE.QT.component/Contents/MacOS/REDCODE.QT
PlugIn Identifier: com.red.redcode.quicktime
PlugIn Version: 3.9 (3.9)

Date/Time: 2010-07-07 15:45:43.140 -0400
OS Version: Mac OS X 10.6.4 (10F569)
Report Version: 6

Interval Since Last Report: 348441 sec
Crashes Since Last Report: 12
Per-App Interval Since Last Report: 206646 sec
Per-App Crashes Since Last Report: 11
Anonymous UUID:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Any advice, of any kind, would be highly appreciated. I tried changing bit depths, re-logging, everything mentioned above. When I launch FCP, I get about 5 minutes of editing before the computer goes hulk on me. As for workflow, I am following the "native" workflow in the FCP whitepapers.
 
We saw this issue today as well. We are pretty sure it's a proxy issue since we get the same result when we drag the proxies into Compressor or open them in the Finder.

I have to say, we never had these issues until we updated our QT codec to support MX sensor media, and since then we have seen tons of issues opening up older jobs where all the proxies need to relink, etc. This has been a huge time waster and I really hope it gets fixed soon.

bk
 
mcshyd said:
Have you tried using a version of REDCODE prior to the MX update?
Click to expand...

We have not tried rolling back our codec since we are actively working with both MX and non-MX footage.
 
mcshyd said:
Right.

Well I installed yesterdays update to the FCPS installer from red and things seem to be working. Fingers crossed.
Click to expand...

Great,will check it out.

I love how even though I signed up for emails when software goes up, I am not getting any.
 
The green issue seems to be fixed, but now FCP crashes every ten minutes. I don't think this workflow should be included in the FCP whitepapers. I'm seriously considering Premiere.
 
We've had the problem as well. Toggling Excess Luma on and off helped a bit sometimes, but wasn't really the solution and still annoying. All problems have disappeared as soon as we installed Snow Leopard. If you are not on Snow Leopard yet, an upgrade might be worth a try.
 
I'm using red codec 3.9, which appears to be current. I'm also on Snow Leopard. I'm going to try using an older codec to see if it's more stable.

PlugIn Path: /Library/QuickTime/REDCODE.QT.component/Contents/MacOS/REDCODE.QT
PlugIn Identifier: com.red.redcode.quicktime
PlugIn Version: 3.9 (3.9)
 
You must log in or register to reply here.
Back
Top