Welcome to our community

Be a part of something great, join today!

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

Release Camera Build 3.2.16

I notice that there's an 'SVN Version' for the camera - which I'm guessing means that there are a number of different modifications to the camera that have happened over time - and this might explain why 'identical' cameras act differently with the same firmware.

This is quite normal with computer motherboards (you often see tiny patches on the bottoms), and the Scarlet/Epic are basically giant multi-layer motherboards fit into a very tiny cube.

Would it be possible to check the SVN Version of our cameras with RED support, and they could tell us - "you're probably going to want to send that in for some modifications"?

It would be nice to know in advance, rather than encountering a problem or strange unexplained behavior?
 
Les C. said:
I notice that there's an 'SVN Version' for the camera - which I'm guessing means that there are a number of different modifications to the camera that have happened over time - and this might explain why 'identical' cameras act differently with the same firmware.

This is quite normal with computer motherboards (you often see tiny patches on the bottoms), and the Scarlet/Epic are basically giant multi-layer motherboards fit into a very tiny cube.

Would it be possible to check the SVN Version of our cameras with RED support, and they could tell us - "you're probably going to want to send that in for some modifications"?

It would be nice to know in advance, rather than encountering a problem or strange unexplained behavior?
Click to expand...

The SVN revision is not for the camera, but rather for the firmware.
 
Trent Lillehaugen said:
Re-installing the firmware will not fix the problem you are having. Unfortunately there is a bug that is causing some people to experience a problem with the LCD monitor at start up. If this is the case (and you don't like any of the work-arounds), please roll back to 3.0.x until we have a fix.
Click to expand...


Thank you, Trent,
I got an email from Red saying that indeed the white or split screen at startup is a software bug; I can live with simply disconnecting & reconnecting the LCD, but the other bugs are far more worrisome. The LCD suddenly going black & requiring a reboot is merely annoying, but having to go back to factory defaults to clear the stuck ISO is a major problem in the field.

I will send you some other thoughts via PM.

Thank you again for your help.

Best regards,

Leo
 
My camera freezes most of the time i turn on HDRx, then i have to reboot. It happens 3 out of 4 times, so probably a bug, it also loses sync and gelock in hdr mode.
Another bug it custom frame guide aspect ratios. in 3K HD i tried making a 85% 1.78 frame guide, but is isn't 16:9 then. To get 16:9 i had to fill in 2.09. Also something to look at

for the rest, works nice!
 
RED Team - I got all excited to imagine that I could program the Slate functions into a couple of slots on my REDmote but was disappointed not to see them on the list in the set-up mode. Any chance you will add the ability to see (and change, if necessary) the Scene and Take info from the REDmote??

THANKS!!
 
On this build, when you go to playback my entire camera freezes and I need to reboot, I lost all audio, when I change frame rates my lcd freezes and I need to reboot, battery levels always read 0% regardless of batt charge, I think that's it.

I'm going to roll back to an older build until they get this fixed.
 
Leo, Indeed, you are not alone. I have the same problem. My Epic boots with a split screen or solid white screen most of the time. Since I use it most often in an underwater housing, unplugging the monitor is inconvenient. I've installed 3.2 twice and am now back to 3.0. Howard Hall
 
Last edited:
nicolas de chateau thierry said:
"Here are the next things I'd like to see :
- Simultaneous HDMI and HD-SDI outputs
- Audio playback
- Look-around
- Long exposures in timelapse mode (and a true timelapse mode with more options)
- A calibration mode that takes less than 20 minutes ;-)
- Better power management if that's possible, especially when using just a Redvolt in the side handle...
Click to expand...

+1 !!
 
Howard Hall said:
Leo, Indeed, you are not alone. I have the same problem. My Epic boots with a split screen or solid white screen most of the time. Since I use it most often in an underwater housing, unplugging the monitor is inconvenient. I've installed 3.2 twice and am now back to 3.0. Howard Hall
Click to expand...

Yes same here Howard two cameras booting up with white screen on the Deep Atom. I might go back a build myself.
 
Yellow dot instead of recording

Yellow dot instead of recording

I upgraded to 3.2.6 yesterday, did some tests and then went out on an observational doco shoot. I love the new high frame rates which I put to good use. Other little touches are welcome too, like the on screen message that pops up when you press a button, letting you know what you've hit. It's good when you accidentally press something. There was a glitch though. About every 5th time I hit record the recording light just went yellow, the menus froze and I couldn't record. Hard rebooting fixed it but I missed a few things in the meantime each time it happened (about a dozen times in 2 hours). Anyone else having this problem on Scarlet. Even with this glitch I'm reluctant to roll back the firmware because the other features are so good. For those who haven't, I don't recommend upgrading quite yet unless you can get around the stability issues.
 
Hah maybe its an Ozzie problem !!...like our toilets flowing in reverse to the northern hemisphere.

Anyway after some success with 3.2.16 I had a few days with no problems then got the white screen, the Iso freeze etc so I have rolled back to 3.2.07 The thing I like most about 3.2.16 was the snappy side handle response. So here in 3.07 land I sit eagerly awaiting 3.2.17 version!

P.S Hopefully Red allows for gravitational differences between the Northern hemisphere & our Southern hemisphere when creating software updates.
 
Last edited:
Trent Lillehaugen said:
The SVN revision is not for the camera, but rather for the firmware.
Click to expand...

Whats the estimated fix time for this please, 3.2.16 is good apart from this, the camera used in a housing is inconvinenet to say the least if this occurs underwater.
 
Yes... I don't think this build is ready for the big time. We did a car shoot today. It was full of little bugs. Playback freezing, playback jitter... jammed playback, white screen starts, white and black screen starts... Split screen previews. Hi frame rate (120 - 240 fps) 6 frame per second live viewing.. (which was highly annoying). No battery levels... and a few more little things that I cannot remember now.. All cured (except for 6 frame per-second on all hi speed shooting monitor viewing) but all other things cured with a simple restart. but that becomes boring after a while.

But ... all that said. The R3D's are perfect.

I would'nt be installing it for a while. We will be taking all our cameras back one build. Just to be safe.

PS 5k HD was good to have. :)
 
Have not installed this release build after reading so many negative experiences, but I'll add, just for general Reduser knowledge, that I have shot quite a bit on the beta build with no problems (other than half white screen on boot-up occasionally). It's as if the release build is behaving as a beta, and vice versa.
 
James Fleming said:
I upgraded to 3.2.6 yesterday, did some tests and then went out on an observational doco shoot. I love the new high frame rates which I put to good use. Other little touches are welcome too, like the on screen message that pops up when you press a button, letting you know what you've hit. It's good when you accidentally press something. There was a glitch though. About every 5th time I hit record the recording light just went yellow, the menus froze and I couldn't record. Hard rebooting fixed it but I missed a few things in the meantime each time it happened (about a dozen times in 2 hours). Anyone else having this problem on Scarlet. Even with this glitch I'm reluctant to roll back the firmware because the other features are so good. For those who haven't, I don't recommend upgrading quite yet unless you can get around the stability issues.
Click to expand...

I am getting same yellow dot freezing problem. Never had any issues with cam before 3.2.16 firmware. Sent logfile to red support. Hoping new firmware will fix it.
 
guys,
Please issue some sort of text (manual update) to help with: how to use the new functions and possibly how to set up the new functions, would be great!
thanks!
 
Mike Garrick said:
Hah maybe its an Ozzie problem !!...like our toilets flowing in reverse to the northern hemisphere.

Anyway after some success with 3.2.16 I had a few days with no problems then got the white screen, the Iso freeze etc so I have rolled back to 3.2.07 The thing I like most about 3.2.16 was the snappy side handle response. So here in 3.07 land I sit eagerly awaiting 3.2.17 version!

P.S Hopefully Red allows for gravitational differences between the Northern hemisphere & our Southern hemisphere when creating software updates.
Click to expand...

Probably a southern hemisphere problem, indeed. Here in Argentina I have the split black/white LCD when booting most times (not always) on both Epics, corrected with plug/unplug. Didn't test every function, but apart from that they seem to work ok. They have already been rented a few times with no complains (I tell about the LCD problem beforehand).
Guido
 
I thought the white-screen problem was gone for me, but today i had it again multiple times. Fixed it with the magnify-button. Today i also noticed some lags when changing settings. I still love the new firmware, can't go back, the flexibility for customization is just awesome.
 
Hi all. This may be my first post, but I have been watching RED evolving since 2007.

I finally decided to upgrade my Scarlet to 3.2.16 two days ago. I have been testing it ever since. I’ve had the split Black/White screen right after the installation; a quick reboot fixed it all up. So far, I found absolutely no additional issues. Many thanks for this great upgrade go to you, Jarred, as well as the RED team.
 
You must log in or register to reply here.
Back
Top