Want less intrusive Live Save

It’s great that we now have the option of Live Save to guard against loss of work. Now that it’s there it would be nice to make it less intrusive so it doesn’t distract, causing people to lose their flow and perhaps turn the feature off.

I’m not sure what constraints the database library might impose, but conceptually the save could be staged in-memory which would be fast enough to not interrupt the UI while preserving atomicity, and then written to the database in the background.

Up to dev to see if they can manage this - but it would certainly make the feature more useful, make Resolve feel more responsive, and reduce the likelihood of people disabling Live Save.


Sent from my iPhone using Tapatalk

I’m not sure I follow but live save is not interrupting the UI, unless you mean the automatic project backups.

It’s great that we now have the option of Live Save to guard against loss of work. Now that it’s there it would be nice to make it less intrusive so it doesn’t distract, causing people to lose their flow and perhaps turn the feature off.

I’m not sure what constraints the database library might impose, but conceptually the save could be staged in-memory which would be fast enough to not interrupt the UI while preserving atomicity, and then written to the database in the background.

Up to dev to see if they can manage this - but it would certainly make the feature more useful, make Resolve feel more responsive, and reduce the likelihood of people disabling Live Save.


Sent from my iPhone using Tapatalk

Live save even on my private computer at home does not slow down the system anymore. It did in DR16 but from 17 onwards it became fast enough for uninterupted work.

It’s great that we now have the option of Live Save

Meh. I've had the Live Save option turned on since it was introduced about 5 years ago, Joe... as far as anecdotal evidence goes, I can say it has never caused any issue for me, or at least none that I can recall. I have seen other users posting from time to time that they're experiencing some interruption 'every time I do something' ... and that generally points to 'Live Save' as the culprit, but not because of its design ... it suggests that there's something amiss in their setups, with their installation perhaps, a possible issue with a specific project or a potential database problem. Automatic backups, yes, I'd agree that those can be annoyingly interrupting - a way to handle those as a background process would certainly be appreciated.

Normally, Live Save is entirely unobtrusive. There is never any interruption of work.

On a slow network Live Save to a PostgreSQL server used to be pretty bad. In recent versions they have optimized it significantly. Allowing newer PostgreSQL versions that have much better default settings likely helps as well.

Haven't tested Live Save on a disk database but I assume it's basically seamless.

I'm using livesave successfully on a PostGres installation hosted off-site. It works fine and invisibly over a normal internet connection.

There's definitely times when the database connection holds things up (mainly, loading large, complex smart bins), but even that has gotten markedly better since DR 18 / Postgres 13. But I don't notice lag due to livesave, so I would guess that whatever lag you are seeing is probably due to some other cause.

Normally, Live Save is entirely unobtrusive. There is never any interruption of work.

That's generally my experience as well. Once in a blue moon -- and I mean, once every 3-4 days -- I might be doing something complex and Live Save kicks in, and there's a perceptible delay, like a couple of seconds. And then everything is fine and the system responds again. Happened today with a client, and I turned to him and said, "ah, I was trying to work a little too fast." I can't remember it happening for a week, so it's fine with me.

I think auto-backup (where it's doing an actual incremental backup) does take a little more time, but that's not a feature I use very often. I usually do manual backups at the end of the session, and that generally works for me.