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

RED CINE-X Failed to Decode (Corrupt Frame)

Marc Dunham

Marc Dunham

Well-known member
Joined
May 10, 2012
Messages
140
Reaction score
0
Points
0
Location
Los Angeles
Hoping someone here can shed some light on my problem. Been having some issues running RED footage lately on my Imac (2012 full supped up). It would constantly have problems playing back footage in Premiere, it would also cause my screen to start glitching out really badly, eventually the computer will go black, log off/shutdown from some error. I decided to check one of the clips that has a problem playing all the way through in RED Cine-X and am getting

"unable to decde video frame: ### from clip #### reeason: 6 Clipld: 0x05156420 - Details: Dailed to decode (Corrupt Frame)

Checked some footage that I shot a few months ago and I don't seem to be having any issues playing this footage at all. Leads me to believe the Imac is fine and my footage is corrupt. This worries me however because this isn't the only day of footage this occurs on (nothings too important thankfully). Nothing weird was happening during shooting however. I'm currently on beta build, which is the first thing I'm considering as a culprit, but could this be a much more serious problem? Is there anyway this can be diagnosed without sending the camera in? I guess let me know what information if any is needed.

**Oh also, this doesn't occur on every clip from the mags either, so Its hard for me to just shoot test footage and know if its working or not
 
New development, I put a corrupted file (its corrupted on my Imac and Macbook Air) back onto a redmag to play from the camera and the clip plays fine in camera. Just seems to have the error when playing in either computer. Now I'm confused
 
Not using a RED rocket right now actually.
 
Had about the same problem.... it's possible that you can rescue your clips from the SSD with REDUNDEAD... if you have not reformatted the mags.

Try to play back the clips from the SSD in camera. if that works you probably have the same issue as I did on a rental camera 2 days ago... think it's a framerate/build issue.. We shot 3x23.97fps
and got corrupt frames all over the place. Red is looking into it now. Me guessing, this is why the last firmware update came out...

See thread:
http://www.reduser.net/forum/showthread.php?111302-Error-transcoding-r3d-file&highlight=
 
Alexey Milokost said:
Same problem, sent a file to Red for examination, they said that it's a firmware issue, you need to upgrade to 5.1.35
Click to expand...

Once updated to the new firmware, is there any way to recover the material from the SDD (that has already been recorded on the previous firmware, 5.1.34, and reporting dropped frame issues)?
I'm trying right now the REDUNDEAD recovery feature with no results so far.
 
REDUNDEAD didn't finally do the trick, not a single frame was recovered and the dropped frame count showed the same result after using the program.
RED technicians just told me to upgrade the camera... which is kind of funny as I'm just the post guy and wasn't asking for that...
 
I'm having same problem. I updated to build 30 and this kept happing went back to build 22 and now its happening there too. Never had any problems in the past before this.

If I restart a cpl of times on build 22 it works but this is obviously very worrying and annoying. Once its up and running it seems fine but if I have to close for any reason I have to go through the same restart process a few times to get it back working.
 
The same issue here. Really annoying. DaVinci after dropped frame shows blank screen. Adobe AE crashes...
Is there any way to avoid this? What is the solution?
 
Dear Bjorn,

I just faced the same problem that you faced 3 months ago. So I just joined the community :) So does the new firmware update resolve the problem ? I did not do any updates yet because I am careful with these updates since I do not want to break a flawless working (seems that it was not flawless) camera. If you resolved the problem can you please kindly let me know which firmware to stick with.

Best,


Björn Benckert said:
Had about the same problem.... it's possible that you can rescue your clips from the SSD with REDUNDEAD... if you have not reformatted the mags.

Try to play back the clips from the SSD in camera. if that works you probably have the same issue as I did on a rental camera 2 days ago... think it's a framerate/build issue.. We shot 3x23.97fps
and got corrupt frames all over the place. Red is looking into it now. Me guessing, this is why the last firmware update came out...

See thread:
http://www.reduser.net/forum/showthread.php?111302-Error-transcoding-r3d-file&highlight=
Click to expand...
 
You must log in or register to reply here.
Back
Top