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

Rocket crashes and stops playback/ rendering...claims corrupted frames

Dominik Muench

Dominik Muench

Well-known member
Joined
May 23, 2008
Messages
2,301
Reaction score
1
Points
38
Location
Gold Coast - Australia
Website
www.instagram.com
hi guys


i'm having an issue with my redrocket, redcine x detects the rocket fine and lists it as active, but it doesnt accelerate playback or rendering, when i try to playback at 1/2 quality, which worked fine in the past and as recent as yesterday, the playback is now sluggish, after a couple of minutes the status error message pops up:

RR CALLBACK - DECODE FAIL - FRAME; 6200 ITEM; 0X104C871B0 MODE; 'DRCR' CUSTOM SIZE 1280X675 PIXEL TYPE...... failed to decode (corrupt frame?) screenshot of full error message attached.


the footage however is fine and looks and plays back ok when the rocket is not attached through my thunderbolt and sonnet case.

could this be a hardware issue with the card ?
 

Attachments

  • aaaaa.jpg
    aaaaa.jpg
    55.7 KB · Views: 0
As far as I have seen:Nope.

I guess that is related to RED not being the manufacturer of that card.
It says DVS on the board and looks a lot like the Atomix board (not saying it is the same or has the same firmware and not designed by RED, just saying the Atomix board looks quite familiar when you've seen a few rockets.)

They seem to get the same hardware failure.
There were quite a few that got the same hardware failure in connection with firmware upgrades.
I have seen some.

You'll get an offer to have it fixed/refurbed for 3000$

Which happens to be the norm for second hand/battle-tested Rockets.
 
Dominik Muench said:
ouch, that doesn't sound good at all.
Click to expand...


Nope, it doesn't.

But you can have it sent in and prove me wrong, of course.

I am in no way affiliated with RED or have any real knowledge of this issue, except for seeing rockets developing hardware faults in situations where one would expect software stuff to happen.

But that is just an observation, and possibly a faulty conclusion...

This is thus to be considered irrelevant hearsay based on observations and no official RED comment on the subject.
 
So after reinstalling the redrocket driver and completely powering down my editing station as well as the sonnet box and unplugging and reconnecting all the thunderbolt ports, it seems to work for now.....I just dropped 50 clips as a batch render in redcine and it chewed through them without a problem, this might only be a temporary fix though, we shall see :/
 
Ah shit. Mine is also 2.5 years old, and started having this problem with the latest firmware upgrade last month. I can get it to work sometimes, sometimes not. So you all are just saying its a matter of time? 2.5 years seems like an awfully short lifespan for something so expensive.
 
Dominik

I've recently ran into same error/issue with our card while running it via our Magma, I tried a few reinstalls of the latest firmware and would get a few clips in then same error. We were under a deadline so in a last ditch effort rolled back to Red Cine 15 and booted 10.8.0 from a drive I keep around for situations like this.

When I first received my TB enclosure and there was an issue with 10.8.2 I was getting these same error which is what prompted me to roll back in this case. The card has since been thrown into our PC workstation and we have been running with no errors.

Best



Dominik Muench said:
So after reinstalling the redrocket driver and completely powering down my editing station as well as the sonnet box and unplugging and reconnecting all the thunderbolt ports, it seems to work for now.....I just dropped 50 clips as a batch render in redcine and it chewed through them without a problem, this might only be a temporary fix though, we shall see :/
Click to expand...
 
turned out to be only a temporary fix, card is definitely on the way out, reflashed the firmware and reinstalled the drivers but the error is now permanently happening every time I try to open an R3D file with the card active :/
 
You must log in or register to reply here.
Back
Top