black frames on R3d are back

[Rohit Gupta]

What version of CUDA are you using? Check in system preference, CUDA panel.

[Nat Jencks]

CUDA 6.0.37
GPU Driver Version: 8.16.76 310.40.00.20f04

But this is happening even when I turn off GPU debayering.

Problem goes away when I go to completely software only debayer.
This rocket card has never had issues before and performs well in RedCineX Pro.

best-
Nat

[Margus Voll]

Maybe not a problem here but time shows in one point RR is a problem to everybody.

—

Margus

https://iconstudios.eu
https://vimeo.com/iconstudioseu/videos

DaVinci 10, OSX 10.8.5
MacPro 5.1 2×2,93 24GB
GUI 4000 / GPU GTX 780
DL 4K
Eizo Color
Scope Box
Full Ligthspace CMS

[Nat Jencks]

It does seem like its an especially moody card.

In this case though it seems to be related to the update in the way Resolve is handling R3D debarring, since it was working fine before (as of 10.1.1) and now doesn’t in 10.1.4.

Hmm. Luckily this isn’t urgent for me as I’m on another project (alexa) at the moment.

-N

[Sarah Jones]

Hi Nat,

CUDA 6.0.37 should generally be okay, but it might be worth a roll back to 5.5.28 just as a test.

Regards,

Sarah
Support Representative
Blackmagic Design Inc.

[Sean Ross]

I am having a similar problem except that I don’t have a rocket card. I am using GPU debayering only. My project has 8.5 hours of r3d EPIC files non-HDR. Once I scan down the clips, the first few work great. But as I go down the list previewing clips, either in the media manager or in the color window, I will get black clips. They appear to be playing, but nothing but black appears. What is even stranger, is that every time I relaunch Davinci, different clips will go black, and clips that were black before will sometimes turn back into color.

It seems to be that the only thing that is making specific clips black is the order in which I am clicking on them. It seems that the first 15 or so clips I click on in the project will show me video. After that, maybe one or two clips will show me information. Another strange thing is that I can no longer see the missing clips in my media library; the folders appear to be empty.

Also, shutting of GPU debayering allows me to see all of the clips.

I have 4 gtx 680 cards in a Cubix and am running off of a SAN. I am running 10.1.4 on a macintosh using os 10.8.5. Also, I have tried going back to 5.5.28 and it doesn’t help.

AAARGH!!!

I have tried putting clips into different folders in my Media Pool.

[Rohit Gupta]

Have you tried the 6.0.37 CUDA update?

[Nat Jencks]

Sean, this is EXACTLY the behavior I was seeing when using the rocket, so I think its safe to say that this happens with either the rocket OR gpu debayer, but NOT with software debayer.

Since you have tried with CUDA 5.5.28 and the newer 6.0.37, it also seems that it is not directly related to the CUDA driver version.

My guess is that back rev-ing the version of resolve to 10.1.X prior to 10.1.3 would solve the problem, but obviously I’m not sure, and in your case you don’t have a rocket card that doesn’t help you.

Sean, perhaps you can send BMD support your logs… Would love to see this issue solved with a 10.1.5 release or sometime before my next red job! Fingers crossed!

good luck!
best-
-Nat

[Mike Most]

Why does everyone here seem feel that these kind of things are always the “fault” of third parties and not of Red?

[Nat Jencks]

Not a matter of “fault” hopefully, mike I agree this could easily be something wonky with the newest red SDK, but hopefully this thread is about finding a solution to this very specific bug, not assigning vague “fault”. Bmd does a fantastic job of supporting red workflow and hardware and as discussed earlier in the thread the rocket card can certainly be moody and I’m sure it’s no joy to program for it, and a constantly moving target of the red SDK clearly makes things difficult too. That said it does seem clear that something changed in the recent 10.1.4 or earlier point release which broke r3d debayering via GPU or rocket. Whether this is a bug in resolve or in the red SDK is less important to me as an end user than that it get fixed, and the only way that will happen is with further troubleshooting and discussion and feedback to BMD… Which hopefully other folks seeing this problem can provide.