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.

KLang, thanks for pointing that bug out, we'll fix that up a.s.a.p.

Ya think this will be released by Monday Am? Got a shoot comin up would luv to use it! This new build is amazing!!! You guys rock!!!
 
did a greenscreen shoot today with this build and it seems to have the raw and redcolor selection reversed when you have it mapped to a button. Not a huge deal once you realize what is going on but is anyone else having this issue?
 
Great looking build, just wondering about the choice to axe rec709. Reason being I just got off a feature as DIT and the look the DP preferred was rec709 in camera and then we set the color space to cameraRGB while keeping gamma in rec709. We'd usually up the sat but the result was a really smooth look that was harder to achieve in redcolor and redgamma. Is there any chance of this feature coming back into the picture?

Thanks
 
Well, I was so impressed with the 30 build I got ballsy and shot a commercial for the SC Aquarium last Friday. We had a second camera available so we weren't too worried. Both my AC and I couldn't believe the difference in the camera. I felt like I had a new camera in my hands. In the past, I had shot quite a bit of film and I have always thought that the RED was nice but it never blew me away, build 30 blew me away. I've never seen anything close to an improvement like this. My hat is off to you guys. I look forward to the future.
 
Bugs

Bugs

did a greenscreen shoot today with this build and it seems to have the raw and redcolor selection reversed when you have it mapped to a button. Not a huge deal once you realize what is going on but is anyone else having this issue?

That User Key bug is fixed In the very latest Beta version I believe Shane.
 
several small look bugs

several small look bugs

Noticed today with latest build (30.4.1) on an MX camera :

- create a new look in camera (like just dialing down the saturation for example)
- after playing with that look go back to VIDEO/LOOK submenu and choose 'CLEAR'
- you get the messages that all values are cleared, if you check in the menu they are back to their original values but the previous look is still applied to the image.

You need to go into any parameter and just change the value then it jumps and applies the 'clear look' to the image.

Also on the MX camera the 'clear look' will now reset ISO to 320 ISO as if it was an M camera instead of default 800...

-----

might be related (or not) to the other bug reported previously where REDCINE-X looks sent to camera have the correct value for curve but the curve itself is not activated by default... see here :

http://www.reduser.net/forum/showpost.php?p=562966&postcount=1
 
might be related (or not) to the other bug reported previously where REDCINE-X looks sent to camera have the correct value for curve but the curve itself is not activated by default... see here :

http://www.reduser.net/forum/showpost.php?p=562966&postcount=1

Yeah, we experienced this too, but the good news is it transcoded just fine with our Red Rocket. I'm pretty sure its all related to the piece of shit that
is Quicktime. I mean seriously. it sucks balls, to put it lightly.

Red will take QT out of RX and the performance will be fine. But we all need to write iphone.com I mean Apple and put a bee in their bonnet about how PIGGY QT is on memory and all other resources. its shite
 
Can we process M sensor B30 footage with RedRushes???

I know MX footage is limited only to RedCine right now.

Would like to upgrade, but need to clarify this matter asap.

thanks
 
B30 RED 300mm White Balance

B30 RED 300mm White Balance

This is a weird one. Chroma DuMonde. Lit with Diva 400 5500K. Put up RED 300mm, frame grey scale only - hit white balance. 13400 kelvin with green tint. Pan off chart, WB, sort of normal. Pan back to grey scale, 13400 with green tint. Put up UltraPrime 135mm frame grey scale only, hit white balance - 5900 kelvin. Switch again. Repeatable. Thought I should mention it. No big deal I guess. Lens coating?

Robert Torrance
 
This is a weird one. Chroma DuMonde. Lit with Diva 400 5500K. Put up RED 300mm, frame grey scale only - hit white balance. 13400 kelvin with green tint. Pan off chart, WB, sort of normal. Pan back to grey scale, 13400 with green tint. Put up UltraPrime 135mm frame grey scale only, hit white balance - 5900 kelvin. Switch again. Repeatable. Thought I should mention it. No big deal I guess. Lens coating?

Robert Torrance

That is interesting.
 
Stuart I didn't followed the hole thread. My question goes to the false color never clips in V mode thing we see at our MX cameras @ B30. Will this be solved in the future ?

thx
rainer
 
Black ped high in B30 ?

Black ped high in B30 ?

I've been testing B30.5.0 on M sensor and I've noticed on waveform that complete black(lens capped/zero light) is not 0 IRE. Viewing either Raw or REDcolor. But it is almost 3% IRE . My other R1 with B21.4.1 shows its 0%. So I imported both cameras' clips into FCP to look at the waveform there, and while the B30 camera still shows to be almost 3%, the other ,B21, is at about 2%. Of course this can be lowered in camera with Shadow adjustment. A slight decrease to 0.2 brings black to zero.
Red team, or anyone, know why there is a difference between the builds, and what does it mean? I'm trying to figure if this has to do anything with noise floor abilities? Incidentally,for comparison, Black Field generator in camera represents true 0 IRE on waveform.
Sorry if this has been posted before, I haven't found it.
thanks
 
I've been testing B30.5.0 on M sensor and I've noticed on waveform that complete black(lens capped/zero light) is not 0 IRE. Viewing either Raw or REDcolor. But it is almost 3% IRE . My other R1 with B21.4.1 shows its 0%. So I imported both cameras' clips into FCP to look at the waveform there, and while the B30 camera still shows to be almost 3%, the other ,B21, is at about 2%. Of course this can be lowered in camera with Shadow adjustment. A slight decrease to 0.2 brings black to zero.
Red team, or anyone, know why there is a difference between the builds, and what does it mean? I'm trying to figure if this has to do anything with noise floor abilities? Incidentally,for comparison, Black Field generator in camera represents true 0 IRE on waveform.
Sorry if this has been posted before, I haven't found it.
thanks

this is a really stupid question, but did you properly black shade it after updating to 30.5?
 
I experienced a peculiar case yesterday when shooting on latest build 30 version. In the morning and afternoon in couple of shots the exposure difference between the light meter and Histogram is almost having 2 1/2 stops difference. This happened one time in morning first shot and afternoon in the middle of shoot. After these shots whatever we metered were set as our exposure and histogram perfectly matched.

Any idea how and why it happens. The above build 30 was installed in Non-MX sensor Red One.

The 2 1/2 stops exposure difference is under and not over. So we need to boost light and open the f-stop.
 
I was trying to update my One with 30.5 and there's a message saying that are no new update available?
What's wrong?
I tried 3 different cards....

deanan?


thanks,
 
False Colors in Build 30

False Colors in Build 30

Stuart I didn't followed the hole thread. My question goes to the false color never clips in V mode thing we see at our MX cameras @ B30.

This begs the question, why do you want the Video Level to clip Rainer?
 
where do I download the latest build 21

where do I download the latest build 21

help please
where do I download the latest build 21

I'm having trouble with 30
 
Back
Top