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

Corrupt frames - please help

I have played it back on the camera but the problem is you only see it when its at 1/2 or full debayer so even when your looking at the clip in RCX you only really see the issue when your at 1/2 or some times only full rez. I think the camera playback is only 720....
Im checking a new transfer with out the esata from the RedStation so Ill let you guys know how that goes.
Im also going to render out all the clips from the corrupt files to compare where the issue is and cross check it with the new transfer of files out of the REDMag.
 
I am experiencing the same problem. Any updates on what the issue might be? I tried recopying from the SSD directly to my computer's drive (as opposed to an external - where I first noticed the problem) and the exact same frame is corrupt. I would suspect if it was a "card reader" problem - it wouldn't happen on the exact same frame? Filed a support ticket.
 
Yes - I'd love to get some more input from Red. The info I received was pretty vague. After sending in sample frames and a log file I was told I should upgrade my firmware. But I was on "release" firmware when the problem occurred. So it begs the question - what is "release" firmware, exactly? If this is a firmware bug - clearly it is not ready for prime time and should not be cleared as "release" firmware, no?
 
did you guys file a ticket with RED? when these issues have popped up for me i file with RED and follow up with them on the phone and i usually get all the details direct from them....my case on the R1 it was a bad video card...but bottom line you have to follow up and do some work with them and give them details rather than hope they run across this thread and have to speculate....
 
Like I said - the response I got was vague. It said engineers "believe" the corruption was firmware related. Does not give one a lot of confidence when supplying a camera to commercial productions.
 
Dylan Macleod said:
Like I said - the response I got was vague. It said engineers "believe" the corruption was firmware related. Does not give one a lot of confidence when supplying a camera to commercial productions.
Click to expand...

It's been occurring since the build in May apparently (Perhaps even earlier)... so either the engineers are stooped and have not come up with a fix since then, or the problem is much deeper than anticipated. It's a nasty issue too since it's random... please RED, give us an answer soon!
 
The side effect of this corrupted frame is: All the good clips in the same folder don´t play well within RecineX (With and without the Red Rocket). They slow down, get stuck after a while. Do you get the same issues?
And, the corrupted frame looks different when I output it on a Macbook Pro then on the MacPro with Redrocket.
BTW I`ll get a ticket if it occurs again, and will send the LOG file to the support.
Marc
 
It's definitely not a heat issue. A few weeks after my really bad corruption (almost completely artifacted frames every second or so) I was shooting in Israel in 46 degrees celsius (115 fahrenheit), no issues whatsoever in the direct sun in the dessert. But in the nice cool studio our clients lost an entire interview. Definitely not a computer or red station issue as the corruption was directly on the ssd's and showed up during in camera playback. The uncertainty of this issue is very unnerving. We never when we could just lose an entire shoot. It's not feasible to always watch all the footage back right away and reshoot.
 
I'm thinking it's an SSD issue as well. I've had this corruption happen on one of my 64GB cards, and not on the other from a shoot I just had recently. Swap was done in the middle of the scene... all the takes on the glitchy card were not usable because of the artifacting, yet the other card ran fine until the end of the day.

Now is it a hardware issue or software...?
 
Actually for me it happened only on one ssd both times it happened as well. No problems with that SSD since. I am not sure if it was the same one both times though.
 
My rep says that they have had no reports of this on Firmware 3.2.21 - so the claim is that it has been solved. Has anyone experienced this on Build 3.2.21? If so - file a ticket so we can help them get to the bottom of it.
 
Johnny Friday said:
did you guys file a ticket with RED? when these issues have popped up for me i file with RED and follow up with them on the phone and i usually get all the details direct from them....my case on the R1 it was a bad video card...but bottom line you have to follow up and do some work with them and give them details rather than hope they run across this thread and have to speculate....
Click to expand...

Yes I did sumbit a ticket, then sent log files and then Red requested my camera be returned. The Red Techs had my camera for about two weeks and were unable to reproduce the problem, but did upgrade the firmware.

As to it being an SSD issue I doubt it as it ocurred over all three of my SSDs. it was not more common on any of them.

At this point I am still worried that I will get the issue again and would love further information from Red as to the corrupt frames possible causes. I will happily change Laptops or hard drives or what ever may be causing the issue, or if it camera related I'd love a bug fix.
 
Dylan Macleod said:
My rep says that they have had no reports of this on Firmware 3.2.21 - so the claim is that it has been solved. Has anyone experienced this on Build 3.2.21? If so - file a ticket so we can help them get to the bottom of it.
Click to expand...

I had this issue on the beta of build 3.2.21.

Upgraded to release 3.2.21. Going to shoot a bunch of tests... I'll report if I get the issue.
 
Dylan Macleod said:
My rep says that they have had no reports of this on Firmware 3.2.21 - so the claim is that it has been solved. Has anyone experienced this on Build 3.2.21? If so - file a ticket so we can help them get to the bottom of it.
Click to expand...
I had it with 3.3.4. Could not file a ticket because me stupid did not copy the LOG file.
With this SSD mentioning: could it be the SSD side module, not the SSD? This would make in a way sense to me, because I did not have once this issue in the first five months. A loose cable inside, dust or some smear on the contacts?
BTW the last time it happened the cam was on a tripod, not moving, 20° Celsius.
Marc
 
I filed a ticket now.
I did some more testing and here are my results:
-ScarletX with same SSD (128GB), both times filled it up until about 50% with shots from the same subjects. Lot of leaves in it and fast moving birds. 4K/ 25P 6:1 and 3K 48fps 7:1 and 1/200th shutter speed. Tripod, no camera moves.
Copied to the HD with SSD reader/ FW 800: 2 corrupted clips. No surprise, because in the middle of the shooting the cam freezed, means, would not stop recording by pushing any of the record buttons. So I had to do a forced shut down. Power up again and it worked normally. Artifacts visible in playback.

Then I formatted the card in camera and shot again the same subjects. No freeze this time. Downloaded the clips exact the same way like before. No issues the second time. All clips without corrupted frames. Same SSD!
An other observation: A clip with corrupted frames- artifacts- does not play at all anymore on my Red Rocket MAC ( I have to go trough frame by frame) , but plays on the laptop...BUT on the Laptop there are much more artifacts.

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