Rocket Davinci Conflict...

[Tom.Wong]

Grading a feature, old sensore, new color science, looks awesome. Everything was going ultra smooth, 8 core mac, quadro 4000, gt 120, rocket and decklink. 16 gb ram. 5 internal raid

So I start getting to finish coloring matching in all my scenes, 2 hour film. Things were really smooth, but towards the end I start crashing like crazy. Da vinci would constantly quit out by itself. I could barely scroll through the timeline before it would just crash out.

At first I thought i didn't have enough horsepower and I was overloading the system with my many nodes, and tons of tracking. But I decided to rip out the rocket card and everything is smooth as butter again. So obviously it's a rocket conflict, and probably a conflict in playback and dumping all the effects form the GPU. does anybody else have any similar issues? will there be a future fix on this? play back quarter rez without rocket is fine, but I still need it for the full debayer output, and I'm hoping the rocket won't affect the stability of the render...

Really a serious issue.

 

[Peter Chamberlain]

Could be a driver issue, or the card. Doesn't sound like application issue but you could capture the logs from /Library/Application Support/Blackmagic Design/Davinci Resolve and send to tech support.

BTW, without the Rocket Resolve will do a full res and premium decode for your render, it will just take a while.
Peter

 

[Shane Betts]

Hi Peter. We're suffering a similar issue here and I think someone over on the Cow mentioned it too. So many updates from so many companies and sometimes somebody's toes get crunched. Can you guys talk to Red?

 

[Tom.Wong]

Could be a driver issue, or the card. Doesn't sound like application issue but you could capture the logs from /Library/Application Support/Blackmagic Design/Davinci Resolve and send to tech support.

BTW, without the Rocket Resolve will do a full res and premium decode for your render, it will just take a while.
Peter

I cross posted in the creative forums. Gotta finish this job first then do tests with the rocket. I wanted the rocket to accelerate higher quality playback nd render out faster witg r3d. Pointless if i cant use it. Hopefully reinstalling firmware and drivers will solve this. If not i hope my log files can help solve this issue soon. Hate to think i spent 3k on a card i cant use.

 

[Peter Chamberlain]

Tom, can you clear some of your PM box so I can send you a mail?
Peter

 

[Tom.Wong]

cleared. I also sent in a log file and my system xml to BM. reinstalled drivers and firmware, still crashing. I even tried to see if i can render anything out using the rocket, still crashes. at the moment rocket is useless other than for RCX.

sigh*

 

[Uli Plank]

I'm afraid it's the card. We were so lucky to still get a few GTX 285, and our RR is happy in the system.

 

[Patrick Tresch]

Is your 2 hour film in one reel/project?

 

[Tom.Wong]

Is your 2 hour film in one reel/project?

Indeed it is, and in contact with BM support right now. Nothing but compliments to them btw, they responded so freakin fast and promptly it's not even funny.

but yeh that seems to be the problem. Seems like the conflict with the rocket is coming from having the whole r3d feature in one session, which apparently is a no no, and the recommend breaking up the film in 20 minute segments. I'm used to a Apple Color workflow, and i thought with a slick ass system and software like Da Vinci this could just eat it up. But the limitation seems more the rocket than the software, as I'm handling the whole feature without the rocket completely stable.

live and learn, now I learn the hard way. Deadline is too tight for me to start splitting up the project now, just gonna man up, not sleep for awhile and finish this puppy up, render it out with the rocket every so slowly. Next project I'll be completely prepared for this, and hopefully something can be worked out with rocket drivers so it can handle more in the future. I know several clients that want to see the whole film in front of them and be able to bounce from part to part as they want, without interruption. Ie. not closing down a project or session to open a separate one. So I'd still like to be able to have the whole 2 hour feature run flawless in one session one of these days, with rocket support!

Does the linux version have these kind of limitations? The rocket doesn't even work with linux right? But I assume all the big bux going to the linux version just means several times the horse power to do this.

would more GPUs and RAM help solve my issue?

 

[mikeburton]

It's standard procedure to break a film up into "Reels" segments to grade a feature. This is partly because most films are still printed back to....you guessed it film! Which means you can't print an entire film to on reel hence the 20 minute recommended chunks. Also for future reference always leave the first and last reels closer to 15-18 minutes for opening logos, credits and of course end credits. And as you've witnessed first hand there are performance issues to deal with as well. Even if your not printing back to film it's still a good way to work. Might be faster for you to send a quick EDL out of Resolve and manually break it up into multiple (6-8 reels) EDL's, reconform with all of your current grades and export with the Rocket than doing a Full Res debayer without the Rocket. It will be the difference from roughly realtime 2-3hours of rendering with the Rocket to 2-3 days without. Your choice but id reconform if I were you.