Upgrade from 18.5b3 to Studio 18.1.4 (Windows)

Hi,

I am newish to DR. I recently upgraded from 18.5b3 to the most recent Studio version 18.1.4. Before upgrading, I made a backup of all my projects by selecting all the projects and then clicking the local Project Library->Backup. Backup ran successfully.

2. I uninstalled DR 18.5b3 and installed Studio 18.1.4. Most of my projects are missing in the initial view. I restored the backed up DB and they are still missing.

3. I uninstalled Studio 18.1.4 and reinstalled 18.5b3 and they reappeared.

4. So I uninstalled 18.5b3 and reinstalled Studio 18.1.4 and they did not reappear before or after restoring the db.

Not sure what I am doing wrong? I would have thought that the projects would move over initially or after the db restore.

Any assistance is greatly appreciated.

Vic

Going from 18.5b3 to 18.1.4 is not an upgrade it is a downgrade. !8.5b3 is a newer version. 18.1.4 was the last full release. If you started your projects in 18.5b3 they are not backwards compatible with 18.1.4.

Thanks for the reply.

After writing the question(s) I reviewed and saw that the versions were going in reverse (hence not an upgrade).

I have now migrated to Studio 18.5b3 and all seems to ok.

I believe making the projects backwards incompatible was a wrong decision. I am also seeking a way to downgrade, since the app is now starting twice as longer than the previous version, and this is just not acceptable. Sadly, I did some progress with one of my projects in 18.5b, and it seems there's no way back now. However I'm glad they at least did not make the whole database incompatible, only a single project...

Always remember to read the release notes before installing a new version.

Read More.jpg (95.72 KiB) Viewed 508 times

Version Compatibility.JPG (40.63 KiB) Viewed 508 times

Always remember to read the release notes before installing a new version.

Read More.jpg

Version Compatibility.JPG

This one I have read fully and was pretty agree with the database entries incompatibility. The one that caught me unexpectedly was that both timeline and project exports would be incompatible too. Hopefully BMD are reading this and they will make an additional effort adding an option to export timeline in a legacy format. For instance, Adobe AE CC23 still have an option to save ae projects in CC18 format.

You can export the timeline as XML, but that'll only contain your editing decisions and some, but by far not all, transitions.

Always remember to read the release notes before installing a new version.

Read More.jpg

Version Compatibility.JPG

This one I have read fully and was pretty agree with the database entries incompatibility. The one that caught me unexpectedly was that both timeline and project exports would be incompatible too. Hopefully BMD are reading this and they will make an additional effort adding an option to export timeline in a legacy format. For instance, Adobe AE CC23 still have an option to save ae projects in CC18 format.

This is why it tells you to backup your database before upgrading, it isn't like File Save As, it is a database, you can't just simply change the structure of the database back to an older one without a LOT of potential pain.

If you have important work in flight, you probably should not be upgrading to BETA software, and if you do decide to take that risk, you need to follow the instructions regarding backups, it is your data, your responsibility.

This is why it tells you to backup your database before upgrading, it isn't like File Save As, it is a database, you can't just simply change the structure of the database back to an older one without a LOT of potential pain.
If you have important work in flight, you probably should not be upgrading to BETA software, and if you do decide to take that risk, you need to follow the instructions regarding backups, it is your data, your responsibility.

I understand complications the database is introducing. The issue is not about the failed backups or some lost job, but the lack of compatibility between Resolve versions. That's why my suggestion for Blackmagic devs was to make an _effort_ with introducing backward compatibility for timeline export. I do not imply this is an easy task. That's just what should be done for a greater user experience. And to my knowledge, they do care about UX a lot.
And of course, I do not perform essential or production work in the beta software. That was my test, and I realized this issue may become a huge pain for future users, who work in mixed environments.

Blackmagic devs was to make an _effort_ with introducing backward compatibility

I don't think that's a good idea, myself. I think it's on us to be knowledgeable about what we're doing (especially when it comes to beta versions), and do it carefully and with forethought.

You can export the timeline as XML, but that'll only contain your editing decisions and some, but by far not all, transitions.

I found that exporting in fcpxmld 1.10 from 18.5 to be able to downgrade to 18.1 retains a lot more information.

True, at least much more than roundtripping from Premiere.
But there'll be no color grades or any of the FX out of DR.