Resolve 18b1/b2 - Not Able To Save

Working on some small projects and after a while, I am not able to save. Cmd+S and the file menu do nothing, nor does clicking 'Save' on the dialog that appears when I try to quit Resolve.

I think it may have something to do with AudioUnits but I'm not sure yet.

MacBook Pro 16", M1 Max

Does changing application focus change behaviour? i.e. Focus Finder and refocus Resolve.

Working on some small projects and after a while, I am not able to save. Cmd+S and the file menu do nothing, nor does clicking 'Save' on the dialog that appears when I try to quit Resolve.

I think it may have something to do with AudioUnits but I'm not sure yet.

MacBook Pro 16", M1 Max

Check if you have enough free space on drive with db on it.

Does changing application focus change behaviour? i.e. Focus Finder and refocus Resolve.

It does not.

Working on some small projects and after a while, I am not able to save. Cmd+S and the file menu do nothing, nor does clicking 'Save' on the dialog that appears when I try to quit Resolve.

I think it may have something to do with AudioUnits but I'm not sure yet.

MacBook Pro 16", M1 Max

Check if you have enough free space on drive with db on it.

I'm editing off the one and only internal SSD, and I have 1.46 TB free.

[Rohit Gupta]

Can you grab a log and post when you are seeing the problem?

The log archive that Resolve generated is 1.4 MB, which exceeds the forum's 1 MiB limit. Is there an email address I can email it to?

Alternatively, I have uploaded it to Wormhole: https://wormhole.app/QOpY3#WNwXfANlql-wOBF_4RWXwg

In this instance, my suspicion about AudioUnits is seeming more likely. The last version of the project that DID save was when I had adjusted the channel strip parameters just before I added my first AudioUnit.

Hopefully there's a b3 release tonight that fixes this but here's some more info:
I'm like 99.9% sure this has to do with iZotope's AudioUnits. When I add RX 9 I'm not able to save, but if I remove it and wait a few minutes it often recovers and I'm able to save. Sometimes this can take up to 10 minutes but almost always works.

Hopefully there's a b3 release tonight that fixes this but here's some more info:
I'm like 99.9% sure this has to do with iZotope's AudioUnits. When I add RX 9 I'm not able to save, but if I remove it and wait a few minutes it often recovers and I'm able to save. Sometimes this can take up to 10 minutes but almost always works.

This is a longstanding issue so don't expect it to be solved quickly. The observations people have made are that it does seem to be triggered by something related to audio keyframes.

The workaround which has always solved it for me is to switch to another timeline and then back to the one that you were working on. Create a new timeline if you only have one.

Hopefully there's a b3 release tonight that fixes this but here's some more info:
I'm like 99.9% sure this has to do with iZotope's AudioUnits. When I add RX 9 I'm not able to save, but if I remove it and wait a few minutes it often recovers and I'm able to save. Sometimes this can take up to 10 minutes but almost always works.

This is a longstanding issue so don't expect it to be solved quickly. The observations people have made are that it does seem to be triggered by something related to audio keyframes.

The workaround which has always solved it for me is to switch to another timeline and then back to the one that you were working on. Create a new timeline if you only have one.

Thanks for the tip! I'll give it a go.

[Peter Chamberlain]

the logs are missing from that link

Hopefully there's a b3 release tonight that fixes this but here's some more info:
I'm like 99.9% sure this has to do with iZotope's AudioUnits. When I add RX 9 I'm not able to save, but if I remove it and wait a few minutes it often recovers and I'm able to save. Sometimes this can take up to 10 minutes but almost always works.

This is a longstanding issue so don't expect it to be solved quickly. The observations people have made are that it does seem to be triggered by something related to audio keyframes.

The workaround which has always solved it for me is to switch to another timeline and then back to the one that you were working on. Create a new timeline if you only have one.

Thanks! This worked for me!

the logs are missing from that link

I've uploaded new logs: https://1drv.ms/u/s!AnRB88NUtJH7iIc8bmC ... w?e=jE8eoA