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!!!

So far no problems on this end using the following configuration.

Build 20.1.3
Red Drives (The old school, first batch drives)
The old drive cables (shorties)
Red Bricks
4KHD and 4K 2:1 modes

I have a shoot tomorrow that should really put everything through a good test, so I'll report back if I experience this issue. As of right now, all is well (knocking on wood).
 
I have a few brand new drive cables unopened. I also just had my cameras come back from the upgrade program with a clean bill of health. I just upgraded 1 camera to new build 20. I will test tomorrow with old and new cables. If I have any errors, I will report. Got a very important job next week and absolutely cannot have this problem. Thanks for bringing this up in the forum.
 
Guys, as would be expected, we are tracking this thread. As requested, keep contacting tech support if you have this issue and send us your log files. As soon as we have more info, we will let you know.

BC
 
I will test tomorrow as well. My camera just finished another job and I didn't want to upgrade to build 20 in the middle of that. All my drives and cables are the old ones and then RED RAM as well. I'll give them all a good test with the new build.
 
I just got word back from Red Support that both my Red drives needed a "component replaced". I don't know what the component is and they didn't say anything was wrong with my cables. Hopefully that fixes the problem for me. I will test as soon as the drives and cables get returned.


Mahalo,
Dusty
 
Brent@RED said:
Janne, I see the support ticket your filed (#42096) yesterday and also where Nate replied back to you. Did you not get the reply? I will forward his reply.

BC
Click to expand...

Hi Brent,
No, I did not get it.

Edit: now I have :)
Thanks
 
Ferrite fix

Ferrite fix

Some extensive use of ferrite core on both ends of cable will also (to some degree) fix this problem. I found that the camera have more errors when close to RF sources and more ferrite cores will filter out this better.

http://en.wikipedia.org/wiki/Ferrite_core

ferrite_fix.jpg
 
Laco Zamba said:
Maybe RED could offer special ferrite cores with RED logo to fix this problem :-)

Sorry - I couldn't resist.
Click to expand...

Second that... If it is a design/material problem that is not allowing the cord to function as it should be, or starts to fail before it was meant to last (well, if this is the cause of the B 20 issues), I see your proposal as a viable one for Red to fix it.:badputer:

Note: Mine does not even have one as yours...BTW, what "components" they were talking about?
 
SATA error

SATA error

Maybe RED could offer special ferrite cores with RED logo to fix this problem
Click to expand...

Its best not to guess here. If you are having this SATA error issue please discuss with RED tech support.

The root cause could involve the cable or the drive, which is why we'd like to communicate individually.
 
I have tested the drive in 4K 2.1 & 2K 2.1 with varispeed mode at redcode 36 with new red cable with red logo molded in. I have not had any issues. I have also played back footage and still no issues. Is there something that I should try to recreate this problem? Also, were the early version of the drive cables with out the Red molded logo? I seem to not have anymore left if that is the case cause all my Red drive cables have the molded logo.
 
Steve Gal said:
... Also, were the early version of the drive cables with out the Red molded logo? ...
Click to expand...


I own # 711 and my cable has no Red molded Logo...:blush: Fancy, eh???

Tonight I have a shooting for a TV commercial, quiete complicated (it is with a heavy metal band !!!), and we upgaded to the latest version yesterday night. Should I be ready for posible headackes, aside of the normals I get while DP'ing? :gun:
 
SATA error

SATA error

I'm going to repeat what I said above.

Its best not to guess here. If you are having this SATA error issue please discuss with RED tech support.

The root cause could involve the cable or the drive, which is why we'd like to communicate individually.
 
Stuart English said:
The root cause could involve the cable or the drive, which is why we'd like to communicate individually.
Click to expand...

Ferrite core is just for emergency tip if your on a shoot and get this problem.

Red support have been very good, and in my case it was just a bad drive cable. It have gone back to RED now for replacement.:emote_hippie:

Cheers
 
I'm guessing that Red is taking advantage of the SATA protocol's ability to report back if a bit has been transferred correctly or not to the host controller. This is why they need to see individually whether it's the RedDrive/RedRAM or the cable, as either being defective would cause the same error message to be passed.

Happy to say neither of our drives or cables exhibit the problem.

HTH

Paul
 
I have been shooting 20.1.2 and have not had that issue although i hear that many drives are failing now. I am also using the old cables that have no ferrite cores.

The only thing I notice with B20 is that I'm having more frequent boot hangs like before I went to B18.
 
boot hangs for me have always been, not alot but on an ongoing basis. as far as the drive issue goes, I just did 3 days of music videos and a commercial out in the hot sun with palyback and fast forwards stops reverse, at many different framerates and resolutions.
and no problems with old cables and older drives from when I got 1350, in april of 2008.
Hope this helps
 
You must log in or register to reply here.
Back
Top