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

Will Build 16 help this.

K

Karl H

Well-known member
Joined
Jan 5, 2007
Messages
612
Reaction score
0
Points
0
I've found Redcode to be very good on most scenes, but the following example is a heavily detailed scene where the wavelet compression appears to go muddy.

It was shot with either build 13 or 14 (cant remember), redcode 28. I have not had a chance to shoot Redcode 36 yet as I'm waiting for my Birger mount. It was exported in Redcine as a Tiff snapshot with a minor curve, then saved to a jpg in photoshop. The lack of detail here is evident in the tiff, this is not due to jpg re-compression.

Here's a 1280 scaled version, followed by 2 images at 100 percent crop of the 4K image. Finally, a link to the 4k jpg should anyone want to see it. The main tree barks appear to have no detail in places, while the tree branches down the centre of the path also have appeared to go mushy.

Will Redcode 36, or the rewrite of Redcode in Build 16, help this issue?

1280.jpg


100crop.jpg


100cropb.jpg


right click and save link for 4K jpg

http://darklineonline.co.uk/red/4K.jpg
 
hey dopey, he probably doesnt have PL glass to use so he's waiting on his mount so he can use the EOS lenses he does have.
 
yeh sorry, i just meant the simple answer might be 'shoot redcode 36' but I cant shoot anything else till I get my mount.
 
just as an added question for the red team. Is this why epic is going up to 100M/sec? Is a scene like this just too much for a 28/36 data rate?
 
RED RAW Uncompressed port is what we need as serious " POST " Production houses NOT INDIES with budget Limitation.

I am ready to pay for USD 10K USD for this option, and what about the other Serious RED Post production owners ?

DALSA outputs RAW uncompressed files to ....any Digital field recorder like S.X and CXdxX or eve some japanese black boxes. Next Jame sBonfd movie is going to use Dalsa + uncompressed digital files on-set.

Mr. David Stump will have more details to share here with you guy soon.

I did uncompressed HD back in 6 years ago, and I am not kidding !!!

Stewart Chong
Founder
REDHKSC

WOW Holdings
CEO






darkline said:
I've found Redcode to be very good on most scenes, but the following example is a heavily detailed scene where the wavelet compression appears to go muddy.

It was shot with either build 13 or 14 (cant remember), redcode 28. I have not had a chance to shoot Redcode 36 yet as I'm waiting for my Birger mount. It was exported in Redcine as a Tiff snapshot with a minor curve, then saved to a jpg in photoshop. The lack of detail here is evident in the tiff, this is not due to jpg re-compression.

Here's a 1280 scaled version, followed by 2 images at 100 percent crop of the 4K image. Finally, a link to the 4k jpg should anyone want to see it. The main tree barks appear to have no detail in places, while the tree branches down the centre of the path also have appeared to go mushy.

Will Redcode 36, or the rewrite of Redcode in Build 16, help this issue?

1280.jpg


100crop.jpg


100cropb.jpg


right click and save link for 4K jpg

http://darklineonline.co.uk/red/4K.jpg
Click to expand...
 
MB/s on EPIC

MB/s on EPIC

darkline said:
just as an added question for the red team. Is this why epic is going up to 100M/sec? Is a scene like this just too much for a 28/36 data rate?
Click to expand...

No, think higher max resolution x higher max frame rate ....
 
I've shot quite a few similar scenes under build 15 redcode 36, and never had this kind of nasties.

Emmanuel
 
Stuart English said:
No, think higher max resolution x higher max frame rate ....
Click to expand...

Is that the same for the Scarlet then? 100M/sec is necessary because of the 180fps burst rate?

Or, in other words: are you saying the new 100M/sec rate is not a RedCode 100, it's still RedCode 36, just more frames per second?
 
Correct me if I'm wrong, but it looks like the focus isn't there. Did you check back focus prior to shooting?
I'll look at the 4K image...
EDIT: I looked at your 4K .jpg image. Nothing appears sharp. Nothing. I believe I was correct in that focus was soft.
 
This has nothing to do with focus. It's a wavelet problem and i experienced it too in footage from a forest scene where there was a lot of detail from branches, leaves etc.

I spoke to Graemme about it and sent him some R3D fles to check out and he replied that they are working on it.

From what i understood though the problem wasn't fixed in build 16...

EDIT: Redcode 36 does it too

Miltos
 
Fair enough.
But wouldn't it stand to reason that if the image isn't focused sharp that the wavelet would have problems?
Look at the .jpg - there isn't anything in complete sharp focus...
 
So the issue at hand seems to occur when "over loading" of detail is presented through the camera?
You mentioned you experienced this before when you shot forest stuff - are you familiar with any other situations where this might happen?

I'm shooting in the jungle in about a week - will post results when I have them. Koa has shoot a feature here in Hawai'i, mostly in the jungle and forest. I haven't heard or seen this from him though.

Perhaps Graeme, or someone from RED, can comment?
Too much detail = poo of an image?
 
There was a Greek music video posted in the footage and field tests earlier this week. It was shot with a friend's RED ONE so we had the chance to inspect the footage together. Although most of it was shot in the same location, only a few shots presented the codec problem.

What i am trying to say is that it's difficult to pinpoint exactly what kind of vegetation produces it and under what circumstances. The only thing i could say that might help is that all the shots that had the problem were framed in a way that the upper half part of the frame had the most detail.

EDIT: Just added the following screenshots to show a similar shot with the same problem

Full frame:
2499495469_267596924f_o.jpg


and a non scaled crop:
2500323098_46ef40f6d7_o.jpg


You can clearly see the loss of detail on the tree trunk the higher you look.
 
Build 15. Redcode 36. Foliage and fur.
Same thing happening here and can be seen looking at a 4K still at 1:1. Scaled 2K and lower footage = no problem.
 
I think our backfocus is ok because other stuff we shot is sharp.. this, well, im not sure whether it looks soft because of the wavelet, or more likely we just missed focus.

We hired a lens for the day so we just shot as much as possible in many different conditions. No tests were carried out on the lenses before we shot (not that I have ever done that before anyhow). This was focused by eye on the LCD in sunlight, so not all the park shots came out perfect - but this image best illustrated the problem.

Other stuff we shot in the park, for example areas with more sky in frame did not show these blotches. However I just read Jim's post that this issue is solved in build 16, so I guess that ends this discussion :-)

thanks for the explaination Miltos.
 
You must log in or register to reply here.
Back
Top