Resolve crashes when Super-scale factor is too high

Resolve 18.1.2 Build 6, Windows 10 Pro 64bit, RTX3090

here's a problem: you set too high a super-scale factor for a clip (example: 4K to 4x on RTX3090) and Davinci crashes in the Nvidia Opengl 64bit driver DLL. Now, whenever you open the project, as the cursor is on the problem clip, Resolve crashes the same way before you can interact with it, making it impossible to fix.

(I get it, 4x on a 4K clip is insane. but you should be able to change it back but you can't because of the crash).

Resolve should catch that this with a recoverable 'GPU is out of memory' error. It sometimes does, but always crashes either way before the user can interact with the project.

if this cannot be reliably caught, then an option to start Resolve with colour grading disabled would be ideal. For example, via right-click on the project 'Start with grades disabled'.

workaround: open another project. disable grades (shift N). now load the problem project (shift 1) and reduce the super resolution factor.

I like the idea of being able to open a project with Fusion and/or Color in Bypass mode. Might be worth a Feature Request.

viewforum.php?f=33

...you set too high a super-scale factor for a clip (example: 4K to 4x on RTX3090) and Davinci crashes in the Nvidia Opengl 64bit driver DLL. Now, whenever you open the project, as the cursor is on the problem clip, Resolve crashes the same way before you can interact with it, making it impossible to fix.

(I get it, 4x on a 4K clip is insane. but you should be able to change it back but you can't because of the crash).

4X scaling of a 4K clip gives you a 16K clip. Even 8K clips tend to give some people trouble, so I'm not at all surprised that this would cause problems. As my doctor always says: "if it hurts when you do that, then don't do it".

If you're desperate to get the project back, this is what I'd try (no guarantees of success, though):

- Create a small project with one clip
- Save the project
- Make a copy of the project and change the clip scaling
- Save the copy
- Use a comparison utility to see how the project files differ. This will help you find where in the project the scaling factor is set.
- Using that knowledge, make a backup of your original project file (just in case) and change the scaling factor.

Projects are stored in a database format, so you may need to use a database front end to make changes to it. Or, with a little luck, you may be able to use something like a hex editor to change one simple number from "4" to 2" or "1".

4X scaling of a 4K clip gives you a 16K clip. Even 8K clips tend to give some people trouble, so I'm not at all surprised that this would cause problems.

figured I try it on my 24GB card.

As my doctor always says: "if it hurts when you do that, then don't do it".

that's the point, with the crash you can't undo it.

If you're desperate to get the project back, this is what I'd try (no guarantees of success, though):

if you look at the end of my original post, I already posted a workaround.

I like the idea of being able to open a project with Fusion and/or Color in Bypass mode. Might be worth a Feature Request.

viewforum.php?f=33

<thumbs up>

Hi George,

could you fix your issue with DaVinci?

Here it crashes also with SuperScale 2x on a ProRes (1080 or others) immediately after pressing "ok" in the clip attributes dialog.

Hi George,

could you fix your issue with DaVinci?

Here it crashes also with SuperScale 2x on a ProRes (1080 or others) immediately after pressing "ok" in the clip attributes dialog.

I've just avoided 4x since then, as it clearly is a VRAM issue (other factors work for me). How much VRAM do you have?

Of course it still shouldn't crash either way, but allow you to undo the setting.

He has no VRAM, George, since the Mac now has unified memory.
@ Christian:
If you have only 16 GB, check the RAM use with the Activity Monitor. But then, I can upscale UHD with 2x without a problem here in 32 GB, so HD shouldn't be a problem even with 16. Might be a different issue. Or do you have only 8 GB?

He has no VRAM, George, since the Mac now has unified memory.

Ah, I know literally nothing about Macs .

He has no VRAM, George, since the Mac now has unified memory.
@ Christian:
If you have only 16 GB, check the RAM use with the Activity Monitor. But then, I can upscale UHD with 2x without a problem here in 32 GB, so HD shouldn't be a problem even with 16. Might be a different issue. Or do you have only 8 GB?

Yes, I have 16GB too.

Yes, I did 2x Upscale to 2k on my Intel-MacBookPro with just 8GB successfully.

Shouldn't the Activity Monitor show the RAM use AFTER I clicked on Deliver to process my video file? DaVinci crashes after I click the "ok" button in the Super-Scale dialog, already.

That shouldn't happen. Please post a log to a cloud service, sat described in the FAQs.

I use 2X Super Scale all the time with HD footage. The last project contained 28 clips all with 2X Super Scale in a UHD timeline. With my GTX 1060 it slows timeline playback to 12 fps rather than 25 but does not crash, and no rendering problems either.

For what its worth my experience is similar to Charles B. HD to 2X Super Scale in 3840 timeline but mine renders in faster than real time even with Voice Isolation + Dialogue Leveler applied. Many projects are in excess of an hour and in multicam without flattening it before rendering. Alienware laptop with Ryzen 7 5800H, RTX 3060 32GB RAM, 2 internal SSDs.

However, the new version of Super Scale called "2x Enhanced" grinds to a halt even for very short single clips so I cannot test that option.

That shouldn't happen. Please post a log to a cloud service, sat described in the FAQs.

I hope this logs give the necessary information.
https://we.tl/t-SAAOTctjqX (WeTransfer)

FYI: my humble laptop needs 2.74 seconds per frame for SuperScale Enhanced from HD to UHD.

Do I have to write someone at the moderation team about that wetransfer-link for the log-files?

I like the idea of being able to open a project with Fusion and/or Color in Bypass mode. Might be worth a Feature Request.

viewforum.php?f=33

Already made a feature request a while ago:

https://forum.blackmagicdesign.com/viewtopic.php?f=33&t=177534

Do I have to write someone at the moderation team about that wetransfer-link for the log-files?

Due to the fact that I posted the log-files, but no one seems to be interested in: How can I point someone from the Blackmagic-Team to these log-files to check for that crash?
Thank you!

If you have Studio, you can contact support directly. For free, you can only hope someone around here has a look at it.
But since you are on a Mac, why not find any old storage you can delete, put a fresh system on it, start from there and install only DR? If it still crashes, something might be wrong with your machine.

I have time to time problem with 1080p timeline. 64GB Ram/ 8BG VRAM

I opened the topic:
viewtopic.php?f=33&t=182341&p=953320
but nobody from Blackmagic reacted so far.