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 20 (Beta) bug tracker

But I like the lower ISO range for the lower noise. Thought it would be nice to have zebra in that range too, otherwise it's a bit useless i think. And the manual doesn't say anything about ISO 100–200 beeing similar to underexposing!?

Page 12:

The sequence of 12-bit RAW images received from the sensor is compressed using proprietary wavelet based REDCODE™ RAW compression. The RAW data recorded is independent of the RGB signal monitored from the monitoring path. ISO, white balance or other RGB color space adjustments made to the monitoring path are not burned into the recorded 12-bit RAW data.

(snip)

The camera’s monitoring path converts 12-bit RAW sensor data white balanced 10-bit 1280 x 720 pixel RGB 4:4:4 video. This signal may be modified using ISO, white balance or other RGB color space adjustments and provides monitor feeds for the RED-EVF, RED-LCD, Preview HD-
SDI and HDMI outputs.

In short (and I can't believe I'm still telling people this) the ISO setting on the monitors is for convenience only; do not use it and think that it will fundamentally change what you are recording. That way leads to pain.

The camera is 320 ISO, treat it as such and you'll go far. Expose to the right while it's on this setting for best results. If you must meter, meter for 250 or 200 but leave the damn camera setting alone.
 
14 in a row boot freezes! So embarrassing(of course I used it on a commercial production, used it on two other shoots prior). Did all the usual tricks. Was a warmer day in LA but the camera had not indicated that it was overheating when we powered down to change batteries. It has never happened as many times in a row on Build 20 since or before so heat is all I can think of but still....90 degree heat with fans on full boar during an MOS project.
 
I said this earlier in another thread, but it's worth repeating.

Build 20, is after all in BETA. So you should use accordingly. You need to test prior to shooting for clients, check everything, test under the conditions you will be shooting.

So far we know there are bugs in Build 20, we've known from the first week of it released, so please spare yourself grief, and only use 20 in situations where it's works properly, or downgrade to Build 17.

If you rent a camera from any pro house you get Build 17, not 20, not until it's officially released.

Beta is for testing, trying new things, finding out what it does, and does not do, and reporting to the mothership so they can make corrections and improvements.

I've been beta testing software for years with digital still, and on closely watched high dollar gigs, I'd never use the beta, too risky, I use what I know works, and wait.

So don't forget "This is a TEST".
 
I said this earlier in another thread, but it's worth repeating.

Build 20, is after all in BETA. So you should use accordingly. You need to test prior to shooting for clients, check everything, test under the conditions you will be shooting.

So far we know there are bugs in Build 20, we've known from the first week of it released, so please spare yourself grief, and only use 20 in situations where it's works properly, or downgrade to Build 17.

If you rent a camera from any pro house you get Build 17, not 20, not until it's officially released.

Beta is for testing, trying new things, finding out what it does, and does not do, and reporting to the mothership so they can make corrections and improvements.

I've been beta testing software for years with digital still, and on closely watched high dollar gigs, I'd never use the beta, too risky, I use what I know works, and wait.

So don't forget "This is a TEST".

I know this. However, most of the time I'm willing to accept that risk especially on landmark builds regarding image quality. I still don't regret doing it either. Also have back up builds just in case. Although these boot hangs have been happening for awhile.
 
Lots of random re-boots and shut-downs here on B20, great image, but probably not stable enough for use on a job.

Cheers,

Paul
 
Also experienced some problems in booting up and had couple random shutdowns until realized the problem is in the cable between the battery plate and the camera. Does not necessarily apply to your case, but once started to use a new battery plate all symptoms disappeared and have stayed away although I'm using build 20.
 
14 in a row boot freezes! So embarrassing(of course I used it on a commercial production, used it on two other shoots prior). Did all the usual tricks. Was a warmer day in LA but the camera had not indicated that it was overheating when we powered down to change batteries. It has never happened as many times in a row on Build 20 since or before so heat is all I can think of but still....90 degree heat with fans on full boar during an MOS project.

On my first attempt with B20, the fan stopped function normal, but this "fixed itself" when I re-installed B20. The fan problem appeared after a reboot and a flickering LCD screen.

I would cool the camera, and re-flash with B20, or Stable 17 at that shoot day. A re-flash and re-black calibrate just take 10 min, so I'm always carrying flash cards with several builds, just in case.
 
On my first attempt with B20, the fan stopped function normal, but this "fixed itself" when I re-installed B20. The fan problem appeared after a reboot and a flickering LCD screen.

I would cool the camera, and re-flash with B20, or Stable 17 at that shoot day. A re-flash and re-black calibrate just take 10 min, so I'm always carrying flash cards with several builds, just in case.

Indeed Indeed. Carry all this. Try different cables, cooling, and have alternate builds present. I'm also aware of the risks taken by using a beta build but I'm a sucker for image quality. However, I feel the "bugs" that should be present at this point in the 20th build shouldn't be the biggest possible bug of all.....does the camera turn on and off? Loving the new image.
 
I was just out on a shoot and had the record button stop responding. The camera had been on for about 30 minutes and the room was probably around 80 - 85 degrees, but the fans were on full (shooting MOS). I went to shoot a take, and it would not record. (It had been working just fine all morning.) I powered down the camera, and powered it back up, and everything worked just fine for the rest of the day - weird ...
 
So on the newest Build 20 (20.0.2) I saw yesterday, when I unplug the LCD and plug it in again I see only white flickering. LCD doesnt come up working. EVF still has normal picture. When I also unplug the EVF and plug it in again, camera self reboots. After reboot everything ok.
 
So on the newest Build 20 (20.0.2) I saw yesterday, when I unplug the LCD and plug it in again I see only white flickering. LCD doesnt come up working. EVF still has normal picture. When I also unplug the EVF and plug it in again, camera self reboots. After reboot everything ok.

Why do you have to unplug/replug?

(I've had to do this for the EVF a couple times, never rebooted the camera though... wasn't B20 either...)
 
B20 stability

B20 stability

Lots of random re-boots and shut-downs here on B20, great image, but probably not stable enough for use on a job.

Have you tried the Build 20, Version 2.0.2 that's available from www.red.com/support ? It specifically addresses these issues.
 
Just install build 20.02 and got an error message while playing back a clip with audio embed (on the raid red). AUDIO PLAYBACK SATA TRANS FAULT. Then the drive unmount and remount. The camera didn't reboot wich is good though. It's the first time I get that message. What does it mean? Bad sata cable or bad sata port? unfortunately, I don't have a second sata drive cable for testing. Any inside would be appreciated
EDIT Hé Hé PROBLEM SOLVED WITH BUILD 20.1.3

Thanks
 
Hard Drives seem to randomly unmount during recording on the Build 20.02.
 
build 20 bug

build 20 bug

Shooting 100 FPS @ 2k to red drive,every take that is longer that 8 minutes has no image for about 4 seconds around the 8 to 10 minute mark making the proxie unusable it is ok in the R3D though,never had this problem on 17.
 
Just install build 20.02 and got an error message while playing back a clip with audio embed (on the raid red). AUDIO PLAYBACK SATA TRANS FAULT. Then the drive unmount and remount. The camera didn't reboot wich is good though. It's the first time I get that message. What does it mean? Bad sata cable or bad sata port? unfortunately, I don't have a second sata drive cable for testing. Any inside would be appreciated
Thanks


I am running 20.1.2 and came across a nasty one today that I'm trying to confirm is a bug. I got a similar "SATA TRANS ERROR" but this was while trying to record to a RED drive. This was during the thick of it and I couldn't reboot to see if that would fix it. Ended up switching to a CF card quickly. I'm trying to track this down to see if it is the drive or the build since 20.1.2 is only a few days old.

This drive has some issues, among them being problematic to mount to a computer, and a FW800 port that doesn't work. But all reports I've received about the drive says that there are no problems when trying to record to it. Makes me nervous about using that drive ever again if I get SATA TRANS ERROR and corrupted files.
 
Back
Top