"Auto-saving" dialogue shouldn't interrupt what I'm doing

A small gripe, for sure, but makes more sense to fix than leave it be!

Currently the "auto-saving" dialogue box interrupts things like: viewing a context (right-click) menu, and as I discovered tonight: even a Change clip speed dialogue box!

+1

This has been requested thousands of times to BMD.

Batch processes are urgent, including stabilization, Deliver page rendering, etc without compromising the system speed nor the GUI.

A good example is DVR Smart Render Cache, which work in background seamlessly performing a complex render process without interfiering the GUI nor the system performace.

+1 it should inform that it's autosaving via the area next to your project name instead of interrupting you with a dialogue box.

This got so annoying I ended up turning off Project Backups. I find Live Save plus manual backups to be sufficient.

+1 This has been asked to BMD since a long time ago. We have much expectation on DVR 17, not beacuse the new features, but for dozens of usability bug fixes that have been repeteadly exposed along this forum.

This got so annoying I ended up turning off Project Backups. I find Live Save plus manual backups to be sufficient.

I have to confess I do the same thing, but I often have pretty gigantic projects that take a bit of time to export and/or make backups of. It's not a big deal to me to do it at the end of the day.

I'll add my +1 too

I know that the act of saving takes time, but the dialog is a real pain.

There are only three reasons I can think of that makes this necessary - the first is that the save operation is so intensive that it's better to stop everything while it happens - secondly there's concern that saving to the database could capture an inconsistent state if the user is able to alter the state in the middle of a save (for instance if a clip is deleted and references to it haven't yet been updated) - thirdly, the software is spidery in nature and it's just safer and easier to stop any work while saving.

I suspect a combination of 2 and 3.

+1

+1x100

+1
It always shows up when I'm doing delicate things like moving points in rotoscoping.
It could inform you with a small bar in the GUI, that would be great.

What I find more annoying is that the application freezes and it can be a couple minutes before the auto-save dialog box even appears midway through it's save. Then there is really no rhyme or reason to the length of time it takes. It can be very long, especially the first save of a day, then fast on several saves. Then it will hang for long periods even when the complexity of the project, timelines, etc. hasn't changed that much. I experience this on windows and linux machines.

Another VERY annoying bug is that after changing focus to other applications then returning, Resolve will only show dialog boxes behind the main UI making it impossible to work and forcing a restart of the application.

Same - Autosave should be in the background and not interrupt work OR steal my pointer focus.

Auto-save just caused DR to lock. Stuck at 35%. So closing by task mgr.

I don't think you can continue to work when the save kicks in, you might messing up the database...

It is annoying that the little GUI shows up several seconds after the app froze...

Bump

Currently, I can't just right-click to change a clip color.

I have to right-click to open up the menu, wait for Resolve to close my menu by autosaving, then right-click again to go back to what I was doing.

+1


Sent from my iPhone using Tapatalk

+1

Just showing a message in a status bar or something should be enough. If the program can't really do nothing at that exact moment, just let the user do whatever he/she wants, remember it and let's really apply it when the autosaving is done.

I think not breaking the workflow is always welcome, even if it's just a little thing.

+1 not only to Autosave, but to those tasks below interrupt our workflow severely:

- all kind of "Analyse" (stabilization, lens correction, tracking, FX analysis)
- All kind of renders (generating proxies from media pool, optimize files, delivery page)

On those waiting times of our paid time is when we visit this forum

I will appreciate a lot if BMD can develop a way to run tasks on the background, like FCPX or Premiere do.

Ideally they should be batched as an option in case we run it from our laptop with battery, we can wait to plug it to mains. Or it can go straight on the background without batches, if our hardware is capable to handle that. Then set CPU/GPU priority to put GPU/CPU power on the GUI or on the background tasks.

Hey look what's coming up in a new Reaper update...

+ Auto save: do not process auto-save during mouse edits