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

16 and artifacting

RC36 doesn't help... The following was shot at RC36.

Since RedCode is a compressed format you will always be able to find scenes that have such/similar compression artifacts. RedCode's is using a little over 1 bit per sample, which is okay. Something in the range of 2-3 bits per sample may be more helpful here, but then the bitrate would increase.
 
You can record REDCODE 36 to the 8GB CF as well as to RED-DRIVE. So no quality difference, unless you try REDCODE 36 at 4K 16:9.

Then yes, RED-DRIVE has the quality advantage as CF can only support REDCODE 28 at 4K 16:9.

Only problem is with Build 15 you can run into codec errors when using the combination of Redcode 36, 4K 16x9 during complex detailed shots. I've only experienced it a couple of times, but one of those times was when panning from a tree to a valley below.

With the improvements in Build 16 on the horizon, I think we just have to accept this as a temporary inconvenience. This hasn't happened enough for me to call it a showstopper.
 
Sorry to disagree... REDCODE 36 is better than REDCODE 28 in Build 15. Shoot the same exact scene in both and you WILL see a difference. There is still an issue with REDCODE 36, but it is not as bad as 28.

I didn't say there is no difference Jim. I only said that even with RC36 you can have the same problem with scenes with a lot of trees (or any other subject with a lot of details).

But fear not, Build 16 will calm your nerves.

What i have learned so far with the RED adventure is that as long as you are in charge i have nothing to fear.
 
Back
Top