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

Major_problem_build_20.1.3!!!

Nikolai Pigarev said:
Ok this might be a wild guess. But from 9 camera i have easy access to - 3 have had the SATA ISSUE. An interesting note is that these 3 did not go through RED audio board upgrade. On one camera the issues vanishes on 20.1.1 on another i have managed to have a stable one day shooting with downgrading to 18 and upgrading back to 20.1.3.
Click to expand...

Contact or call tech support. This issue is 99.9% either the drive or drive cable.

BC
 
Bottom of frame image corruption

Bottom of frame image corruption

what the heck is this junk at the bottom of the frame. 2 cameras showing the same type of artifacts, that never happened before.
Click to expand...

What post firmware are you using to create that image?

4K 2:1 records perfectly under Build 20 v20.1.3 in our tests.
 
Issues

Issues

issue two - 4k 2:1 23.976 RC36
Click to expand...

And that works just fine to RED-DRIVE too. Best to send RED tech support a LOG file.

issue three - goes away when rolling back to previous build.
Click to expand...

Well it would, Build 20 v20.1.3 is the one that adds the more rigorous SATA error check. So if you roll back to a previous version of Build 20 you won't see it, but you will then run some risk of camera reboots in record when using a RED-DRIVE, that is also true of Builds 18, 17 or 16.

Have a discussion about your options with RED tech support, rolling back firmware is certainly one of those... but ideally when its convenient for you they should inspect your RED-DRIVEs and SATA cables.
 
Rollback

Rollback

Colin, in the other thread you said

"rolled back, everything is ok, rolled forward back to 20.1.3 problem reappears "

Which of these three problems re-appeared? And rolled back to what version of firmware?
 
Stuart English said:
Colin, in the other thread you said

"rolled back, everything is ok, rolled forward back to 20.1.3 problem reappears "

Which of these three problems re-appeared? And rolled back to what version of firmware?
Click to expand...

the results of rolling back to firmware 20.0.0 (beta) was that all the issues I described have gone away, all issues have gone away. The footage looks fine, audio is fine, everything is working as it did before. Installing 20.1.3 reintroduces the same problems I described.
 
Stuart English said:
Well it would, Build 20 v20.1.3 is the one that adds the more rigorous SATA error check. So if you roll back to a previous version of Build 20 you won't see it.
Click to expand...

So far so good on my end (fingers crossed).

But in my opinion if you are going to add a "more rigorous SATA error check" you might consider trying that out in the beta build first, not the release. Unless I'm reading the statement above wrong.
 
Dan Blanchett said:
So far so good on my end (fingers crossed).

But in my opinion if you are going to add a "more rigorous SATA error check" you might consider trying that out in the beta build first, not the release. Unless I'm reading the statement above wrong.
Click to expand...

It was in the 20.1.2 beta build released on Jul 28.

BC
 
Got my drive and cable back from Red today.
It took ONE week. Great Work.

Wanna thank Brian, Nick, Daniel, Sean and Brent.
You guys were fantastic on the follow up.
 
I'm having the problem now!!! Until Build 20.1.3, OK! Then... build 20.1.3 in 3 RED Drives the same error:
SATA_TRANS_FAULT.
CF 16GB is OK!
camera N.#4375
Terrible!
 
Luis, thanks for your patience and glad we got it back into your hands quickly.

mariosbj, please contact tech support to get those drives and drive cables back to us for eval.

BC
 
SATA_error

SATA_error

You shouldn't, and most people won't see any media issues with the release version of Build 20 either. However if you ARE seeing SATA_TRANS errors, that means the camera firmware is doing its assigned job. To avoid those SATA_TRANS error reports you can go back to Build 17 or stay on Beta 20.

As another option we should have a version of Build 20 without SATA_TRANS error reporting in a day or so.


However, I will repeat.

If you are seeing SATA-TRANS errors under Build 20 v20.1.3, you should still arrange to send you SATA cable and RED-DRIVE to RED tech support for inspection.
 
Aloha Stuart,

I'm just trying to figure out my best course of action. Are you saying that no matter what you do to the software, some hard drives and cable will have problems with build 20 and beyond?

I have not upgraded to 20 for fear of this issue. Will it be eventually fixed in software or do we each have to check our drives and cables independently and send them in to get fixed if we want to use future builds?

I can wait a bit if it will be fixed in software but if not, then I need to move quickly before I get another show.

What is your advice? Thanks.

aloha,

Keith
 
Stuart English said:
As another option we should have a version of Build 20 without SATA_TRANS error reporting in a day or so.
Click to expand...

Hi Stuart. The Error in the display can be there, and it's good to know that something is wrong, but just let the recording continue as normal.

..or a meny item that maybe says, "Abort recording on error" -YES/NO :)

I probably get my drives and cable back tomorrow :) !!!!
 
SATA_error

SATA_error

I'm just trying to figure out my best course of action. Are you saying that no matter what you do to the software, some hard drives and cable will have problems with build 20 and beyond?

I can wait a bit if it will be fixed in software but if not, then I need to move quickly before I get another show.
Click to expand...

If you are experiencing SATA-TRANS errors to RED-DRIVE with Build 20 v20.1.3 (and the majority of people don't) its not because of a firmware issue per se Keith. We can conceal a SATA error but not fully fix the cause of it in software.

So only if you are, it would be best to get your SATA cable and RED-DRIVE inspected by RED sooner than later.


I probably get my drives and cable back tomorrow :) !!!!
Click to expand...

Lets us know how you get on with those Janne.
 
Keith, as the issue appears to be hardware (drive/cable) and either is or isn't present, it would be in your best interest to update the software, at least long enough to determine if you are affected.

If you are, just covering up the error isn't going to fix your hardware, it needs to go back to Red.

I have been using 20.1.3 since the day it came out, along with several other owners I know, and none of us have had a single issue with this.

It seems to be an isolated issue, but since 100% of people with the issue have chimed up, it makes it look widespread.

Believe me it isn't.
 
You must log in or register to reply here.
Back
Top