Blackmagic Forum

This is my second project I simply cannot seem to export in 4K. This is very frustrating. I am coming from Premiere Pro and I have never had a problem like this using lesser spec'd equipment.

I am new here , so forgive me for not knowing exactly what I should be posting but here are the specs in the deliver window:

Format: quicktime
Codec: h.264
Ecoder: native
network optimization

Resolution: 3840x2160 ultra HD

Quality:
restrict to 80,000 Kb/s

Encoding Profile: Auto
Key Frames: Every 12 frames
Frame reordering

Force sizing to highest quality
Force debayer to highest quality

Bypass re-encode when possible

The project is a :44 second promo that has a lot of stylized fusion effects but I don't see how any limit on these would make any difference.

Thanks in advance for your help. It is much appreciated.

The render stops? You can’t put it in the render queue?
It’s not clear what isn’t working?
Does render to dnxhr work?

The render completes fully however the video is complete garbage and that result differs every time. In this last instance the video was just a fraction of a second and completely black screen.

in regard to your second question: I tried to export via dnxhr (HQ since I am working with 8bit A73) and i received two error messages:

1. Your GPU memory is full (try reducing the timeline resolution or the number of correctors) wtff?
2. Render Job 2 failed as the current clip could not be processed (failed to encode the video frame)

Your GPU is at the lower limit for UHD. Any complex effects and the problems you get are expected behavior.
To be sure it's not something else, just try to set your timeline to HD and try to render.

HD always rendered fine in Davinci (my footage is always 4K) and I have a hard time thinking DaVinci Resolve is not capable of doing something Premiere Pro is capable of doing (I export 4K in premiere with less tech spec). What did I invest $299 in? A lemon? There must be a solution for me, I really don't want to have to go back to premiere. Davinci is far more intuitive with everything else.

Try this, Anthony.

Error message 2 minutes into render:

Your GPU memory is full.
(try reducing the timeline resolution or the number of correctors)

Render job 1 failed as the current clip could not be processed.
(failed to encode the video frame)


Also, I dont have AQ Strength options nor adaptive b-frame option

Yeah, there are some new options in 17. Ignore those you don't have.

Next, try turning off Preferences>User>UI Settings>Stop renders when a frame or clip cannot be processed. Use the same setting I posted and try again.

Is your GPU driver up to date? I'm using 457.30 and have no problem rendering to UHD.

I do have that option turned off already and I am using the same driver as you Charles (457.30)

Alright.

At this point, my best recommendation will be a better GPU I'm afraid.

Jim Simon wrote:Alright.

At this point, my best recommendation will be a better GPU I'm afraid.

I appreciate your feedback regardless Jim. What I am scratching my head about is that Charles Bennett (the gentleman above your comment) is quite literally using the same GPU as I am. Mine is actually faster (and meets minimum requirements) so there has got to be a solution for me within Davinci.

Using the same hardware doesn't mean using the same media and Fusion nodes, which is where I'm speculating your card is failing.

At 1080 resolution, using ProRes instead of H.264, with fewer or different nodes, yours might work just as well as his.

Jim Simon wrote:Using the same hardware doesn't mean using the same media and Fusion nodes, which is where I'm speculating your card is failing.

At 1080 resolution, using ProRes instead of H.264, with fewer or different nodes, yours might work just as well as his.

You might have missed my previous comment about being able to export to 1080 with no problems at all and not having to change ANY parameters to do so.


Just to reiterate, exporting HD vids in Davinci works fine. UHD 4K is where Davinci starts throwing errors.

My clips are HD 50fps h264 in a UHD timeline, and I render to H264 50fps UHD. Clips are graded and there are no Fusion fx in use. These are my render settings. I use a custom resolution for a widescreen picture.

Charles Bennett wrote:My clips are HD 50fps h264 in a UHD timeline, and I render to H264 50fps UHD. Clips are graded and there are no Fusion fx in use. These are my render settings. I use a custom resolution for a widescreen picture.

I appreciate you sharing that Charles. I guess I am a power user but I am disappointed because my specs meet requirements yet I cannot do the things that Davinci sold me on. I really wish the good people at Black Magic could chime in again and help me troubleshoot or at least help me find a way to get a refund.

The one difference between us is that I have three internal SSDs. The system drive and also the one I render to is a 1TB Samsung EVO 860. My source clips are on a 250GB Samsung EVO 860, and the Database is on a small MSATA drive.

Charles Bennett wrote:The one difference between us is that I have three internal SSDs. The system drive and also the one I render to is a 1TB Samsung EVO 860. My source clips are on a 250GB Samsung EVO 860, and the Database is on a small MSATA drive.

My read/write speeds (T7) are twice as fast as yours.

My advice, forget h264 either native or Nvidia with Resolve. h264 encoding is terrible and there have been a few discussions about its lack of everything.

MP4 h265 output via Nvidia has produced results an order of magnitude better IMO. And leave quality to Auto: Best. Anytime I've touched that screwy things happen. Pretty much leave all settings default except for the advanced and subtitle settings. Turn off bypass re-encode as well. Let the encoder use the original footage to produce the final grade just as with the other clips.

Questions:

1. Are you using an OFX plugins or other ResolveSFX on clips?

2. Any Fusion compositions?

3. Is the crash around the same point in the timeline every time?

That being said. You could do the DNxHD render and then re-compress afterwards. That's worked for me too.

You could try to disable and GPU acceleration if your card is as old/underpowered

aglyons wrote:My advice, forget h264 either native or Nvidia with Resolve. h264 encoding is terrible and there have been a few discussions about its lack of everything.

MP4 h265 output via Nvidia has produced results an order of magnitude better IMO. And leave quality to Auto: Best. Anytime I've touched that screwy things happen. Pretty much leave all settings default except for the advanced and subtitle settings. Turn off bypass re-encode as well. Let the encoder use the original footage to produce the final grade just as with the other clips.

Questions:

1. Are you using an OFX plugins or other ResolveSFX on clips?

2. Any Fusion compositions?

3. Is the crash around the same point in the timeline every time?

That being said. You could do the DNxHD render and then re-compress afterwards. That's worked for me too.

You could try to disable and GPU acceleration if your card is as old/underpowered

I appreciate the info about h.265, I will adjust accordingly.

As for your questions, I am only using ResolveFX clips with simple animation points. So in total about 7 clips, total vid is :44 seconds with resolvefx clips applied on every one.

Lastly, I don't recall if its at the same point every time.

The DNXHD render also fails (as noted previously).

tetheranthony wrote:exporting HD vids in Davinci works fine. UHD 4K is where Davinci starts throwing errors.

Exactly my point. Lower the requirements, and it works. Raise them above the card's capabilities, and it fails.

Jim Simon wrote:

tetheranthony wrote:exporting HD vids in Davinci works fine. UHD 4K is where Davinci starts throwing errors.

Exactly my point. Lower the requirements, and it works. Raise them above the card's capabilities, and it fails.

I know what you are saying but we can't pretend this doesn't exist:

Davinci Resolve 17
Minimum system requirements for Windows
Windows 10 Creators Update.
16 GB of system memory. ...
Blackmagic Design Desktop Video 10.4.1 or later.
Integrated GPU or discrete GPU with at least 2GB of VRAM.
GPU which supports OpenCL 1.2 or CUDA 11.
NVIDIA/AMD/Intel GPU Driver version – As required by your GPU.

Another question, which Nvidia driver are you using. Gaming or Studio? Also, latest version?

aglyons wrote:Another question, which Nvidia driver are you using. Gaming or Studio? Also, latest version?

You know , that's a GREAT question and funny you should ask that. About 10 minutes ago I came across an article making a distinction between gaming and studio drivers. I never knew about this and just finished installing so ...fingers crossed. Here's a quote from the article as well as a link to the article for the record:

NVIDIA
The NVIDIA GPU’s listed below will all give you GPU decoding of AVC / H.264 / HEVC media in DaVinci Resolve Studio on Windows. This is a big enough reason alone to purchase Resolve Studio. Make sure you’re using the latest NVIDIA studio drivers [emphasis mine] rather than the gaming drivers.

Nvidia GeForce RTX 3090 24GB
Nvidia GeForce RTX 3080 10GB
Nvidia GeForce RTX 3070 8GB
Nvidia Titan RTX 24GB
Nvidia GeForce RTX 2080 Ti 11GB
Nvidia GeForce RTX 2080 Super 8GB
Nvidia GeForce RTX 2070 Super 8GB
Nvidia GeForce RTX 2060 Super 8GB
Nvidia GeForce RTX 2060 8GB
Nvidia GeForce GTX 1660 Ti 6GB
Nvidia GeForce GTX 1660 Super 6GB
Nvidia GeForce GTX 1660 6GB


Link to full (amazing) article:

https://www.richardlackey.com/davinci-r ... uirements/

After swithcing to Studio driver: No luck it is still behaving the same way.

Sorry, but it's a better GPU then or delivering HD.

Have you tried reducing the render speed on the deliver page? Sometimes I set it very low (under25fps) when I get render errors.

tetheranthony wrote:My read/write speeds (T7) are twice as fast as yours.

the T7 SSD is not designed for large files that need a continuous stream of data.

Peter Cave wrote:Have you tried reducing the render speed on the deliver page? Sometimes I set it very low (under25fps) when I get render errors.

I appreciate the thought. Sadly yielded the same results.

Mark Foster wrote:

tetheranthony wrote:My read/write speeds (T7) are twice as fast as yours.

the T7 SSD is not designed for large files that need a continuous stream of data.

OK, so the drive is USB. Many possible situations going on here. First, yeah the T7 is fast but have you tried moving your source and target off of external drives? USB is great for transferring files not so good to support random access. That and USB drivers are notoriously flakey no matter which brand of hardware you are using. Windows power management also affects USB in odd ways by default. The first thing I do for most of my USB controllers and devices is to disable all Windows power management control.

For productivity systems, I really like to run a debloater on Windows to get rid of all the crapware that's in there taking up resources. Chris Titus has a good one he updates regularly (https://christitus.com/debloat-windows-10-2020/)

If this is your everyday system best not run this won't as you may rely on some things that it will remove breaking your accustomed workflow. Only run this on a fresh install system prior to installing all your productivity software.

The first thing to check is if the render is failing on the same clip near about the same spot. The only way to do this is to watch it like a hawk while it's rendering and note the time the playhead freezes on the render page. Render again and not eh the spot. If it is, then there's something with that clip either the source or a node or an OFX that is causing an issue. Try disabling all nodes and OFX's and try a render. If it crashes again, note the time as before.

Second, move your source files off of the T7 and try a render again. Try the same steps disabling nodes and plugins.

Third pick a different target drive as well. Maybe the target drive has some cluster problems writing to the same spot each time. If you have a drive that you can blow the partition and full reformat then great. It should catch bad sectors and try to remap them during the full format process.

It may not at all be a display card issue but it seems that's all that has been focussed on so far.

Best of luck.

The T7 is usb 3.2 gen2 (c-port) not usb at all and plenty of throughput (the new usb specs add to the confusion lol)

I really appreciate your input but I used to work in IT and I have done 75% of the things you have suggested. What I am left to do now is rebuilt my project and step by step, painfully render and see where it chokes up. I am making an educated guess to stay it will choke as soon as I introduce Resolve FX which sucks and makes Resolve quite the lemon for me but I will definitely report back with my results. I am hoping I can hack around my problem for a solution but I am not holding my breath.

It has been a minute but wanting to post my results in case someone else is coming across my same exact problem in the future.

I was able to find a solution to my problem. It is one of two things or both (but I believe mostly the second solution):

1. dedicated hard drive upgrade -
Samsung (MZ-V7S1T0B/AM) 970 EVO Plus SSD 1TB

2. Maxed my GPU to +95 core clock and +475 Memory Clock.

Error messages are gone.