These paragraphs are discussing backing up both project files and databases, so when he emphasized in italics that one must always leave the original intact and untouched, I assumed he was still talking about these back-ups, which are also “original” files. The key is to always leaving the original intact and untouched.
Decide what you’re going to do with existing projects and databasesĪre you going to upgrade an existing Database, with existing projects? If so, then export that database and NEVER upgrade the original database. My initial confusion came, I realize now, by misreading these two paragraphs:Ī. I think I understand a lot more of what he’s saying now, but still a few questions remain. Since I posted my original questions I’ve been reading a bit more and re-reading Inhofer’s article “Guide To Safely Upgrading To DaVinci Resolve 15 (and beyond)” (which I quoted in my original post and which has been mentioned in this thread). until i do I’m going to be too nerveous to upgrade to 15. So here’s hoping someone can help me understand all this. Equally I can’t understand why and in what way an imported project file or database would not necessarily be reconfigured within 15, yet Inhoffer even places in italic his admonition to “always leave the original intact and untouched.” In what he says I can’t get the link he’s making between that exported database and the creation of the database in 15.
The key is to always leaving the original intact and untouched. And then NEVER upgrade the original project! You will only ever import that exported version of the project, always leaving the original intact and untouched.Īre you going to upgrade an existing Database, with existing projects? If so, then export that database and NEVER upgrade the original database. Yet, my remembered experience with 14 is that when it was installed it didn’t retain and upgrade the old 12.5 database.Īnd why do so many things I’ve read (primarily a long piece by Patrick Inhoffer) emphasize the impotance of exporting and backing up both database and project files? Is this simply as a safely measure in case something screws up when upgrading to 15? Inhoffer says:Īre you going to upgrade active or recent projects? If so, then before upgrading you need to export those projects. Some things I’ve read seem to say that when 15 is uploaded it will say “would you like to up-grade your database”, and that when you select this your 14 database will be upgraded and your 14 projects will now become active that is, you don’t have to import the old database as part of this process. Where I seem to be getting mixed messages is on what happens next. This time I’ve done a back-up of my 14 datbase and have exported all my individual project files.
My memory is that when I upgraded from 12.5 to 14 I failed to make a database back-up and lost all those projects. I’ve been reading as much as I can on the process of upgrading but still find myself with a few questions.
0 kommentar(er)
