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 want my money back and send my scarlet back to RED...tired to deal with unfinished camera...it should be still in pre production and not sold as finished product!!! I am not going on the set with a camera that is making me feel uncomfortable and scared to get sued by a client!
 
Same problem here!
Don't know exactly the shooting condition but not shot in heat or humidity for sure.

Corrupted frames cause RCX-"pro" to crash, so I have to render image sequence, write down every bad frames, relaunch renders everytime it crashes and create my proxy from the dpx sequence. :banghead: :emote_hanged:
Totally random bugs...
 
This is weird...

Never had issues with corrupt frames on any of the epics I have been using ever...

This was a known issue on the R1 when shooting to cf, but was in all the instances I have been able to verify, a copying issue.

But on the ssd's i have yet to see a copy bug, and if it is firmware related, that kinda makes sense.

Just a bit taken aback by this thread, I guess...
 
3 of my 6 Epic

3 of my 6 Epic

3 of my 6 Epic whit the same problem
 

Attachments

  • 001.jpg
    001.jpg
    94.2 KB · Views: 0
  • Screen shot 2012-11-20 at 5.14.48 AM.jpg
    Screen shot 2012-11-20 at 5.14.48 AM.jpg
    14.9 KB · Views: 0
Gunleik Groven said:
This is weird...

Never had issues with corrupt frames on any of the epics I have been using ever...

This was a known issue on the R1 when shooting to cf, but was in all the instances I have been able to verify, a copying issue.

But on the ssd's i have yet to see a copy bug, and if it is firmware related, that kinda makes sense.

Just a bit taken aback by this thread, I guess...
Click to expand...

There are many threads like this...and many Scarlets with the exact same random problem. It puzzles me when I read posts like yours suggesting that this is a unique and uncommon problem, because it's not! It's not the SSD card slot. It's not a temperature problem. it's not a RedMag problem. It's not a Redcine-X problem and it's not a firmware problem. It's an early build Scarlet problem. RED fixes it (as they fixed mine) but with no explanation other that "a component was replaced". Honestly, I was very happy with the way RED dealt with my camera and got it back to me quickly (to and from Australia), but let's check reality here and accept that maybe RED sent out early builds of Scarlets that may have been rushed through the testing phase, or something of that nature. I'm not speaking badly of RED, but I'm also not in denial that things like this happen with camera's from the future.
 
Matthew Scott said:
There are many threads like this...and many Scarlets with the exact same random problem. It puzzles me when I read posts like yours suggesting that this is a unique and uncommon problem, because it's not! It's not the SSD card slot. It's not a temperature problem. it's not a RedMag problem. It's not a Redcine-X problem and it's not a firmware problem. It's an early build Scarlet problem. RED fixes it (as they fixed mine) but with no explanation other that "a component was replaced". Honestly, I was very happy with the way RED dealt with my camera and got it back to me quickly (to and from Australia), but let's check reality here and accept that maybe RED sent out early builds of Scarlets that may have been rushed through the testing phase, or something of that nature. I'm not speaking badly of RED, but I'm also not in denial that things like this happen with camera's from the future.
Click to expand...

Its also an Epic problem and according to Red its a firmware issue.
 
Tim Bradley said:
Its also an Epic problem and according to Red its a firmware issue.
Click to expand...

Firmware? Then how was I getting corrupt frames NO MATTER WHAT firmware I used? How was I getting corrupt frames, no matter what SSD I used? No matter what temperature I shot in, no matter if the camera was still or moving? After countless black shades and system restores. Read some of the other posts. Firmware fixes nothing. I wasn't aware it was an EPIC problem too...that sucks! I'm just glad mine is sorted now. I've had many shoots since it was returned to me and not a single corrupt frame :)
 
This artifact pattern probably isnt just one exact problem. Maybe its a symptom of several different problems. Some firmware, some hardware related. Like if you have a fever you could have many different diseases.
 
Thomas Koba said:
This artifact pattern probably isnt just one exact problem. Maybe its a symptom of several different problems. Some firmware, some hardware related. Like if you have a fever you could have many different diseases.
Click to expand...

I hear you, but if you look at the Scarlet examples, they ALL seem to be predominantly to the right of frame, "corrupting" the same portion of the image.
 
I hear you, but if you look at the Scarlet examples, they ALL seem to be predominantly to the right of frame, "corrupting" the same portion of the image.
Click to expand...

Still, it could mean a 100 different things. Maybe the critical part of dumping a buffer of data to the SSD is when the computer IS dealing with exactly that right area. Or something like that. Then there could be alot of things, that mess up that buffer. The filling of the buffer/the emptying of the buffer/calculating of the buffer. A glitch in some timer-process could mess this up. Dust in the SSD slot. Slow SSD connection. etc. etc. I don't know I´m not a technical person, and it probably has nothing to do with buffers. :)

Just like audio-stutters. 50% of all digitial audio problems have the symptom of audio stutter. (This is NOT a fact checked number :) )
 
Matthew Scott said:
There are many threads like this...and many Scarlets with the exact same random problem. It puzzles me when I read posts like yours suggesting that this is a unique and uncommon problem, because it's not! It's not the SSD card slot. It's not a temperature problem. it's not a RedMag problem. It's not a Redcine-X problem and it's not a firmware problem. It's an early build Scarlet problem. RED fixes it (as they fixed mine) but with no explanation other that "a component was replaced". Honestly, I was very happy with the way RED dealt with my camera and got it back to me quickly (to and from Australia), but let's check reality here and accept that maybe RED sent out early builds of Scarlets that may have been rushed through the testing phase, or something of that nature. I'm not speaking badly of RED, but I'm also not in denial that things like this happen with camera's from the future.
Click to expand...


Sorry. I am not in denial. On the R1 it was another case.

Here it seems not.
Just a bit puzzled, as I haven't seen it.
 
Gunleik Groven said:
Sorry. I am not in denial. On the R1 it was another case.

Here it seems not.
Just a bit puzzled, as I haven't seen it.
Click to expand...

Okay, you're not in denial. Maybe that implication was a bit much, but it sure as hell is frustrating when someone who isn't experiencing the pain we new to red, want-to-love-and-trust-our-Scarlets-but-have-already-lost-clients-and-have-a-damaged-reputation users are, chimes in with how strange it seems that a RED camera isn't functioning properly. I am lucky enough to have had my camera recently repaired and back in my hands, but many others aren't. I guess I'm ranting on here in a strange supportive way because I know what it feels like. I enjoy your input and expertise on these forums but this post just annoyed me. Sorry.
 
Thomas Koba said:
Still, it could mean a 100 different things. Maybe the critical part of dumping a buffer of data to the SSD is when the computer IS dealing with exactly that right area. Or something like that. Then there could be alot of things, that mess up that buffer. The filling of the buffer/the emptying of the buffer/calculating of the buffer. A glitch in some timer-process could mess this up. Dust in the SSD slot. Slow SSD connection. etc. etc. I don't know I´m not a technical person, and it probably has nothing to do with buffers. :)

Just like audio-stutters. 50% of all digitial audio problems have the symptom of audio stutter. (This is NOT a fact checked number :) )
Click to expand...

You are right, it could be anything.
 
Matthew Scott said:
Okay, you're not in denial. Maybe that implication was a bit much, but it sure as hell is frustrating when someone who isn't experiencing the pain we new to red, want-to-love-and-trust-our-Scarlets-but-have-already-lost-clients-and-have-a-damaged-reputation users are, chimes in with how strange it seems that a RED camera isn't functioning properly. I am lucky enough to have had my camera recently repaired and back in my hands, but many others aren't. I guess I'm ranting on here in a strange supportive way because I know what it feels like. I enjoy your input and expertise on these forums but this post just annoyed me. Sorry.
Click to expand...

Thanks and no problem. Can def see how something like that roughs up the mood a bit...
 
I just wanted to add a bit to this. I've been having this problem with our Epic very intermittently since May, but it didn't rear its ugly head again until recently. Last week, a handful of frames, yesterday, I had clip actually stop recording with a yellow-instead-of-red recording indicator, and the camera shut down. That clip is full of bad frames. So I decided today to swap out the SSD Module from our Scarlet, and use a different SSD card, with the hope that this might solve it. Unfortunately, right from the start today the 1st clip looks to have several bad frames and the 2nd clip crapped out and shut down the camera like yesterday. Oddly, the 3rd clip is fine. I've filed a support ticket.

But at least for me, swapping out SSD Module did not fix the problem.....

And I'll add that this artifacting, looks almost identical to a problem I was having with my RedRocket a couple of years ago when transcoding (perfectly fine footage). It would introduce these same kinds of artifacts when transcoding. To fix that, it required a dip switch change on the rocket, which apparently reset everything, and then it was fine.
 
I have the same issue with footage shot last week. It`s a take of ca. 10-20 Minutes with maybe 4 of those blueish corrupt frame.

Because of the recording time it could be an overheating issue... hard to tell a week after shoot.
The files (recorded on a 64GB or 128GB REDMAG) were transfered directly to a MAC via the RED Station.
 
I have had the corrupt frames occur also, like those pictured on this thread.
Further to this a situation I have also experienced situations where clips cannot be seen at all in redcine or any other program I have been able to check it through. In my examples, in place of the standard clip preview thumbnail, I have had clips that no longer have a preview file and only see the word "offline" in red text can be seen. The clip cannot be played with or without a rocket in any version of redcine. Footage is completely inaccessible, and what would appear to be the full record data is sitting there, GB's worth, inaccessible through any program that handles r3d's. This happened to me on Epic SN 1995 back on build 3.0.0 (around April '12) and has recently returned on build 3.3.12. This time I also had an issue on one clip, where the record dot that is usually red, turned yellow and gave some sort of record error message on the touch screen. At least this showed me the clip was corrupted and the camera had to be restarted and that shot redone. On the most recent occasion where corrupt files occurred, the corruption was only present on the 1st one to 2 clips, after that, perhaps once the camera had warmed up more (?) it sorted itself out and what was recorded from then on was fine. I have filed a support ticket on both occasions and received no solutions from Red, not even 'send the camera in and we'll try and fix it' and this time no response at all. Makes me nervous shooting when I am unsure whether what I film will be accessible later. On the occasions mentioned except where the record light turned yellow, I had reviewed the corrupted clips briefly in camera to check their visual presence (not knowing they were corrupted) These clips I later discovered were corrupted, but could play back in camera, leading me to believe the footage was fine. Obviously not a rigorous enough test it seems...
I love this camera but I really hope Red get to the bottom of this problem as a priority, as it is clearly costing reputations and red user confidence in the camera they support, as we cannot afford to continue being left with missing corrupted footage.
 
I got corrupted frames too on my Scarlet since i installed last firmware.I've tried changing the EVF cable, the SSd's etc, the corrupt frames still there. Rolling back the firmware to 3.2.21 has fixed the problem. But if i reinstall the 3.3.14 the failure come back. So it seems, in my case, that's a firmware problem. I will wait till build 4 to see what hapens.

Just my 2 cents
 
You must log in or register to reply here.
Back
Top