Resolve 17 Disk Image freezing Finder when opened

Hi, I picked up this decent MacBook Air 11" with an i7 (2015) and can edit in Premiere just fine but I picked up Resolve in addition, or at least I tried to.
I downloaded the Mac version, it was a zip so I extracted it, and then opened the resulting .dmg (Disk Image).
Now, this opens a new window (as dmgs usually do), that shows what's inside the DMG, but there is no background (which I think is related) and after opening the mounted disk image from then on will completely freeze Finder and will make "iconservicesagent" a memory hole, as it'll just keep eating RAM until I force quit/relaunch Finder. This has happened before and I now recall why I don't use resolve, I literally can't install it. This has never happened with any other program I have installed at all, this is unique to Resolve as far as I can tell. I can see everything (that I know of) that's in the mounted disk image but I cannot open or use any of it because by the time I see it Finder is off with the wind.

This is the MacBook Air I have: https://everymac.com/systems/apple/macb ... specs.html
It's on Mac OS X 10.14.6 and has 8GB of RAM with a 512GB SSD.

Thank you,
-jaden-

I have the same problem with DaVinci 17.2 dmg.

I have "skipped" the issue mounting dmg from terminal

Code: Select all

hdiutil attach /path/davinci.dmg

then go to /Volumes/mountedImage and copy .pkg file to desktop (or whatever you want). After, I have launched .pkg from UI normally.

Note: There's not the first time that I have this problem with others dmg provided from Blackmagic, but I don't know where is the source of this issue.

this problem is under mojave - not under big sur
wait and it will work.

I'm not sure you'll like what you get once you have installed DR 17.
It'll barely work in a 1280x720 timeline with your footage converted to ProRes. That MB Air is severely underpowered. Having only TB2, even an eGPU won't help you.

this problem is under mojave - not under big sur
wait and it will work.

Maybe, but at least in my case, only I have seen that issue with .dmg from Blackmagic.

What tech details are involved with it? I mean, if definitely is a combination of Mojave/Blackmagic-DMGs, how I can find the source of this problem?

no, this problem is not only related to the blackmagic .dmg

I have encountered the exact problem with installing Davinci Resolve 16.x on Mojave. It was fine when I installed it on an internal SSD drive with Mojave. I cloned this drive to an external drive (before the installation) and encountered this problem when I tried to install the app.

The solution to use command prompt to mount and copy the pkg file works. It hanged when I tried to install immediately after the install; the installation pkg icon was generic. After I restarted, the icon became custom icon and the installation went smoothly.

I'm not sure you'll like what you get once you have installed DR 17.
It'll barely work in a 1280x720 timeline with your footage converted to ProRes. That MB Air is severely underpowered. Having only TB2, even an eGPU won't help you.

At least it would have worked... in theory. We work with what we have.
I now have an M1 Pro 16-inch and an M2 MBP in addition to this MBA, and I usually use those now when I do editing, so I'm not sure if this is still an issue.

This is actually still a problem, on MacOS 10.14.6. It still happens with Resolve 18.1.1.

This is actually still a problem, on MacOS 10.14.6. It still happens with Resolve 18.1.1.

but you are also aware that 18.1.1 no longer supports mojave and therefore
various functions in the program no longer work properly.

I would update in your place by means of OCLP to big sur on the cMP.
on the others you can run big sur nativly.



.

This is actually still a problem, on MacOS 10.14.6. It still happens with Resolve 18.1.1.

but you are also aware that 18.1.1 no longer supports mojave and therefore
various functions in the program no longer work properly.

I would update in your place by means of OCLP to big sur on the cMP.
on the others you can run big sur nativly.



.

Except I would never actually do that, as it would run significantly slower on a new OS, and could no longer run 32-bit applications, which makes it non-viable for me, not to mention I shouldn't have to anyway, this should just not break..
Resolve 16 seems to work fine. If 18 and 17 both are able to install on 10.14, why in the hell would the disk image background break it out of everything?

I'm not sure you'll like what you get once you have installed DR 17.
It'll barely work in a 1280x720 timeline with your footage converted to ProRes. That MB Air is severely underpowered. Having only TB2, even an eGPU won't help you.

At least it would have worked... in theory. We work with what we have.
I now have an M1 Pro 16-inch and an M2 MBP in addition to this MBA, and I usually use those now when I do editing, so I'm not sure if this is still an issue.

I no longer have this MacBook Air, I now have the last Intel i9 MacBook Pro, and a 2013 13" MacBook Pro as my backup machine, which I was stuck with in its lonesome for 3 damn weeks, and I needed to edit sh*t, so I need this fixed before that happens again.
This thing doesn't have as underpowered graphics as the MacBook Air, but they still aren't discrete or great, but they should at least WORK, if the resolve installer DMG didn't crash finder for no reason. Again, this shouldn't even be a problem to begin with.

Also I have no idea what a "cMP" is. I'm assuming here due to context that it basically means MacBook Pro.
Also, I tried to figure out how to use OpenCore, but I couldn't. It's too god damn complicated and no one on the Discord server was any help, they all just made fun of me instead for not knowing stuff. Yea, f*cking hell I don't know some things, but I need to get sh*t done.

This is still a problem, and has happened on MacOS 10.15 and below for me, and I don't think it's that unreasonable to make a dmg that slightly older MacOS versions can read without crashing, for us that simply can't upgrade their OS for one reason or another, some of us are still stuck on 10.14 due to app compatibility as well.