Welcome to our community

Be a part of something great, join today!

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

RED ONE build 32

Haven't had a chance to test RG3/RC3 yet(just getting it installed), but what has me curious is REDLOGFILM. I didn't anticipate that this would make it to the Red One. I'm planning on running this through my on-set LUT system and see what kind of magic this allows. Feels like getting the Red One all over again. :-)

Thanks again Jarred! I know there's a lot on the plate there, so the fact you're able to support a 5 year old technology is great.
 
Thank you to all at RED for releasing Build 32 for the RED One! We are fully invested in the R1 for the time being, and the addition of the new color science is like giving us a whole new camera! I know that all of us R1 owners greatly appreciate it, and all new Epic and Scarlet owners should take notice of the way that RED supports it's older products and feel great about their decision to purchase RED.
 
Thank you.

I went Stage Two like one climbs Everest - because it was there. Red One MX is still my A-Cam in the Studio with my motion control macro rig, so it's good to get the col-science update. The Epic only comes into its own away from the studio and that's not my main work.
 
Beta version Build 32

Beta version Build 32

My greed has inspired me to write this, specially when RED has been generous to fulfil it!
I am a proud owner of RED ONE M (not MX) and would like to be that way (I am extremely happy with the results of the Original RED ONE M and wont change until I finish my project).
Just wondering if this new firmware upgrade (although in BETA) will work for the RED ONE M or this new firmware upgrade is only meant for those who have upgraded to MX.


Either ways, I am happy to live with the current build 31 firmware, but I am writing because RED is generous.

Cheers,
Kalpesh
Film is as real as reality because I react and emote the way as I would off screen. I make films because it finites the infinite within me.
 
[COLOR=#FFFFFF !important]i can confirm that everything works fine except this bug. [/COLOR]
 
In REDCine-X Pro (Build 16) I'm attempting to export a look w/ REDColor3 + REDGamma3 to RED M-X, but I'm getting an error message in RCX-Pro:

"Error Exporting to Camera: Color Space must be REDcolor and Gamma Space must be REDgamma to export look to camera."

Is this simply a matter of RCX-Pro needing a corresponding update for Build 32?

Thanks!

Best,
Adam
 
Adam Bricker said:
In REDCine-X Pro (Build 16) I'm attempting to export a look w/ REDColor3 + REDGamma3 to RED M-X, but I'm getting an error message in RCX-Pro:

"Error Exporting to Camera: Color Space must be REDcolor and Gamma Space must be REDgamma to export look to camera."

Is this simply a matter of RCX-Pro needing a corresponding update for Build 32?
Click to expand...

Current REDCINE-X "Save Current Look for RED ONE" is intended for RED ONE with firmware prior to build 32. One of the new functions in build 32 is the ability to load a look from an RMD file, same as Epic/Scarlet. So try using the Epic/Scarlet look export.
 
I saved the look in RCX for EPIC/Scarlet. This saved an RMD Files to the SD Card. The RED M-X (on build 32) recognized the look (it had previously not recognized the RLK files). However, when selected to import, we received an error message:

"PROFILE IMPORT FAILED. Verify that the SD card is seated properly and try again."

We've tried multiple SD cards to no avail.
 
if i only have a ssd module , on my red mx. can ii use a sd card or a ssd to transfer build 32 over?
 
Yes, you can.
 
Hi there… Just wanted to get some feedback from people who are actually using the Beta build on M Sensor (non-X). Any inconveniences despite the one bug mentioned (jump from RC3 to RC1), any things one needs to know after stepping up? I don't need .RMD/Look functionality in camera so any problems regarding that part are not an issue).

Still lurking around on an older - but stable running - build (30.6.12) on our original RED One and we have a shoot in about 2 weeks (it's our Backup/Rental/2nd-Cam Body when the EPIC is otherwise blocked or not right for the job). Since I have a few days for testing now I can either go latest Release or Beta - usually I'm feeling better with Release builds but on the other hand side I'd love to see the results of the newer color science with the original M Sensor… Shoot will be outdoors most of the time (no Studio lighting). I'm always having all the builds with me to play safe - but why not just ask.

Any recommendations or user-reports are very welcome - Thank you! :)
 
Peter Stelzhammer said:
Hi there… Just wanted to get some feedback from people who are actually using the Beta build on M Sensor (non-X). Any inconveniences despite the one bug mentioned (jump from RC3 to RC1), any things one needs to know after stepping up? I don't need .RMD/Look functionality in camera so any problems regarding that part are not an issue).

Still lurking around on an older - but stable running - build (30.6.12) on our original RED One and we have a shoot in about 2 weeks (it's our Backup/Rental/2nd-Cam Body when the EPIC is otherwise blocked or not right for the job). Since I have a few days for testing now I can either go latest Release or Beta - usually I'm feeling better with Release builds but on the other hand side I'd love to see the results of the newer color science with the original M Sensor… Shoot will be outdoors most of the time (no Studio lighting). I'm always having all the builds with me to play safe - but why not just ask.

Any recommendations or user-reports are very welcome - Thank you! :)
Click to expand...

Hi Peter!

I haven't find any bug in the build (except for the RC3 going to RC1 after RAW viewing), but I've been working EPIC these days, primarily. What I can say is that, with the original M sensor, I've found that RedColor (1) gives a more pleasant image than RedColor3, which I guess has been designed with the M-X sensor in mind. In fact I find that RedColor (1) in the M sensor is closer to the look of RedColor3 in the EPIC-X than if you use RedColor3 in the original M sensor.

As you know, I'm talking subjective perceptions here, but I just thought these can help you decide. Anyway, maybe you prefer the look of RedColor3 in the original M sensor. The only way to know that for sure is to test it.

Hope this helps!
 
Jordi Figueras said:
Hi Peter!

What I can say is that, with the original M sensor, I've found that RedColor (1) gives a more pleasant image than RedColor3, which I guess has been designed with the M-X sensor in mind. In fact I find that RedColor (1) in the M sensor is closer to the look of RedColor3 in the EPIC-X than if you use RedColor3 in the original M sensor.

!
Click to expand...
I had the same experience! I thought first there must be something wrong with my eyes, then I came to the same conclusion: it is logical that M looks best with r1/c1, as these were designed for the M sensor
 
will be this bug removed, or is over with any new firmware release?
 
You must log in or register to reply here.
Back
Top