No warning if you are opening an older session

I would love to have any warning that I can´t go back to 18.6 when i save a session once in 19.

Agreed that a warning that the project will be converted would be helpful.

Well there is this in the release notes.

Well there is this in the release notes.

Understood. Are you suggesting that the solution to the OP is to read the documentation, Charles?

Reading documentation is for cowards

Well there is this in the release notes.

Thanks Charles! To do that is a good idea with every update and I usually do that and have system backups anyway.

But I still think it would be a great feature during beta to just have one popup that tells you when opening a project from an older stable version.

Or the enlightened.

Beta or no, you should ALWAYS backup Libraries and Projects before an update, ideally to two locations with at least one of then off the system.

Doing that kind of obviates the need for any warnings, I think. You just assume things will go sideways, and prepare!

Warnings are particularly important for new users. A warning would clearly help new users in this case.

The warning isn’t for users like you Jim.

Beta or no, you should ALWAYS backup Libraries and Projects before an update, ideally to two locations with at least one of then off the system.

Doing that kind of obviates the need for any warnings, I think. You just assume things will go sideways, and prepare!

And assume every user comes to forum to read this advice, so it shouldn’t be mentioned in docs nor in software itself?

Then I guess they could also remove all tooltips, messages, warnings, maybe whole documentation while at it, as all of it is either known (gee, get some training) or mentioned in the forum already.

I'm trying to recall a case where a software package silently updates a project without warning the user. In fact, most will automatically duplicate the project to save with the new version schema in order to preserve the original project - and of course the user is notified via some sort of meaningful dialog. One might argue that this goes overboard in protecting the user from misadventure but I would say that it is closer to standard practice than the current approach employed in Resolve 19b1.

Warnings are particularly important for new users.

Slight rephrase.

"...important for ignorant users..."

Possibly. But man, trying to solve willful ignorance with programming can be one hell of a rabbit hole, don't you think?

Jesus, are you stuck in the 60s where man hours were a lot cheaper than computer hours? Software should be helpful and pleasant to use, not a torture device by design which screws you over and laughs when you look at it wrong.

It was there for a long time (the warning)...

Jesus, are you stuck in the 60s where man hours were a lot cheaper than computer hours? Software should be helpful and pleasant to use, not a torture device by design which screws you over and laughs when you look at it wrong.

Torture devices for the modern age: Avid, Premiere, FCPX & Resolve.
None of these are "helpful and pleasant to use".

FCP7 how I miss thee