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

RELEASED: Beta Build 20 Firmware (v20.1.2)

Mark Crabtree said:
I just updated to the 20.1.2 beta. Someone recently posted no iData in this build but perhaps it just needs another boot. After back shading I put on a Canon lens and had no iData. But, now, after another reboot, all my lenses are showing iData. I'll do more testing tomorrow, but so far it works with all my lenses. Also I want to thank the whole Red team for all they have done to make this the best build ever and especially for fixing the audio codec playback error. It was such a delight today being able to show my client the takes without seeing green clips and codec errors over and over.
Click to expand...

That's great news! Really hope RED will do everything possible to make Birger/i data integration solid and approved. It is a major deal for some of us.
 
Stuart English said:
Either "optical" stops in the sense of lens aperture, or "electronic" stops in the sense of shutter speed.

But not "electrical stops" in the sense of monitor path IRE values.


That seems to have been a confusion for some people.

As we are representing a higher dynamic range image (what's in front of lens, and / or recorded to the .R3D file) by a lower one (what's displayable by the LCD / HD-SDI monitor) you have to be careful describing the characteristics of the former image by the latter one.
Click to expand...

Ok. thanks.
So im curious. How does one activate the Sensor RAW meter and histograms? What camera menu. (sorry, still learning them!)
 
I upgraded a camera to build 20.1.2 and have noticed an odd problem (not on my camera, on someone else's I'm shooting with on a movie):

The BACK LCD panel intermittently won't show any info on boot with build 20.1.2 and stays blank the whole time until I reboot the camera. then it usually comes on with no further issue.

Anyone else seen this with their cameras?

One note is that we are using the Birger mount, but this worked fine with build 20.0.2 so it's not my first guess as culprit, but you never know.... haven't had a chance to test PL mount yet on same camera as we're shooting until end of Sunday with Canon EF lenses.

One other thing I noticed on this client's camera, on taking the PL mount off to put on the Birger mount.... the /i pins were installed, BUT the pin connector was disconnected inside the mount itself!! Is Red shipping cameras this way or did Seika DI do this locally after trying to service the client's camera? The client hasn't ever touched the mount so they haven't done it....

Thanks,

Paul
 
Sensor RAW meter...

Sensor RAW meter...

Eric Ulbrich said:
Ok. thanks.
So im curious. How does one activate the Sensor RAW meter and histograms? What camera menu. (sorry, still learning them!)
Click to expand...

Sensor RAW meter is always active - its the vertical bar to the right of the histogram.....
 
Build 20

Build 20

Possibly, but there is always an internal check list to go through before we take that step.

But let me say this, Build 20 V 20.1.2 is our most reliable build. I'd certainly use it...
 
Mark Crabtree said:
I just updated to the 20.1.2 beta. Someone recently posted no iData in this build but perhaps it just needs another boot. After back shading I put on a Canon lens and had no iData.
Click to expand...

With the Birger mount to get the lens data after updating to build 20.1.2 toggle the S4i menu and then press exit. Thereafter the lens data will then appear on the screen in a few seconds.

While using the camera, if the mount sends incorrect lens data to the camera, then the lens data won't appear until one reboots. I think Stuart said somewhere this is a new feature of the build.

So far build 20.1.2 has been the most stable version with the Birger mount inmy camera. Only once the lens data disapperaed and had to reboot. Otherwise everything and all the time, including syncing the Impero, has worked out without any issues.
 
Paul Leeming said:
One other thing I noticed on this client's camera, on taking the PL mount off to put on the Birger mount.... the /i pins were installed, BUT the pin connector was disconnected inside the mount itself!! Is Red shipping cameras this way or did Seika DI do this locally after trying to service the client's camera? The client hasn't ever touched the mount so they haven't done it....

Thanks,

Paul
Click to expand...

Hello Paul,

I have just got back my Red from the upgrade few days ago, and the ipins were installed and the pin connector was connected.

Ivan C.
 
20.1.2 was solid on a shoot I did with it last night. To my eyes there has been some significant improvement in the image quality. Footage that I thought for sure would have some noise, didn't. Blue channel seems the best it's ever been.

Let's keep in mind that although Build 17 has a release build and that certainly holds a lot of weight in terms of comfort levels on set, it also has some bugs that have been addressed with 20. It seems pretty stable. I'll put it through some more rigorous testing over the next few days but 20.1.2 seems like a good one so far.
 
muffinny said:
Hello Paul,

I have just got back my Red from the upgrade few days ago, and the ipins were installed and the pin connector was connected.

Ivan C.
Click to expand...
Thanks Ivan, ours did too, that's why I was curious to see if Red had missed one by accident or whether it was done locally by the company who has been selling Reds directly to local buyers here with service contracts etc. and who is now the official Red Service Center here.

Anyone from Red able to weigh in on this?

Cheers,

Paul
 
I'm still finding a stop difference between the green 18% grey and my spot meter. I can believe that my meter might be off by 1/10-1/4 of a stop, but not that much. I just checked it against other meters and the biggest difference was 1/10 of a stop. Has everybody been getting corresponding readings with the new false color and their spot meters?
 
As I understood the latest false color indication has very many different shades of grey between for example pink (+1) and yellow (+2)?

I thought that's rather confusing as opposed to the former version where every step had a color. I think that somehow it would be better to have maybe different saturations of color or any other seperation than using grey between the indicators. Does anyone else feel this way or am I just too used to the old version?
 
False Colors

False Colors

The majority of responses that we have had have been of the opposite opinion, so that's the way we'll leave it....
 
This reply belongs here I guess:

Carl Dieker said:
I have recently upgraded from built 17 to the latest 20 beta built. But I can't get magnifying mode to work while recording in 2k 16:9 time base 25fps, varispeed 100fps. With built 17 this used to work smoothly. Otherwise, it looks spectacular.
Click to expand...


Looking forward to the release build.
 
Paul Leeming said:
The BACK LCD panel intermittently won't show any info on boot with build 20.1.2 and stays blank the whole time until I reboot the camera. then it usually comes on with no further issue.

Anyone else seen this with their cameras?

Paul
Click to expand...

Hi Paul,

I had the same problem last week, with the back panel staying blank.

But I am still on Build 17.

As you suggest, a reboot seemed to solve it.
 
I saw today something I couldn't explain.

Two red ones both updated to the latest beta build v20.1.2, properly color balanced, matched settings, etc. yet displaying marked differences in the monitors colors in redspace. To make it more confusing there was an accompanying difference in the rgb hist with a noticeable increase in exposure in the red channel that matched the monitors warmer tinge. Both in raw and rec709 colors and hist matched nicely. Most importantly the raw files matched nicely if defaults were restored via RA and confirmed after looking at the files on a scratch system. All of the obvious (at least to me) problem solving methods were tried ie. reinstall build, black shading, switching lenses and monitors, restoring defaults, etc.

Would anyone care to confirm if this is also the case between other cameras? Not even sure if this is related to the latest build as I did not compare the cameras redspace with build 17.

-noel
 
You must log in or register to reply here.
Back
Top