horizontal line in RESOLVE 11 renders

Dear All, I am working with Canon C500 footage (4K) in Resolve 11 on the new Mac Pro. We are having problems with horizontal lines of different colors (1px high) that appear during grading and are output when rendered!

Any advice or any idea what we could do?

Thanks!
Lisa
Ajenjo Cine/ Mexico City

This is a known issue with the GPU's. They seem to have a high failure rate. You'll want to return them to Apple and hopefully get ones that work. A lot of people with the new Mac Pro have this problem.

We did just install Resolve 10 on the same Mac Pro and there are no lines.

Try rendering a few more times, and you'll probably see the glitch again. There are a couple long threads on this board about this problem. If it shows up, it doesn't go away until oyu get new boards form Apple.

Lisa, it is definetly an issue with your GPUs. I also went mad about this issue, as it was rendering fine in FCPX, but only resolve seemed to have the problem.. until I found that Premiere was producing the same artifacts.

Look for the messages on the same topic here, and on Adobe's forum : it is a well known GPU issue, and you can get your cards replaced by Apple.. no other solution !

Hello, i had horizontal lines over picture on playback. I solved it with HDMI splitter with amplifier conneted to output of DeckLink. Maybe that is it.

Well, In France, AppleCare does not recognize this as an hardware issue and will not replace the GPU. They put the blame of this issue on the third party developer, in this case, Blackmagic. There is not unfortunately no official word from Apple about D700 failures and the fact they will replace them. So, this issue is pretty hot right now in France since they clearly refuse to admit the problem and to replace GPUs under warranty.... Quite an unpleasant situation where the end user is the sole victim.... Hope that Blackmagic issues some kind of official statement that helps Applecare understand the situation.

Just as you said: the lines did reappear and we are now trying to get the GPUs replaced. Quite a mess!
Did any of you manage to get replacement under warranty in the US or Mexico???

Thank you all for your comments!

Lisa

Bonjour Jean-philippe, si tu as toujours un "non", dis moi, moi j'ai obtenu un oui... même si l'incompétence d'Apple fait que je n'ai toujours pas de remplacement, j'ai eu un oui.

mail moi et je propose de te mettre en contact avec les "bonnes" personnes.

Hi Pierre-Emmanuel

As of today, still a no from most Apple Authorised Service Centers, so I decided to contact higher management at Apple, and I'm expecting some official answer about that issue. Cases are multiplying, each week a new case appears, so that can no longer stays without a solution.
As of today, we will advise customers that seek Grading Station with DaVinci Resolve to consider PC platform until Apple admits and takes care seriously this issue...

But if you have other contacts, you can indeed send them to me.

Sorry if I can't follow the logic that if the issue only exists in Resolve (here,too btw!) that it's somehow Apple's fault or the GPU. I have not had any issues otherwise or anywhere else in over two years with any of the various machines/GPUs I'm seeing this with, so I don't buy it, sorry.

As far as I'm concerned, this is clearly a Resolve issue. I'd say BMD needs to fess up.

Just rendered some problematic files in Resolve 12b and have not encountered the dreaded glitch. Yet.

If you research the problem, you'll see that there have been people running Windows on Mac Pros and the problem does not surface. Under Mac OSX, the problem happens. It's not hardware, and it's not Resolve... it's OSX. My guess is it's something to do with how the operating system accesses the GPU for processing.

[Rohit Gupta]

Sorry if I can't follow the logic that if the issue only exists in Resolve (here,too btw!) that it's somehow Apple's fault or the GPU. I have not had any issues otherwise or anywhere else in over two years with any of the various machines/GPUs I'm seeing this with, so I don't buy it, sorry.

As far as I'm concerned, this is clearly a Resolve issue. I'd say BMD needs to fess up.

Pretty sure other OpenCL apps which use the GPU heavily see this as well. Here's a thread from another software vendor:

https://forums.adobe.com/thread/1422947 ... 0&tstart=0

Pretty sure other OpenCL apps which use the GPU heavily see this as well.

Presume all you like. But I've now seen this on SIX completely different Macs with six completely different GPUs (2 rMBP, 3 iMacs and an MP) and different versions of OS X, from 10.9 to even 10.11. So use Apple as the cheap scape-goat all you want, but there is no way this isn't BMD's fault, sorry. If it were in fact an exception with a single machine or model or GPU (or even OS version)... maybe. But it clearly isn't.

Especially since none of the aforementioned machines show any type of issue with any other (more!) GPU (yes OpenCL) intensive app, of which there are many. PPro, Motion, FCP X, AE etc. etc., all of which are being used on the listed machines.

Do your homework BMD

Oh and btw: I've now had to resolve (no pun intended) to using AE and Compressor to transcode the exact same 4 and 5K DPX files that are unusable coming from Resolve. And guess what? Exactly... not a single glitch or render error to be seen.

Gee, go figger.

For what it's worth, I've never had a hit in a Resolve render from a Mac Pro, MacBook Pro, or Linux Resolve in the past 4 years. I've never used the trashcan Mac, though. The stories definitely make me not want to buy one yet, even though I do hear they're fast.

Andie, sorry to hear of your issues. I hate to hear stories like that. You mentioned 4k and 5k. Do you have fast enough storage for that? Old computers love DPX, but fast storage greatly increases the performance and reliability. Resolve is much more about real time performance than AE or Compressor. I think that's the key difference there. Hard to compare them. Different beasts. I generally avoid Compressor because of the slowness, but it is less taxing on the system. Maybe try slowing down your Resolve renders to match what your storage or CPU can deliver?

Hey Everyone,

I ran some tests to isolate what was causing the lines, in my case it was a setting. The "Data Levels" setting in the deliver workspace. I tried many different scenarios, and every time I exported something with "Data Levels" set to "Automatic" it produced those lines. Every single time I turned "Data Levels" to "Full" there were NO lines. I'd love to see if anyone else can replicate this success!

You can add the computer I work with to the list as well. The computer is a nMP from 2013 with 32gigs ram and two D700 cards. I am using resolve 12.5. I made sure the video level was checked to full and the problem continued. The video is 1080 with only simple color on it. It seemed like the line was not there at times during a color session but then after I made a tweak it returned. Sorry, I don't remember exactly what circumstances caused it to show up and disapear.

After booting up the computer this morning, I was able to render out a deliverable without the nasty line of nonconformity.

Bob

so I'm running resolve lite 12.5 on my 2013 trashcan. I was having the issues with the horizontal lines on my prores proxy exports (which will go to premier for editing)

I believe I have solved the issue by disabling one of the internal FireGL cards in resolve. under GPU settings, I unchecked one of the cards (I was also working in after effects simultaneously and finding the working memory being impacted by the resolve renders)

At first I was using the 5fps export, but that's awfully slow. So I went up to faster render speeds with one of the GPU's unselected and it appears to be working great.

Hopefully this helps others.

Cheers!

Very interesting that disabling one of the cards appears to fix the issue. What happens if you switch which card is disabled?

The problem was previously though to be either faulty GPUs or heat, but I now wonder if it could be PSU related or possibly the connection between the GPUs that is causing the issue.

Has this problem been solved by Resolve? My guess is it is a problem with dual GPU rendering on OSX when heavy processing takes place and system temperature raises too much.

How do you turn off one GPU? Can someone provide guidelines on how to do so? Inside Resolve or using System Preferenses? ...

Daniel Perez
ONSet color / Workflow Specialist