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

Build 30... the Crossover build.

Question:

On the HD-SDI output.. What lever debayer is that output? Half or full?

Thanks

Jay

It's still a RED ONE. It's not an EPIC so I would bet that the debayer does not change. 8 bit 720P. Still the best video tap in the biz.

David
 
Build 30 is great !
Now there is still something strange:
The Manual WB cursor is very much stuck on the left of the bar,
5600K used to be centered, is this an volontary improvement ?
 
Yes!!!!!!!!!!!!

Thanks for the multi-user button for focus, and the false color views!

Tim Eaton

I´ll second that!
Build 30 is fantastic! I have even more the feeling of having a new camera then with build 21. It´s "epic" now. I didn´t seriously used Redspace in the past, always RAW. With Redcolor it´s a whole new story. Love to work with it already.
Clipping and noise bar: ingenious.

Not a simple thank you...big hugs to Jim and his team!
Marc
 
Black Sun?

Black Sun?

Has anyone had the chance to test the M camera with build 30 for the black sun issue?
 
ok just loaded the new build.. I already knew about the asa 800 being the default..
(mysterium one sensor)
now.. is that really set at 800? or is that 800 really 320.. but saying 800?

Reason I ask is because my image seems to be pretty clean up to asa 1280...

and in fact.. in this lighting situation.. normally a 320 reading would be super dark.. but I am getting more image than that, which leads me to believe this is really set as 800.
but my image seems clean... weird.
 
Sword Fightin' with B30...

Sword Fightin' with B30...

Here's a quick and dirty one light edit from last night's rehearsal footage shot with a NON-MX Red running Build 30:

http://www.youtube.com/watch?v=Hc9wy43Ro4k

Production Notes:
Shot 4K 2:1, RC36 to CF w/Long-ish Zoom (primarily 85mm) at 2.8, 1/48th sec shutter. Camera was rated at 320, One light in RCX Build 104...

Every piece of the shooting puzzle was just easier w/ Build 30... Everything.
And it really does feel like we have a brand new camera in hand.
(Oh. And the calibration of in camera imaging with RCX (B104) is just HOT.)

This is an Amazing Build.

THANK YOU RED TEAM!
 
are there any independent tests out yet which rate the new sensor?

Rate the new sensor for what?

The M-X sensor has the same size pixels as the M sensor so they both have the same "native" sensitivity... a term we really don't like using because it confuses people.

Both sensors have a useful range of ISO settings... which is what does matter. The M-X sensor has a wider range of useful settings because the pixels (and sensor) are less noisy.

Since there is more highlight protection at 800 than 320, there is an obvious advantage to shooting a higher EI/ISO/ASA under most circumstances. The higher the EI/ISO/ASA, the more noise you get. So there seems to be a sweet spot... point where you get the best protection and lowest noise... for each camera. Typically that is 320 for the M sensor and 800 for the M-X sensor. That is why they default to those settings (or will with the next build).

Jim
 
OK... here it is. This build works with both Mysterium and Mysterium-X sensors in the RED ONE. Includes FLUT™™ Color Science and a ton of other goodies. Use with REDCINE-X 104 and above.
http://www.red.com/support

So can anyone confirm that this builds .R3D files will not open in old Redcine?
 
So can anyone confirm that this builds .R3D files will not open in old Redcine?

I can confirm that Build 30 footage will NOT open properly in the old REDCINE. The color science will be off and there is no FLUT support in the old REDCINE.

Jim
 
I can confirm that Build 30 footage will NOT open properly in the old REDCINE. The color science will be off and there is no FLUT™ support in the old REDCINE.

Jim

We really need the ability to transcode selective portions of shots by loading XML or EDL files into Redcine-X. I was hoping this functionality would be released with or before this kind of camera build as it's putting post-production people like myself in a bit of a bind who don't own the big ticket .R3D native systems and rely on tools like Redcine to get the best results in the pipeline.
 
I can confirm that Build 30 footage will NOT open properly in the old REDCINE. The color science will be off and there is no FLUT™ support in the old REDCINE.

Will it at least open in the old REDCine? I find the interface better to scrub through footage fast with (sorry, not crazy about RedCine-X interface with importing footage and what not). What about RedRushes for quickly creating offline files for edit? Or maybe a better question is when the next RedLine with the new ColorScience is going to come out?

Matthew
 
Too funny.... I spend all day Friday going over the meters on build 21 to get a good handle on stuff and of coarse a new build comes on Sunday!! With that said excellent work Red Team!!! You guys really keep us on our toes!!
 
I can confirm that shooting into the sun looks like you are shooting into a sun.

Shot at 7AM this morning with hoar frost and fog at -18 celsius and the footage is unbelievable. My actress is in foreground with plenty of detail and skin tone while the sun is immediately over her shoulder. Wickedly good.
 
I can confirm that shooting into the sun looks like you are shooting into a sun.

Shot at 7AM this morning with hoar frost and fog at -18 celsius and the footage is unbelievable. My actress is in foreground with plenty of detail and skin tone while the sun is immediately over her shoulder. Wickedly good.

Footage puh-lease! At least some stills. (stupid thing is, I want to see the sun and only just wondered what the girl looks like......)

:001_wub:
 
Following my WYSIWYG WORKFLOW there are examples and steps with B30 here:

R3D_01_ISO800.jpg

R1-M, B30 processed in REDCINE-X using Wave and RR, ISO 800 (default), Canon FD 85mm L f/1.2 @ wide open f/1.2, shutter 1/50.

R3D_02_ISO800.jpg

R1-M, B30 processed in REDCINE-X using Wave and RR, ISO 800 (default), Canon FD 85mm L f/1.2 @ wide open f/1.2, shutter 1/50.

R3D_03_ISO800.jpg

R1-M, B30, ISO 800 (default), Canon FD 85mm L f/1.2 @ wide open f/1.2, shutter 1/50.

R3D_04_ISO800.jpg

R3D processed with REDColor and REDLog then loaded in FCP ready for FilmEffects lookout.

R3D_05_ISO800.jpg

R3D processed with REDColor and REDLog then loaded in FCP and processed with FilmEffects as Kodak Negative Film 5245 and Kodak Print Film Stock 2383 look (LUT).

R3D_07_ISO800.jpg

To compare with the first picture above (image out from QT file rendered in FCP):
R3D processed with REDColor and REDLog then loaded in FCP and processed with FilmEffects as Kodak Negative Film 5245 and Kodak Print Film Stock 2383 look (LUT).
 
ISO 800 is for M-X. M should be ISO 320. Maybe we should start calling it EI (exposure index) instead of ASA or ISO?

Jim

Hey big fella,

Quick question, 800 iso is the new base? I think your saying.
Can we still set the iso to shoot at 250 - 320 without any picture or latitude issues.

Only reason Im asking is, that I'm trying to get rid of the amount of filters I have to now stick in front of the lens during a sunny day. I've only just got used to shooting at 320 asa in the middle of the day.

I'm a big Kodak... (was) a big Kodak 50D & 250D user and not having layers of filters on the lens made for far cleaner frames and less flare or less bounce reflection etc...

So question is, is it cool to shoot or set a forced 250, 320 asa without any quality loss to the image. Am I pushing the sensor to much?

Your thoughts.

Thanks Jim.
 
Hey big fella,

Quick question, 800 iso is the new base? I think your saying.
Can we still set the iso to shoot at 250 - 320 without any picture or latitude issues.

Only reason Im asking is, that I'm trying to get rid of the amount of filters I have to now stick in front of the lens during a sunny day. I've only just got used to shooting at 320 asa in the middle of the day.

I'm a big Kodak... (was) a big Kodak 50D & 250D user and not having layers of filters on the lens made for far cleaner frames and less flare or less bounce reflection etc...

So question is, is it cool to shoot or set a forced 250, 320 asa without any quality loss to the image. Am I pushing the sensor to much?

Your thoughts.

Thanks Jim.

You can still shoot the M-X sensor at ISO/ASA 320... you will have the same highlight protection as you do with the M sensor. But consider that the IRLP filter is so much better on the new M-X sensor, using NDs is not the issue it was with M.

Jim
 
Back
Top