Davinci Resole Fusion M1 Max Painfully Slow

Reduction of the number of pixels. Of course, no less than needed for the desired output resolution.

HI Juan:

What is this reduction in map image?

Don

Hi Don

The original map is 11292x6621 pixels. I resized down to 1920x1126 using affinity photo

Juan

Hi Juan,

Thank you.

Don

Hi Juan,

Thank you.

Don

You're welcome

When I saw that Fusion was only using efficiency cores on m1 Pro, my first thought was - “What if those efficiency cores were busy doing single core low priority background tasks. That would force Resolve to utilise the high power cores for the Fusion job.
Maybe have mail download, and a time machine backup running when you begin your renders. Time machine is notorious for being slow because it defaults to efficiency cores.
And it would not add significant IO load to the ssd to detract from rendering.


Sent from my iPad using Tapatalk

+1 here, Fusion struggles a lot on the M1 Max. Did a test render on a Windows and a M1 Max Mac. The M1 Max struggled and stayed at 0 - 0.5 fps each time it would come across a fusion title. This happens since Resolve 18.1

Running that file on our 16 core Windows PC with a 3090, it is slower than on our M1 Max.

It doesn't appear to be an optimisation issue, as no one here is reporting this particular render to go faster on any Windows machine than on an M1 Max.
On both my Windows and my Macs the CPU is doing very little during the render, so it is not the bottleneck.

It does point to Fusion being slow generally and to this not being the best way to achieve the outcome you are after.

Second that. Fusion is far less optimised than DR.
If I see what Apple's Motion can do on the same hardware, it's very obvious that Fusion is not limited by the hardware. Yes, I know, Motion is not a full-blown compositor, but it does what 90% of editors/graders really need.

+1 here, Fusion struggles a lot on the M1 Max. Did a test render on a Windows and a M1 Max Mac. The M1 Max struggled and stayed at 0 - 0.5 fps each time it would come across a fusion title. This happens since Resolve 18.1

see my experience viewtopic.php?f=21&t=175066&p=921645&hilit=skierevans#p921814

ridiculous slow on a $4000 mac, solution: make what you need to make and export the assets and edit in CapCut Desktop

Fusion is obviously not optimised for Apple silicon as much as DR.

For compositing, Nuke (we tested a prerelease) or Flame are the better solutions, they are getting really good now on Apple silicon. And 3D like Blender is impressive on the M3 line with it's dedicated raytracing units.

If you want the detailed tests, drop me a PM and translate with DeepL.