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

shocking blue noise in Standard-processed Redcine quicktime files

Mark Pugh

Mark Pugh

Well-known member
Joined
Feb 25, 2007
Messages
1,485
Reaction score
0
Points
0
Website
www.markpughfilms.com
Processing at Standard is giving me nasty blue noise in certain areas of the picture - areas of a lot of chroma - yellow or green.
It is not there in Draft Mode, or Full Mode
I cannot transcode a full day's work overnight in Full Mode.
An Hour's footage I can do overnight so is the most sensible for offlinine editing the next day.
I'd really like to be able to use Standard
I can process about three frames per second, and Full is only about one frame every two seconds.
Anyone else getting this kind of noise using Standard?

I'm not altering anything in curves, Exposure, or anything else.
Trying to output 4k files at Red2k.
On a brand new Macbook Pro 17" with 4GB Ram.
 
I just changed the project settings and output settings to 1080HD, but did not change scaling of shot.
Same problem
Tried again and changed shot scaling to Fit To Width.
Problem has gone.
Is this a known problem with creating Red2k- sized quicktimes.
Right now I'm throwing away hundreds of files and many hours of transcoding.

Processing at Standard has also been given me the "frozen first frame" on all subsequent files after successfully transcoding the first file of a sequence.
Processing at full also seems to fix that, but it's just too slow for the workflow on this top-specced Macbook Pro.
 
I've never seen it before. What build were you on when you shot it?
 
Mike Prevette said:
I've never seen it before. What build were you on when you shot it?
Click to expand...

I've got it on dozens and dozens of quicktimes, as I say, all when processed with Process Standard output setting.
I'm now re-doing some of them as 1080P quicktimes without the issue, but with the frozen-frame issue after a file or two.
BTW it happens if I export as TIFFS as well.
Shot on Build 15 (the one previous to the release build)
The noise is not evident on opening the R3D in Redcine, or on exporting with Process:Full
I can't get a good, fast workflow happening here at all, though.
 
It looks like some kind of math error where the blue channel wraps around from black (0) to full-on (255). Or the equivalent in 12 or 16 bits.
 
I've taken the files to my other Macbook Pro - same crap results with standard processing. Same frozen frame in quicktimes after, sometimes, half a file.
I re-installed Redcine on this computer before doing this.
I simply have no decent, overnight workflow here. I've been having a hard time of it with these 400 files from 3 days shooting for a week and a half now.

Can anyone who has anything to do with RED or Redcine respond to this, please?

I'm going to have to keep posting until I get a result.
I have a camera here that I want to be able to use professionally, and am finding it very difficult. Between Redcine and codec errors on the camera, it is actually getting harder and harder.
I don't want to seem like a miserable a**hole, but I've got nothing to lose. I just can't fathom why Jim can't invest a bit more on getting issues such as this fixed.
Right now, I don't give a damn about Scarlet, or RedRay, or Epic (well, maybe Epic...). I just want to be able to use my Red One efficiently.
 
markp said:
I've taken the files to my other Macbook Pro - same crap results with standard processing. Same frozen frame in quicktimes after, sometimes, half a file.
I re-installed Redcine on this computer before doing this.
I simply have no decent, overnight workflow here. I've been having a hard time of it with these 400 files from 3 days shooting for a week and a half now.

Can anyone who has anything to do with RED or Redcine respond to this, please?

I'm going to have to keep posting until I get a result.
I have a camera here that I want to be able to use professionally, and am finding it very difficult. Between Redcine and codec errors on the camera, it is actually getting harder and harder.
I don't want to seem like a miserable a**hole, but I've got nothing to lose. I just can't fathom why Jim can't invest a bit more on getting issues such as this fixed.
Right now, I don't give a damn about Scarlet, or RedRay, or Epic (well, maybe Epic...). I just want to be able to use my Red One efficiently.
Click to expand...

I would try exporting with Half Debayer in RedAlert or Redline. It sounds like that might be helpful and fast.

IBloom
 
I've just had this same exact blue problem, in addition to the transcoding issues on my MacBook Pro.

The footage is 4K 16:9 so I can't use REDALERT or REDLINE. The blue clipping/noise/crap problem is still present on "Full" processing.

For some reason the blue isn't present in tiff outputs, but is present in 1080p ProRes outputs when the time line is set to 4K 16:9, but not when it is set to 2k 16:9.

I am reaching the end or my tether with this.

Some feedback from Red Support? REDCINE coders?
 
markp said:
I'm a cinematographer, not a coder.
Click to expand...

The two are not mutually exclusive ;)

I've written custom scripts previously to get these tasks done for consulting clients. I'll be building a solution into Crimson in the next couple weeks. If you need this done "now" then I can take the time to do it. In the meantime just see if rendering one clip in RedAlert would in fact solve the problem.

Cheers,
Ian
 
ibloom said:
The two are not mutually exclusive ;)

I've written custom scripts previously to get these tasks done for consulting clients. I'll be building a solution into Crimson in the next couple weeks. If you need this done "now" then I can take the time to do it. In the meantime just see if rendering one clip in RedAlert would in fact solve the problem.

Cheers,
Ian
Click to expand...

Sorry Ibloom, I'm sure they're not mutually exclusive. I just mean that being one shouldn't be a pre-requisite for being another...
Can't get RedAlert to open files... Reinstalled the app with same results - crashes on opening a file. I can't see how it would solve my problem, though. I can't sit up all night loading individual shots into Redalert... The color artifacts definitely aren't there on full or draft renders for me, only standard. My machine is giving me an estimated render time of 59 hours for 2/3rds of a days shooting - simply not a viable workflow.

Except for the noise, the standard renders look nice - sharper than the full renders... It's a big shame that I cannot rely on them.
I'll shoot more and see how it goes. I wonder if it's a build 15 thing. I'll try Redcine build 82 as well.
On a brighter note, I've been rendering tonight with airport turned off and there are no frozen-frame quicktimes....??? here's hoping,


Ibloom, are you saying you can write something for batch- transcoding in RedAlert?
 
markp said:
Sorry Ibloom, I'm sure they're not mutually exclusive. I just mean that being one shouldn't be a pre-requisite for being another...
Click to expand...

Think about redcine / redalert as the lab.
Its like processing your own negatives, only less dangerous - thats why so many people do it.

regarding your mistake i sadly am no big help, i never have ssen anything like it in red footage.
 
laguun said:
Think about redcine / redalert as the lab.
Its like processing your own negatives, only less dangerous - thats why so many people do it.

regarding your mistake i sadly am no big help, i never have ssen anything like it in red footage.
Click to expand...

Well the lab certainly f^%ed the transfer in this case.
BUT HOLY JESUS AFTER DAYS AND DAYS...
I just tried taking saturation down to 0.7 or 0.8 and it works!!!!!!!!!!!!!!
No more artifacts.
I tried 0.9 and there was still still a few blue artifacts in green areas, and white dots in bright red areas.
Tried saturation at 1 again and the problem returns.
I had stopped all color adjustment as part of eliminating possible causes for my strange phenomenon. Hence the time it took to find a workaround.
I only kept one R3D on my system - I'll get some more back from the editor and see if it works for all of them.
If the slight desaturation and turning off airport solves all my Redcine woes I'll be a very very happy guy. Yee ha.

Can someone at Red please acknowledge this thread and do something about this in an update? Just asking...
 
BTW i noticed in the release notes for (windows - not sure about mac) Build 90
of Redcine that an issue of white dots appearing had been fixed.:blink:
 
ibloom said:
I have something, but it was very specific for one client. I have not written the generic yet.

Ian
Click to expand...

Ibloom, everything is OK in my world now.
Reducing saturation took care of the blue, magenta, and white artifacts in Standard Renders (I have to check a few more R3Ds that had less saturation than the big problem ones - but still had white specs appearing in the shadows)
Turning off airport took care of the frozen frame issue, it seems. I've rendered overnight until the hard drive was full, twice now.
I'm back in love.
Cheers.
 
my laptop computer doesn't have Redcine .. so i'm guessing where this setting is ...
make sure under project settings (i think) that you are not running 709 twice .. you should see " camera RGB " and gamma at "709" ... not "709 "& gamma at "709" ...

also NOTE: that you do not see others here posting images like your's which tends to tell me this is more specific to your set up ? which could be several things ?? i know on my system i thought Redcine was the problem and it ended up being a graphic card issue not redcine ...
 
You must log in or register to reply here.
Back
Top