Blackmagic Forum

Hello,
I've just started using Davinci Resolve 16 and have created a new project. It let me save it the first time to give it a name but now it won't let me. I think I have tried everything: 'Save', 'Save As...', 'Ctrl +S' 'Ctrl+Shift S' and exporting it. I have enabled AutoSave, but only after I realised it wasn't saving.
Any help would be gratefully received.
Kind regards,
Claire DW

Maybe a permission issue on the volume where your database is located?

Thank you for your response. I must admit that I'm not quite sure what it means as I am not very computer literate! If you could tell me where I'd need to look to find out, I'd be very grateful.
Closing the program and re-opening it (I lost some work) seemed to work yesterday and I was able to work again this morning with it saving it. Now, after a couple of hours, it has started again and is refusing to save any new work. I've done the same bit 4 times now! If it were a permission issue, would it be this erratic?
Kind regards,
Claire

I have the same issue every so often. It seems to happen at very random times for me. Just like you said though, Resolve just refuses to save. It doesn't matter what I do. There are no problems with permissions, or full disk drives, and no errors in the log. Closing Resolve and not saving (because clicking save does nothing), it begins to work again. It appears to be a bug in the autosave that somehow gets triggered, because autosave stops functioning when this happens. I had one project where I could trigger it without fail by just changing the color of a text effect. I would be able to work and do whatever on the project and save would work, but as soon as I tried to change the color of that text it would not let me save. I eventually replaced the text clip and could change the color and save again. It really is an extremely frustrating bug, but in my experience so intermittent that it is hard to track down. When people mention it, others just look at us like we are crazy.

The same issue.
It works OK for some time, but after few tasks in Timeline it stops saving.
None of the saving methods works (File-> Save Project or File -> Save Project As or even closing the program and clicking Save in the prompt).
Unfortunatelly 16.2 update didn't solve the issue.

Glad to see I'm not the only one. It also happens every now and then, and I haven't been able to determine the exact sequence of steps that makes it happen, so I'm just careful about saving very often.

I'm using 16.2.0.054 on macOS 10.15.3.

Yeah I'm also somewhat relieved I'm not alone; thought I was losing it. I'm trying to ditch adobe so hard and wanted to finish this project in resolve. Might have to use FCP instead.

For anyone else, I've just ended up losing work, but it was indeed previously saving. I updated to Catalina 10.15.4 this morning. I was able to save, before this OS update. For Resolve, I am on 16.1.2.026.

Lots of fixes in Catalina and between your version and 16.2.1 released today. Can you download and try the new build?

Peter Chamberlain wrote:Lots of fixes in Catalina and between your version and 16.2.1 released today. Can you download and try the new build?

Hi Peter,

It seems to have been fixed, at least with the one way that I could reproduce it almost deterministically: by dragging volume keyframes in an audio clip in the UI. After doing that in 16.2.0.054, it would some times trigger the no-save state, either by moving the keyframe along the time axis, or by increasing or decreasing the volume for a specific keyframe or within two keyframes. This didn't happen all the time, and I think it happened only with an MP3 clip, as opposed to the rest of my clips, which were WAV files, but don't quote me on that.

Anyway, I've tried a few times so far in 16.2.1.017 and it hasn't failed yet. If it does, I'll try to do a screen recording to report it.

Thanks!

HI Everyone,

I updated to newest version 1ž.2.1 and I'm on Cataline. Unfortunately, this bug happened to me for a first time. I haven't save and have a lot of work there.
I'm afraid to close the app.

Is there anything I can do?
This is really frustrating.

Matej

Falllo wrote:HI Everyone,

I updated to newest version 1ž.2.1 and I'm on Cataline. Unfortunately, this bug happened to me for a first time. I haven't save and have a lot of work there.
I'm afraid to close the app.

Is there anything I can do?
This is really frustrating.

Matej

You can always export to a generic format that you can open again, but the eternal recommendation for any software is to save often, and enable an aggresive autosave time in Resolve.

Same issue here, only once however, but lost a lot of work.
Yeah, I know, save more often!

Hello,

i am having the same issues here since the Version 16.2.1 (Studio) . I am running Mac Os Catalina 10.15.4.
It occurs randomly. After it happened, i also have problems working in the timeline, "Undo" and "Redo" is also not working. Nor can i do Project Backups in the "Project Manager".
Yesterday after 1 hr of working it starts saving again...

Hopefully there is gonna be a fix sone.
Thanks in advance
Axeguitar

janoma wrote:

Peter Chamberlain wrote:Lots of fixes in Catalina and between your version and 16.2.1 released today. Can you download and try the new build?

Hi Peter,

It seems to have been fixed, at least with the one way that I could reproduce it almost deterministically: by dragging volume keyframes in an audio clip in the UI. After doing that in 16.2.0.054, it would some times trigger the no-save state, either by moving the keyframe along the time axis, or by increasing or decreasing the volume for a specific keyframe or within two keyframes. This didn't happen all the time, and I think it happened only with an MP3 clip, as opposed to the rest of my clips, which were WAV files, but don't quote me on that.

Anyway, I've tried a few times so far in 16.2.1.017 and it hasn't failed yet. If it does, I'll try to do a screen recording to report it.

Thanks!

The same "no save" bug triggered for me when dragging volume key frames on an audio clip. Undo, redo, save, save as, export project and i'm sure some other functions also became disabled. Luckily didn't loose any work but definitely scary.

On version 16.2.1.017

I'm also experiencing identical behavior. Cannot use "Save," "Save Project As," or any of the "Undo" or "Redo" functionality.

What do we do?

I can't even restart to fix it.

Save happens to me on Catalina 10.15.4 and Resolve 16.2.2.011 - just will not save and therefore won't quit. I'm going to have to risk and force quit.

Permissions issue with the external HDD providing the write path did occur briefly earlier, but it's showing in finder, is perfectly reliable in all other operations and I've saved and output to it from Resolve within the last 10 minutes or so.

I'm having the same issue. Seems to occur after I used keyframes in a .wav file to alter the volume, sliding them up or down but can't be sure that is the exact problem or how it started the problem. Can't save any of my work, cut, paste, export and the timeline won't let me add anything past the 1:00:05:46 mark. It just ends and won't let me add anything past that point... Tried re-doing all my work by starting a new timeline but the issue of not being able to save keeps happening no matter which timeline I try. Auto-save also is not working.

I'm using Catalina 10.15.4 and Davinci Resave 16.2.2.011

Craig, Are you on the App store or BMD web site version?
Can you save as from the project manger?
Did you start a new DB in a drive location that you do not have 'write' rights too?

Hi, also having the same problem in 16.2.2 now and did not run into this with the prior version. I see no error message when I try to Save. The only reason why I know Save isn't working is when I click the X to close out, it asks me to Save and I click Save and nothing happens. If I click the X to close out and choose Don't Save, it closes out.

I wasn't able to Save As either. When I select the File | Save As option, the dialog box never appears.

This issue is still present in v16.2.2.012. running on macOS Mojave v10.14.4, iMac 27-inch 2017.

I can reproduce it almost every time by moving volume keyframes on audio tracks horizontally (forwards or backwards in time). Apparently, bigger edits (moving a keyframe by more seconds to the right or left) has a bigger chance of manifesting the issue.

As a quick workaround for my fellow video editors, I've started editing keyframes by clicking the bottom right of the audio region - that opens up a dedicated interface for managing keyframes. If I move keyframes there, the issue doesn't happen.

sebjur wrote:This issue is still present in v16.2.2.012. running on macOS Mojave v10.14.4, iMac 27-inch 2017.

I can reproduce it almost every time by moving volume keyframes on audio tracks horizontally (forwards or backwards in time). Apparently, bigger edits (moving a keyframe by more seconds to the right or left) has a bigger chance of manifesting the issue.

As a quick workaround for my fellow video editors, I've started editing keyframes by clicking the bottom right of the audio region - that opens up a dedicated interface for managing keyframes. If I move keyframes there, the issue doesn't happen.

Thanks for the suggestion! I'll try this too.

sebjur wrote:This issue is still present in v16.2.2.012. running on macOS Mojave v10.14.4, iMac 27-inch 2017.

I can reproduce it almost every time by moving volume keyframes on audio tracks horizontally (forwards or backwards in time). Apparently, bigger edits (moving a keyframe by more seconds to the right or left) has a bigger chance of manifesting the issue.

As a quick workaround for my fellow video editors, I've started editing keyframes by clicking the bottom right of the audio region - that opens up a dedicated interface for managing keyframes. If I move keyframes there, the issue doesn't happen.

Thanks for the tip. Will check it out!

I have the same issue. I moved keyframe points to lower volume of some parts of an audio track and I cannot save. No way, no how. I am running the latest version of Resolve on a Windows 10. This is just FYI, so that maybe this bug can get fixed fast as not being able to save a project is obvious a fatal issue for use of the software.

Yup, I'm another person it is happening too.

Intermittent problem. Latest version of the free edition running on Windows 10.

Does this bug exist on the paid for version?

ianbutty wrote:Yup, I'm another person it is happening too.

Intermittent problem. Latest version of the free edition running on Windows 10.

Does this bug exist on the paid for version?

Yes, Studio version here

pnguyen720 wrote:Yes, Studio version here

Oh, well, I can't use that as a reason to buy the studio version then!

[off topic]
(Part of me wants to buy studio version to support DaVinci, but with my business head on I only pay for upgrades when I actually need them - I've been using DaVinci free for a year now and still haven't found anything I need to do that I can't do in the free version! How do BlackMagic actually make any money! )
[/off topic]

ianbutty wrote:

pnguyen720 wrote:Yes, Studio version here

Oh, well, I can't use that as a reason to buy the studio version then!

[off topic]
(Part of me wants to buy studio version to support DaVinci, but with my business head on I only pay for upgrades when I actually need them - I've been using DaVinci free for a year now and still haven't found anything I need to do that I can't do in the free version! How do BlackMagic actually make any money! )
[/off topic]

Studio works a lot better for H265 and of course, you have 4K export.

Same issue for me! After I've moved volume keyframes to the left or right of an audio track I cannot save anymore.

This is a bug, hope it will be resolved in the next version.
Happens for me on Macbook Pro 16" as well as latest iMac. Using the studio version of Resolve on both.

Hoping for a quick fix. This has happened so many times over the last months.

Same Issue here. I've been experiencing it for at least the last 2 updates. Issues still not solved. It would be nice if some BM Official could address it!
Autosafe also doesn't really help as it also is deactivated with the bug. So unless you notice through some other issues appearing at the same time, you could be working for a while and loose all the work!

I tried also to export the project when it happens to prevent loss, but the export only uses the last saved version and not the current state of the timeline.

When you are using other commands like copy-paste, undo-redo... things like that. You are most likely to notice quite quickly. But when you are doing fine tuning work e.g. mostly trimming and moving timeline clips you might not notice for a long period of time. Thats when this bug really f...s you over!

So, please. Would someone from BM address this issue. We are professionals trying to make a living... and loosing work time constantly would force me to leave the platform again.

Cheers
Chris Bu

I'm having this same issue on a Windows 10 laptop Davinci version 16.2.1.

I'll update my signature with specific system specs.

Please, how do we fix this? This is a critical problem for professional work.

I've been having the same issue intermittently for the past few days. I'm running Davinci Resolve 16.2.0.055 on Windows 10.

Oddly enough, if I get into a situation where Davinci won't save my project, if I toggle "Live Save" to the opposite state (if it was on, turn it off, and vice versa), the issue goes away for a while, and I can save my project like normal.

Reporting back as this happened again with studio version 16.2.2.011, and again it happened while moving keyframes visually with the mouse pointer in the Edit page.

I've been using Resolve more than usual since the last version upgrade, and this is the only time it happened, but I needed to mention it here because there seems to be a way of reproducing the issue with the editing of keyframes as mentioned.

The next time u see this, please generate a diagnostic log, NFO file and post a link here with those and a description of the last 3 things you did prior to the lack of save. I don’t see this so the request it to try to repo.

OMG I wish I had seen this post two days ago. Exact same thing happened to me. I had three timelines that I was trying to embed into a main timeline but every time I tried to save after doing so it wouldn't. I tried a half a dozen things that resulted in an abort of embedding timelines and ended up copying and pasting everything from those three TLs into one big one. I just tried to do it again but it worked. Just throwing this out there as another clue. Sorry I can't remember any other exact details, but I have a shortcut on my desktop now that creates the diag logs.

Peter Chamberlain wrote:The next time u see this, please generate a diagnostic log, NFO file and post a link here with those and a description of the last 3 things you did prior to the lack of save. I don’t see this so the request it to try to repo.

Never done that, but I’ll see how to do it and try to reproduce it with a dummy project that I wouldn’t mind losing. Hopefully I’ll be posting back later.

janoma wrote:Never done that, but I’ll see how to do it and try to reproduce it with a dummy project that I wouldn’t mind losing. Hopefully I’ll be posting back later.

First generate Resolve logs...

Mac OS:
In Finder, select "Go to Folder..." (⇧⌘G by default), type the path /Library/Application Support/Blackmagic Design/DaVinci Resolve/ and hit Enter. Run the CaptureLogs application.

Windows:
Go to C:/Program Files/Blackmagic Design/DaVinci Resolve/ and run CaptureLogs.bat application

Then System logs...

Mac OS:
Go to the Apple logo in the top left hand corner and select "About this Mac" >and click the "System Report" button. In the next window, select "File" then "Save".

Windows:
In the Windows Start menu, type DxDiag and run this application. When open, allow for the progress bar to complete analyzing your system. You will see a "Save All Information" button. Save this text file.
In Windows start menu, open Windows System Information. From the File menu, select Save and save this NFO file.

Thanks for the instructions! I created a dummy project and tried to reproduce it for a while, but didn't manage it. If it happens again during my normal editing, I'll generate the report as requested.

All right, here it is, with a lot of info that will hopefully make you reproduce it.

• Resolve logs:

  DaVinci-Resolve-logs-20200608-185757.tgz

  (463.11 KiB) Downloaded 1249 times

• System report:

  SystemReport.zip

  (376.01 KiB) Downloaded 1044 times

Screen capture showing how I reproduce it:

Just happened again.

Can't tell you what I was doing at the exact point it stopped being able to save, because I had been working for quite a while before I noticed I couldn't save.

I have generated a log file following the instructions above but it is 267Mb which is too large to upload via this form. Please let me know how you would like me to get the file to you.

Ian.

Yep, same here, just noticed for the first time.

I'm a recent FCPX partial convert, and it would do the same thing (you don't "save" in fcpx traditionally, it autosaves after every click and keystroke.)

It seems there's a consistent tell, and IT WAS THE SAME IN FINAL CUT: your undo stops working. I learned the hard way and made a mental note that as soon as undo did nothing, or gave me the "no" OS sound effect, I quit and reopen, because I knew it was no longer saving.

Resolve just now, hit undo and the timeline UI didnt update but playback revealed that the changes were in fact made. This is when the save stopped. Just quitting and reopening now.

Just happened for me, too. Tried to post the Resolve logs but the zipped folder containing them is greater than the forum's 1MB upload limit.

New Resolve 16.2.3 release!

See if it's fixed now.

pnguyen720 wrote:New Resolve 16.2.3 release!

See if it's fixed now.

At least it's not in the release notes. I doubt this would count as a stability improvement, which is the bucket list at the end of each version's notes, but we'll see.

janoma wrote:

pnguyen720 wrote:New Resolve 16.2.3 release!

See if it's fixed now.

At least it's not in the release notes. I doubt this would count as a stability improvement, which is the bucket list at the end of each version's notes, but we'll see.

So I just tested it, because im fighting right now with this bug, and nope, its being very persistent and its making me mad..

Cosmonauta wrote:

janoma wrote:

pnguyen720 wrote:New Resolve 16.2.3 release!

See if it's fixed now.

At least it's not in the release notes. I doubt this would count as a stability improvement, which is the bucket list at the end of each version's notes, but we'll see.

So I just tested it, because im fighting right now with this bug, and nope, its being very persistent and its making me mad..

Still there? Sucks..

Peter Chamberlain wrote:Lots of fixes in Catalina and between your version and 16.2.1 released today. Can you download and try the new build?

Hi everyone, I seem to have had some luck with getting around the bug.

I opened the DaVinci Logs as mentioned above, and found that it had a repeated entry of something containing "Invalid" something something "-100". At which stage I assumed it was referring to one of the recent key frames I created on the audio of one of my clips, which was dragged to the bottom of the track. The second I moved that key frame up a notch, everything returned to normal and my project saved as it should.

I hope this can help the devs with solving the issue permanently.

TL:DR, move any audio keyframes at '-100' up to another value and see if it fixes your issue.

I hoped, BM would fix it with 16.2.3... unfortunately Resolve still refuses to save the project after some audio keyframe manipulation.

I'm a professional video editor mainly working on Avid MC. I bought the Davinci Resolve 16 Studio Version for some testing and I like to work with it on some projects. BUT it's an absolute NO-GO not being able to save your project. Even autosave isn't working in this case - so you might work for hours till you realize that you can't save...
This is realy frustrating - and of course this happens when you are on a deadline.
...so for important, time sensitive projects I can't recommend using Davinci Resolve and I won't use it anymore.

MigaelD wrote:I opened the DaVinci Logs as mentioned above, and found that it had a repeated entry of something containing "Invalid" something something "-100". At which stage I assumed it was referring to one of the recent key frames I created on the audio of one of my clips, which was dragged to the bottom of the track. The second I moved that key frame up a notch, everything returned to normal and my project saved as it should.

I hope this can help the devs with solving the issue permanently.

TL:DR, move any audio keyframes at '-100' up to another value and see if it fixes your issue.

This is really interesting, I'll try this next time it happens to me. Thank you for posting, if this work around works it could save a lot of us a lot of time and save a lot of work. (Not to menention actually saving the projects!).

Please assist by providing system and OS details and generate logs. Post a link here. 16.2.3 had a few changes but it seems some still see this so we’ed like logs to try to repo.

Also a reminder for those who post but can’t see their reply, you need to register with your full real name. Please contact Tony to update your registration.

Peter Chamberlain wrote:Please assist by providing system and OS details and generate logs. Post a link here. 16.2.3 had a few changes but it seems some still see this so we’ed like logs to try to repo.

Also a reminder for those who post but can’t see their reply, you need to register with your full real name. Please contact Tony to update your registration.

If you look back through the thread I tried to suply a log but it was too large to upload via the forum. No one replied to say how I should suply it. I think there was someone else who had the same problem.

If you let me know how to send I will regenerate the log if/when the problem happens again.