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 :)

Weird Blue Noise on dark areas.

Ian D said:
I'm getting the same issue on my mac book pro 2.4 GHz Intel Core i5 late 2011. Its a real pain, have it with redone and scarlet footage. I would love to hear a simple solution.
Click to expand...

I'm about 99% sure this issue is based on the GPU you're using. This definitely happens if your machine just has the Intel HD Graphics 4000 card (and no NVIDIA card to back it up). So... if you're running off a mac mini or an older laptop without a nice GPU, and you're trying to play back R3D's in FCPX, there's a pretty good chance you're going to run into this.... no idea what the cause is, though.
 
Ian D said:
Thanks Sam, I think your right, further research is proving i could be screwed.
Click to expand...

Well, one thing you can do is transcode down to proxy and edit in FCPX... your proxies shouldn't have any of the blue noise on them. Then you can maybe move to another system, flip back over to the R3D's and do your export...
 
I think my workflow will be to transcode all footage thru red cine to pro res lt or proxy, edit in fcpx, lock the pic, send xml to redcine, adjust raw and export online 422hq from there, relink in fcpx and finish. The blue is transferred to files transcoded in fcpx. Using hte old fcp would nearly be easier at this point.
 
Ian D said:
I think my workflow will be to transcode all footage thru red cine to pro res lt or proxy, edit in fcpx, lock the pic, send xml to redcine, adjust raw and export online 422hq from there, relink in fcpx and finish. The blue is transferred to files transcoded in fcpx. Using hte old fcp would nearly be easier at this point.
Click to expand...

Yeah... that sucks. This bug has been around forever... I'm surprised there hasn't been a fix for it yet. Frustrating. To really take advantage of FCPX, minimum configuration is probably a Retina MBP and 16 gigs of RAM, especially if you're doing RED work. Thunderbolt storage is really going to help too. Anything lower may cause you problems, especially for processor intensive stuff like R3D's.
 
I have a GTX Titan in my system and am getting the blue noise, so I'm not so sure it has to do with the GPU. FCPX also doesn't use the GPU for rendering, so that doesn't make sense that it would be the GPU causing it. R3D's look fine if you turn off background rendering and delete all the render files. Turn background rendering on or export/share the project and you'll get the blue noise. Even just exporting/sharing, where there's no GPU involved and rendering is done by the CPU results in blue noise.
 
Issue presents with and without the NVIDIA GPU on rMBP 15" with 16GB ram. I think it might not be a GPU issue at this point. I haven't bothered installing FCPX on any actual production machines, this was to be the test run for viability and reliability.
 
The problem is with FCPX because it plays fine in Redcine X.

It can't be GPU alone because it plays fine in Redcine X.

It is specific to FCPX

Having said that, it works fine within FCPX on my iMac 32GB RAM.

The problem only exists in FCPX on my Macbook Air.
 
I'm experiencing it on my Hackintosh, but my Macbook Pro Retina has no issues. I understand it's a FCPX issue, but Red might have insights. I assume they also have a better way of communicating with Apple than we do and could hopefully report it to Apple so it gets fixed.
 
With the new MacBook, does anyone think the issue will be resolved? Thinking the top end version with graphic card would solve the issue. But would be interested if the lower end ones could work also.

Cheers
Ian
 
I could find no resolution with my 13inch late 2011 macbook pro so I upgraded to Retina, 15-inch, Early 2013, Processor 2.4 GHz Intel Core i7, Graphics NVIDIA GeForce GT 650M 1024 MB, its only got 8 gigs of ram but it works, did a quick import export and no blue noise. Happy days.

Cheers
Ian
 
I think I've found a solution to this problem, or at least a temporary one. The way I was using it before was not transcoding optimized media and setting playback quality to "High Quality". If I turned background rendering on I'd get the blue noise. So I just tried transcoding Optimized Media and then background rendered and there was no blue noise. There's still a problem though, as I don't get the blue noise and don't need to transcode Optimized Media on my other computer with the same events and project.
 
You must log in or register to reply here.
Back
Top