I've built a few workarounds for live save limitations.
These are more safety mechanisms, and while not incredibly slow, are still not the same as simply reverting to the last save, as if live save wasn't on.
All of these workarounds are for temporary use while working in a project, not for archival or project distribution. They all work by simply copying the project folder and .db file to backup folders. I then have a "restore" disk database that is empty or contains the last project I restored, that I can use to load the last saved project (from my built auto-save macro backup folders described below).
These all use Keyboard Maestro and Applescript. The Applescripts are simple, and I'm sure could be converted to python or other PC solutions. I don't know if KM works on Linux.
1. This is my autosave save macro. You can set the frequency and file paths. It's set to an internal drive bu folder, external drive bu folder, and a cloud bu folder. There is no limit to back up frequency and no limits on how many back ups you want to keep in a folder. However, in general, if you are using other KM macros, you don't want background macros firing all the time. I'd say 3-5 minutes is your max. It doesn't seem to interrupt Resolve, it's just if another KM macro fires and has conflicting action you might get something wierd. I haven't run into this yet.
Right now it's just time of day, and frequency, but I'd like to add that it only starts when Resolve is launched.
It runs in the background, and doesn't require a trigger.
https://drive.google.com/file/d/12YjuHxkEugW08h1PoCtS7kBkH2o2R7S0/view?usp=sharing2. This is restore macro. It clears a temporary "restore" diskdata by moving all projects to a temporary folder, then moves the latest saved project into the "restore" database folder. You can then simply click on the restore database back in Resolve, and your last saved project is there. I would then copy your timeline, dup your project, or in someway get your work back to the database of your original project.
In the case of defeating live save, you could either create a folder you save to independently of resolve, or adjust an Applescript or KM macro action to choose the second to last folder saved.
Applescript:
https://drive.google.com/file/d/1dtTkfpL8cadPHXwPKB1sneB3_azQ0TTy/view?usp=sharingHere is a video of the project restore in action. You can see in the video that even when Resolve is open and the "restore" disk database is open, it doesn't crash or care, when I swap project folders. However, it's best to click into another database, and click back to the "restore" database, or in some way let the database scan again before opening the project.
Sample restore video:
https://drive.google.com/file/d/1t-Q5lZ07d8bq987uND_OvG6pm1neBW9f/view?usp=sharingThis macro needs a trigger. I've assigned it to one button on an xKeys.
https://drive.google.com/file/d/1kiduAfemxq1Mnbo5apBhoiqtwiSuqAE-/view?usp=sharing3. This is a way to back up the project just before rippling a color grade change.
I wanted a way to press one button to both backup the project and then ripple a color grade change. The great part of the macro, is that Keyboard Maestro is actually handling the project save, so the macro waits until the save function is complete, before moving on the ripple action. Just never wanted to forgot to save before rippling.
This macro needs a trigger, I assigned it to an xKeys button.
https://drive.google.com/file/d/1n0Sbqvxu4ruVs7TzEvwmxKNgLCSjZ9cM/view?usp=sharing
Windows 10, Latest DR, GB TRX40, AMD 3970X, 2xRTX Titan, 128 Gb RAM, PCIe 4.0 SSD (boot), PCIe 4.0 SSD Raid 0 (cache) 14Gb/s, BM 4K, Raid 5 3.3Gb/s (storage). Mac 2019, OWC raid 0 (cache) 6GB/s, AMD MPX Pro Vega II, 256 GB RAM, 1Gb/s storage.