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

OK, took the plunge, now nothing works...

Can someone in authority on the subject place a sticky at some stage regarding sequence-of-upgrades to avoid more of this kind of thing happening (I would love to jump to build16 but threads like this mean I might never take the plunge)

Good to hear your back on-line Gunleik.
 
jtm said:
Can someone in authority on the subject place a sticky at some stage regarding sequence-of-upgrades to avoid more of this kind of thing happening (I would love to jump to build16 but threads like this mean I might never take the plunge)

Good to hear your back on-line Gunleik.
Click to expand...

Same here. I would like to upgrade from build 15 to build 16 this weekend.
Is it safe to go directly to the latest beta build (after the intermediate 2.2.8) or do we need to do it incrementally?
 
It's all detailed in the "build_16_v3.2.1_install_readme" file that comes with the upgrade download...

"Note: Before upgrading to Build 16, you must first upgrade the camera to Build 15 v2.2.8, or have previously upgraded to earlier beta version of Build 16."

These are called "README" files for a reason, guys!

:wink:
 
Upgrade Sequence.

Upgrade Sequence.

Is it safe to go directly to the latest beta build (after the intermediate 2.2.8) or do we need to do it incrementally?
Click to expand...

Yes, as the READ ME says. :red_bandana:

First load Build 15 v2.2.8, then you can load any version of Build 16 - including v3.2.1 or any other version if your prefer.

I don't know specifically what would cause Gunleik's LCD issue, but a firmware re-install is a reasonable idea if something weird happens like that. The install should clear out all camera registers, a second install would flush any that possibly got stuck the first time.
 
It has become subsequently better as I've re-installed builds, and is now close to gone...

Just to be clear:
This can pop in with the cam standing alone on the table (as it was on the initial upgrade), and it disappears after ending a recording session. Without the cam being otherwise physically touched (other than hitting the rec button again)

I'll try to do another re-install

Cheers.
 
OK.

Haven't tried on another cable, but I can can confirm that it happens synchroniously and identically on the HD-SDI tap.

Will try to re-install the latest build before taking Charlie out tomorrow.
 
Unfortunately, not.

It was gone for a while, but now it's back in a baad way.

Have tried to swap cables. Same thing.

After a hellish shoot yesterday (nothing almost worked monitoringwise) I booted today.

Everything fine

Again; Fine

Again: Fine

Again: F***ed

tried to re-install the 16 builds, everything is as bad.

The thing is that when you push the menues, the green gue (if present) moves around.

Symptoms (all or any one can be present at the same time)

1. Magenta cast
2. Pixels offset (so where you should see white, you see red, green and blue outlines)
3. Green "snow" appearing randomly around the scree, changing place as you push the buttons.

I must stress that when I did the boot test this morning I made a point of not touching anything but the power button...

And that the symptoms change as one walk through menues.

The recordings are fortunately good, though.

Any possibility the build 16 upgrade involves some kind of firmware upgrade to the LCD?

Gunleik
 
Gunleik, I am sure you probably already have, but have you opened an incident ticket on RED.com/support so one of our techs can help? PM me if you need any additional assistance,

BC
 
Gunleik, Brent are there any news on the boot problems? Heard from a german rental house, that one cam was not booting anymore after installing build 16. In a other thread I think I read that there was a problem with the CPU board and had not really something to do with build 16. I am asking because we have with beginning of september a big feature to shoot and want to do it on build 16. But if we have no stable firmware and we can't be sure that the cam will not get damaged by upgrading to build 16 it will be a problem.

So can you give us please an update...

thx

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