Welcome to our community

Be a part of something great, join today!

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

very strange compression artifacts?

Joe you have the same issue? Did not know you own a RED...

I don't, the company I work for does. We experienced this a lot with high contrast scenes with lots of fine detail. The irony is that the compression mess doesn't necessarily show up in the high detail, rather it just shows up in random places. But yes this is codec error stuff. We're on build 16 right now, not the most current one, but the one right before the most current one and that one seems to have killed off most of the codec error stuff we were experiencing. I believe when RED releases the "Release Build 16" most of these problems will be gone. In the meantime, it's not fun....belive me I know.
 
I've had various similar errors on Build 15. So far none on 16.
 
It looks like the split compression issue:

http://www.reduser.net/forum/showthread.php?t=4450

It is much more noticeable on images like this where the top and bottom half have a big difference in detail.

I noticed that starting in build 16 3.2.1 the split is left-right instead of top-bottom.
 
Beta Build 16 v3.2.4 - Available on RED.com/support (password-protected download).

Changes since RED-ONE Beta Build 16 v3.2.1 firmware:
* Additional codec optimization
* Boot up logo relocated to bottom of screen
* Time Code output enabled on the LEMO 5 pin timecode connector

Maybe it's better in 3.2.4?
 
Hey Obin,

Is this from a ful debayer? Does it change in the Redcine window when you switch between half and full debayer?

Cheers mate,
S
 
Hey Obin,

Is this from a ful debayer? Does it change in the Redcine window when you switch between half and full debayer?

Cheers mate,
S

I asked that very same question a few posts ago, but no one has responded, yet.

Like I said. I have encountered this error many times, and it was always due to an unsuccessful 1/2 res debayer.

Switching to full res solves the problem for me 100% of the time.

If you have, indeed, done a full res debayer and still see this problem, I'd love to hear about it.

regards,

jt
 
Try Build 16. There are a lot of improvements, including this issue... full res is also helpful.

Jim
 
Back
Top