Blackmagic Forum

Hi,

I know, it doesn't make much sense to try that already.

But workloads during pandemic times allow some research, where I'm interested in. Production OS is still 10.14.6.

Is any (beta) version already known to support BigSur?

I tried 16.2.7 and 16.3.b3.
Both start and the database/project screen appears. If I choose any project, Resolve crashes instantely.
I also tried a fresh database and new project. Same behaviour.

Nobody tries BigSur beta with Resolve?

Installed the latest 11.0.1 beta.
Still the same here - crash after the project window.

I'm not saying this is an issue, only playing with it so far.

If anybody has some ideas, give it to me!

This is not expected. Could you please post a log file so we can check where it might be crashing?

What sort of a Mac are you running this on?

Interesting. I’ve had Big Sur betas on my editing Mac for two months and have not a single issue. I upgraded to 11.0.1 today and did editing, fairlight and simple fusion and the only thing I noticed was getting that pesky error during rendering about a fusion clip couldn’t be rendered. All I did was adjust the length of the fusion clip by 1 frame and it rendered ok. Of course I’ve had that little issue come up from time to time and that trick usually fixes it.

Tried BigNothing a few weeks ago on an older 2013 MBP and Resolve worked without issues.
Do check if its maybe some plugin you have that is exploding. Had similar issues when i had a few audio plugins that did not like Crapalina and cause Resolve during the startup scans to blow up.

Glenn Venghaus wrote:Tried BigNothing a few weeks ago on an older 2013 MBP and Resolve worked without issues.
Do check if its maybe some plugin you have that is exploding. Had similar issues when i had a few audio plugins that did not like Crapalina and cause Resolve during the startup scans to blow up.

How do you REALLY feel about Apple?

sackboydad wrote:

Glenn Venghaus wrote:Tried BigNothing a few weeks ago on an older 2013 MBP and Resolve worked without issues.
Do check if its maybe some plugin you have that is exploding. Had similar issues when i had a few audio plugins that did not like Crapalina and cause Resolve during the startup scans to blow up.

How do you REALLY feel about Apple?

Thats a well guarded secret

( Its a love hate relationship. My house is plastered with dozens of apple devices (native and hacks) and typing this on a new top specced way too expensive MBP16'. But still i also hate them for so many reasons )

no problems with bug shure DP 11.0.1 and DR 16.3b3 on a cMP

EDIT: yesterday no problem - today on my main cMP everytime crash in project window : -(
here i use glenns software

THX for chiming in.

I do use a X299 based Hackintosh, so can't really await support here.
I use the BCC, Filmconvert/Nitrate and several other OFX plugins like Paul Dores OFX collection.

Where do I deactivate/delete them?

Edit: Found the OFX Plugin folder and moved the plug-ins to another place.
Doesn't work.

Here's the crash-log!

Can you check one thing. May be something completely different, but just to exclude this rare bug as cause .
Its very specific to your setup (which i know) and a (reported) old bug with midi feedback loops that has been in DR since V14 (when hui/mcu control was implemented) and never 100% fixed. (where it crashes explosively if it receives certain midi signals during startup/project load)
Can you open the file :
/Users/Erik/Library/Preferences/Blackmagic Design/DaVinci Resolve/Fairlight/System Parameters.xml
Then set the value :
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_ENABLED" value="1"/>
to
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_ENABLED" value="0"/>

If it is already set to 0 you can ignore , but likely if its a copy of your working OS drive you upgraded , it is set.

hi glenn

will look at it tomorrow
is the 10.10.9 still the last version ?

Keep in mind that untill i tell you, so there is no support on BigSur yet for my Resolve edition kits. Waiting for the final to build and release a compatible version.
So stay away from it .
If you want to test Resolve , that is fine of course. The check i gave above is to disable any midi control input into Resolve to make sure that is not a factor. Not sure if that is related to the crashes but as BigSur messes with midi as i already found during some testing , just disable it in Resolve to exclude is as a source of problems when testing.

was only for testing which software is running well and which makes troubles ; -)

my main cMP is back on the mojave drive

Mark Foster wrote:was only for testing which software is running well and which makes troubles ; -)

my main cMP is back on the mojave drive

Mojave is our friend for a long time still i bet.
Dont move unless you absolutely have too, or unless you absolutely require new Mimojis for your production work

i am 62 years old and hate emojis and mimojis ;- )

but do apple support since 1992 and one day the users
will be at the door with their new systems - so i have to test it all.

Seems to be running fine here.

I tend to agree with the macos bashing, overall the whole thing runs better on my Win10 20H2 workstation, & that includes the ability to run 'proper' Nvidia GPUs (unlike the dreadful, overpriced, underpowered AMDs that Apple insists on). Otherwise, Apple breaks everything that comes before in every OS upgrade - hence making Apple users dread the next OS. Very unlike Win where drivers and older apps just continue to chug along, and with two regular Win updates per year, patch Tuesdays etc.

Just sayin ... macos, the most expensive os in the world /'Apple tax' /, you'd need to 'really want it'.

Paul Draper wrote:Seems to be running fine here.

I tend to agree with the macos bashing, overall the whole thing runs better on my Win10 20H2 workstation, & that includes the ability to run 'proper' Nvidia GPUs (unlike the dreadful, overpriced, underpowered AMDs that Apple insists on). Otherwise, Apple breaks everything that comes before in every OS upgrade - hence making Apple users dread the next OS. Very unlike Win where drivers and older apps just continue to chug along, and with two regular Win updates per year, patch Tuesdays etc.

Just sayin ... macos, the most expensive os in the world /'Apple tax' /, you'd need to 'really want it'.

Apple don't insist on AMD GPU. NVidia refuse to support Apple due to a long standing disagreement.

Can we please keep personal OS bashing out of this thread?

THX

Erik Wittbusch wrote:Can we please keep personal OS bashing out of this thread?

THX

+1

Glenn Venghaus wrote:If you want to test Resolve , that is fine of course. The check i gave above is to disable any midi control input into Resolve to make sure that is not a factor. Not sure if that is related to the crashes but as BigSur messes with midi as i already found during some testing , just disable it in Resolve to exclude is as a source of problems when testing.

How can I disable the midi control without actually starting it?

Erik Wittbusch wrote:

Glenn Venghaus wrote:If you want to test Resolve , that is fine of course. The check i gave above is to disable any midi control input into Resolve to make sure that is not a factor. Not sure if that is related to the crashes but as BigSur messes with midi as i already found during some testing , just disable it in Resolve to exclude is as a source of problems when testing.

How can I disable the midi control without actually starting it?

Check my earlier post with the xml file you need to edit.
You can also delete it (or back it up) as contains some fairlight settings , which will then return to default.

Oh gosh...
How blind can one be!

Will test tomorrow.

THX

Confirmed!

The Midi Controller was the issue.
Now it runs just fine!

Thanks!

Tnx for checking. Good to know the bug is still in Resolve since v14
But then again , not many people are directly driving midi into Resolve.

Erik Wittbusch wrote:Confirmed!

The Midi Controller was the issue.
Now it runs just fine!

Thanks!

not for me : -(
click on anything > crash

deinstall, delete all resolve content > start normal
edit the setting and after restart crash after 5 seconds

bug shure 11.0.1 RC (20B5022a)
DR 16b3

Thats is differet and not related.
Just forget about BugSur for now and enjoy your life. There are more important thing to worrie about

Glenn Venghaus wrote:Thats is differet and not related.
Just forget about BugSur for now and enjoy your life. There are more important thing to worrie about

it is only for experimenting - not for working ; -)

Big Sur will be released Thursday November 12, 2020. Not in any hurry to upgrade until we are advised DaVinci Resolve 17b1 or later runs without issues.

rick.lang wrote:Not in any hurry to upgrade until we are advised DaVinci Resolve 17b1 or later runs without issues.

Don't you like a bit of danger in your work?

Some adrenaline is always nice given how predictable one’s day can be during the pandemic. Still I’m perfectly content to learn Resolve 17 on Catalina if there’s any difficulty with Big Sur. I hardly use any plugins so just knowing a ‘basic’ install will work well on the Mac Pro might prompt me to give it a go.

Not sure it I want my Mac to look like an iOS device given the Mac doesn’t have a touch screen. Muscle memory might mean I keep trying to touch the 6K screen like it’s my phone! I actually embarrass myself sometimes already when I’m using one of the girl’s MacBook Pro!

Hahaha i thought i was the only one. I keep cleaning my new MBP 16 screen after i do more and more on my ipad pro lately. Good i am not alone
I never had that on my old 2013 model that i just replaced, but likely the new screens are more alike so more tendency to mistake. Also i use my ipad with a little keyboard which makes the mixups even worse

Thanks, Glenn. “Misery loves company.”

Unfortunately, Resolve doesn't really work here.
It starts without any flaws, but when I try to to something, Resolve crashes and the color circle appears.

This os with every version of Resolve (16.2.7., 16.3b, 17b).

I'm still just experimenting here, but as BigSur has reached its first 11.01 release candidate, it theoretically should work.

Theoreticaly......
Could be anything at this point eg gpu / metal driver changes come to mind that dont like your R7's anymore.
If i have some time i will play with it in the coming weeks myself , but lo prio.

I still fear, that some plug-ins might cuse the issue.
A firend of mine is also testing it the next days.
I will also dive deeper in it the coming days.

THX!

Appreciate your efforts folks. I don’t want to make the move to a new macOS until BMD posts Resolve 17 is compatible either via Rosetta2 or a new ‘universal’ binary app. No rush for me during the pandemic.

While I have the same attitude, Rick, you don't need Rosetta 2 for Big Sur if Resolve is running on Intel hardware.

It'll be a sandbox system for me after a few months have passed.

Running iOS apps on a future Mac might be attractive, though. And, BTW, some great alternatives to Adobe programs are already M1 optimized, namely the whole Affinity series.

Uli, you’re right; I didn’t word my post very well (since I’m not moving to M1 machines for the foreseeable future). I’m really just hoping BMD will provide guidance on moving to Big Sur. I’m not upgrading until then because I no longer have a separate machine or drive I can boot to test things out. Hoping some others on the forum have that capability.

From what I read about Big Sur, it’s treating your computer system differently than previous macOS versions in the name of ensuring your security and data integrity. I probably enjoy those protections already with Catalina on the Mac Pro vía the T2 chip that manages my 8TB internal system drive; so I don’t feel there’s any significant benefit at this time of doing the Big Sur upgrade until apps that I use make it a requirement.

I’m becoming a more cautious person, maybe that’s a psychological side effect of the growing cautious attitude many have during the pandemic that is nearly out of control in some jurisdictions and dramatically growing almost everywhere.

Any idea what makes Resolve freeze?

I also deleted several OFX plugins, but it still doesn't work...

Get the new beta 17.1 for Big Sur (only).

Yes, 13 was a typo.

Uli Plank wrote:Get the new beta 13.1 for Big Sur (only).

I think you mean 17.1 but i believe that is for M1 machines only and not a general big sure release.
But could be wrong

Erik Wittbusch wrote:Any idea what makes Resolve freeze?

I also deleted several OFX plugins, but it still doesn't work...

No idea. Will upgrade my old mbp 15' and test it out today with DR17 beta
Could it be our Radeon Vii's maybe ? As every release has some metal changes etc

I have this issue with every Resolve Version I have.
I also had the issue with older BigSur betas.

Since I deactivated the MIDI thing, it's starting just fine, but I can't do anything
as Resolve freezes with the colorcircle after a few seconds no matter what I do.

Erik Wittbusch wrote:I have this issue with every Resolve Version I have.
I also had the issue with older BigSur betas.

Since I deactivated the MIDI thing, it's starting just fine, but I can't do anything
as Resolve freezes with the colorcircle after a few seconds no matter what I do.

Seems its something local to your system as not related to the Resolve version.
Also just tested Resolve 16 and 17 on my old 15' inch mbp 2013 , which i just installed BigSur on (a fresh install) and both run fine with zero issues on this old machine.

You could try starting with Resolve in OpenCl instead of Metal mode to see if it relates somehow to your GPU's
In older releases you could do that by modifying a local preferences file (config.dat, but the location where that has set has changed and not sure where as when i change to OpenCL that file does not change anymore. BlackMagic can chime in here on how to start in a different GPU mode. At some point there was even a keyboard shortcut you could press during startup but dont remember nor sure if still relevant.

Can you generate a new crash dump and attach so BM (and others) can have a look ?
Also include (zipped) the output of :
log show --predicate '(process == "Resolve") and (eventType == logEvent)' --last 1d

Yeah,

must be related to my system unfortunately.

As I have some time before Resolve hangs up, I switched to open CL and restarted Resolve.
It takes a long time to start, reacts slowly and also hangs after a minute or so. Pretty much the same I'd say.
Also with only 1x GPU activated, still the same behaviour.

It always hangs after a minute, sometimes faster.

Wierd, but the fact that you have some time in resolve before it hangs it is a clue although not sure what though......
One thing comes to mind which takes a bit more time during startup and that is vst/au plugins scanning.
So try removing the audio plugin path from the setting so it wont scan these.
I have had vst's that could blowup resolve in the past

I reinstalled the Desktop Video Driver - same.

I removed the audio plug-in folder and disabled all plug-ins - same.

I totally removed the PlugIn folder from the library - same.

Did you try a different user ? Maybe its you

Glenn Venghaus wrote:Can you generate a new crash dump and attach so BM (and others) can have a look ?
Also include (zipped) the output of :
log show --predicate '(process == "Resolve") and (eventType == logEvent)' --last 1d

This

Glenn, thanks for the successful test of Big Sur with Resolve. That’s encouraging.