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

Major_problem_build_20.1.3!!!

I'm staying on 17. Losing takes is scary shit. It seems that the only significant gains with build 20 are nicer looking ON SET preview images.

I can still use RedCine 20 on build 17 shot footage and benefit from the better tweaked color space.

Has anyone had serious issues with Build 20 is while using cards ?

Matt Uhry
www.mattuhry.com
 
Red, I don't understand why people were not getting this issue prior to Build 20 are now getting this issue after upgrading. What is going on here exactly? Instead of just telling people to snail mail their gear back to you, can you instead give us some technical insight as to why this issue is happening? Or is Build 20 just a way to sweep out all those bad drives and cables out there?
 
It is pretty simple actually. Before, if you had an issue with your drive or drive cable, it could cause the camera to reboot. So, in the release version of build 20, it gives you the SATA error message instead of a possible reboot of the camera. Just because you did not get a reboot before build 20, it does not mean that you would not have at some point if you have an issue with your drive or drive cable. So, if you get the SATA error, contact tech support so we can troubleshoot for the real cause of your issue.

Thanks, BC
 
Brent, I have to say I'm a bit skeptical about the analysis that the SATA error is something one experiences rather than a reboot.

I have never experienced a spontaneous reboot. Never. Not with any previous build and I've installed every one when it was released. Only this build has caused the SATA error.

I've send the tech support in, but have received no reply.

What is the customary response time for reporting this SATA error?

Should I have tried to phone in the report?

Best regards,

Leo
 
Leo, I see your support ticket in the system under ticket #42326. Sean replied less than 90 minutes later. I will forward you his reply....

Everyone, please make sure you whitelist the red.com domain in your email preferences. Please check your junk folders. Our domain is just gobbled up by filters...

I can understand your skepticism, Leo. Notice I said the SATA error trigger "could" cause a reboot, not guaranteed. Sure, you could have had a bunch of boots with no reboot. I kind of compare it to this:

Each time you drive on the freeway at 10pm, there are probably drunk drivers on the road. Just because they don't crash into you, it does not mean they are not there. The SATA error tells you they are there and COULD hit you. The reboot, it is too late - you just got hit!

BC
 
Hi Brent,
I really appreciate the the support I have got. Thank you. Just for my curiosity, is there a suspected cause of the error? Is there anything we should avoid or take action to reduce the risk of errors?

Best
 
Not really, it throws the error if there is any hiccup along the eSATA path. As you know, it could be a few things that generate the error - but 99% of the time it is the drive or the drive cable that needs to be evaluated for a root cause.

And thank YOU, JJ, for your patience and cooperation.

BC
 
Brent, are the drives or cables you are finding to be problematic from same batches or production runs? Is there any patterns to what you guys are seeing? So far I've shot a decent amount on Build 20 with the only issue so far being a playback error that happens occasionally. For reference, I have the original batch of drives and drive cables.

Matt Uhry, I think you have to test it out with your camera, see if the problem exists and when you confirm whether it does or not decide a course of action. There were bugs in Build 17 too. Overall, 20 seems to be an improvement and worth at least a look. You can always go back if it's not working for you. Then again, I suppose if Build 17 is working for you and you're getting everything you need out of it, maybe just leave it where it is until you need to go to a different build. The old don't fix it if it ain't broke. :-)
 
No troubles to report with Build 20 here. I think there's just a handful of people with problematic drives/cables. There's not that many people complaining about the problems, assume that even 10X that many people are experiencing such problems. So that's maybe 100 assumed people out of nearly 7000 cameras having this problem or less than 1.5% of camera owners.

Best thing to do is upgrade to the new build and test all your media and shooting modes and see if it's reliable. If not, then contact RED support and they will help you fix the problem.
 
Steve Sherrick said:
Matt Uhry, I think you have to test it out with your camera, see if the problem exists and when you confirm whether it does or not decide a course of action. .......... The old don't fix it if it ain't broke. :-)
Click to expand...

Next job is a national commercial, It's the agency's first Red job. Feeling super risk averse. Will check out 20.1.3 on something else. Thanks for all the good input guys.

Matt Uhry
www.mattuhry.com
 
Build 20

Build 20

Next job is a national commercial, It's the agency's first Red job. Feeling super risk averse.
Click to expand...

The lowest risk (and highest image quality) option is Build 20 v20.1.3 to 8GB or 16GB CF
 
I also get SATA_TRANS_FAULT errors with the new firmware. But only when I use a new drive cable (with ferrite). It works fine with an old one (without ferrite). Never had problems with both cables on firmware 17.

Filed a ticket...
 
20.1.3 weirdness

20.1.3 weirdness

we are also experiencing weirdness with this build... what the heck is this junk at the bottom of the frame. 2 cameras showing the same type of artifacts, that never happened before. Tried processing out the footage on different machines, and all output resolutions (full, half-high, half-standard etc.) Cards we're freshly formated, then zeroed out, but the problem remains. ETA on the fix to this software glitch? seems significant to me. FYI I never had any issues what-so-ever with the "beta build" 20 RED staff?

A026_C004_0822CS_00000.jpg
 
...and just now got a call from some people of mine in the field saying that the camera is reporting the media too slow on a Red Drive...geez, I thought we were past all this with "released firmware"

I hate trying to trouble shoot issues for my staff, when I can't seem to get answers from the manufacturer...
 
holy crap. I guess trouble comes in 3's now another seasoned operator using 1790 says he is getting the SATA_TRANS_FAULT error.........

I guess I'll put all the other work on hold to try and deal with all this...

nice.

edit - just called all my staff back, to roll back all camera's to previous build.
 
Colin, what do you mean you cannot get "answers from the manufacturer"? You saw my reply on the other thread where you originally posted. Have you filed a support ticket?

As I said there, I have never seen the first issue you are reporting. If it is not there when you roll back, I will pas this along to engineering. Issue two - What are the settings you are trying to record at? Third issue - See my posts on this very thread about SATA errors.

BC
 
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.
 
Brent@RED said:
Colin, what do you mean you cannot get "answers from the manufacturer"? You saw my reply on the other thread where you originally posted. Have you filed a support ticket?

As I said there, I have never seen the first issue you are reporting. If it is not there when you roll back, I will pas this along to engineering. Issue two - What are the settings you are trying to record at? Third issue - See my posts on this very thread about SATA errors.

BC
Click to expand...

issue two - 4k 2:1 23.976 RC36

issue three - goes away when rolling back to previous build.
 
You must log in or register to reply here.
Back
Top