Problems with 17.3

Hi there,

I installed Resolve 17.3. on my new M1 MacMini 16GB a few days ago.
While it undoubtedly exports at least 2x faster than it did before on my Intel iMac, there are some major drawbacks I´m experiencing:

1: delivering H.265 files (same project, same timeline, same settings on delivery) – those files are massively large, around 270 MB where before they were less than 50 MB. Tried several times, even with tiny tweaks to the settings,but can´t seem to change the outcome. Annoying thing, did anyone else experiencing this or even has an idea what could be the reason?

2: there is no deliver of a timeline my Intel Mac took longer to work on but delivered without pain that my brandnew M1 machine doesn´t quit with the ubiquitious "app running out of memory" - message, forcing me to quit the application and restart DVR. This has already been addressed in this forum but obviously not been resolved (ooops, no pun intended) yet. Sadly, because this is a major drawback. I have to go back to 17.2.2. and my 6 years old iMac to be able to work properly again.

Is it just me, or does Resolve become better on one hand and buggier on the other with every release?!

kind regards

V.H.

[Peter Chamberlain]

We would need details how to repo your "bugginess" inc crash logs as per the FAQs.
and for running out of memory, that depends on a dozen things inc source clip type and res, timeline res, frame rate, processing tasks, render res..render codec etc..

In my tests, 17.3 on an M1 is far faster than a 6 yr old iMac on 17.2 but im using
ProRes and you may not be, or maybe are using complex processing. Details are valuable.

Hi Peter,

thanks for the quick reply.

I´ll try to reproduce the problems on the M1, put the requested information together and post it to you. Will have to get the ongoing project ready first on my old machine, so please allow me until end of the week to do so.

There is no question about 17.3. on the M1 being faster – it definitely is a looot faster – but that´s no use if at the end it fails delivery. The old iMac takes at least 2,5times to process, but it does.
That memory leak problem has already been addressed in an older post – several people experiencing it.
Yes, a lot of layering(different modes) in the project, but in 2K timeline with some Braw files, some psds and jpgs and otherwise prores and H264 files.

If I set DVR to a max of 11GB memory usage, it sometimes delivers to the end (sometimes fails), but the system keeps telling from around the 75% mark on although that it is taking up around 16GB of mem and I have to force quit it – how is that even possible when set to 11 GB max usage?? What setting can I choose to avoid this? If I reduce the allowed mem for DVR to the 9GB mark it fails to deliver 100% without warning.

BTW: Any ideas on the file size when rendering H.265? ProRes files are produced in "normal" size...

Thank you!

V.H.

I’m still getting memory leaks in 17.3.3

Can you reference how it has been resolved.


Sent from my iPhone using Tapatalk

@David: How did you get 17.3.3?

@Volker: How large are your stills? If you don't need to zoom or pan, make them timeline resolution.
And then, try to export ProRes and do the encoding to H.265 in Handbrake. This has two advantages:

1. It takes load off the machine under DR.
2. It is far more flexible when adjusting size vs quality.

And please remember, the current M1s are entry-level only.

@David: How did you get 17.3.3?

@Volker: How large are your stills? If you don't need to zoom or pan, make them timeline resolution.
And then, try to export ProRes and do the encoding to H.265 in Handbrake. This has two advantages:

1. It takes load off the machine under DR.
2. It is far more flexible when adjusting size vs quality.

And please remember, the current M1s are entry-level only.

Oops. 17.3.1

Still. Is there a way to plug the leaks?


Sent from my iPhone using Tapatalk

[Peter Chamberlain]

Still. Is there a way to plug the leaks?

Sent from my iPhone using Tapatalk

please show how to repo the leaks.. none will be attended too if we cant see them

I will post a snapshot of the iOS warning that comes up and also the activity monitor if I can.

Thanks


Sent from my iPhone using Tapatalk

Maybe this helps?

David

You are asking too much from the poor thing.

You are asking too much from the poor thing.

She is a champ!

Yes, but not in the heavyweight class.