![]() ![]() It's enaough to backup, the instal 17 then restore is not necessary since DR17 did it for me. Shrinivas Ramani wrote:The way I understand it, This trade-off is up to the user, but making a backup and testing it before upgrading is a good recommendation for safety. DaVinci Resolve Studio 17 features over 100 GPU and CPU accelerated Resolve FX in categories such as blurs, light effects, noise, image restoration. Yet others backup DRP projects and preset/config files that they later restore on a different machine. Others may skip the separate backup-and-restore in favor of a literal folder copy for a disk database. Invoking the restore as part of this copy gives you that additional piece of mind on the integrity of the backup.īased on workflow, people may approach the first two steps (backup and restore) differently, using Resolve's tools, using postegreSQL or a clone-and-check process away from their main machine. It’s why when you buy a Pocket Cinema Camera 4K, you might get a box promoting DaVinci Resolve 16 when we’re on 17 and some resellers will even still have stock from when it was version 12 or 14. The exact procedure depends on your workflow, but the main take-away is that if you have three copies of your data at the time of upgrade - one for upgrading to v17, one still compatible with v16 in the off chance you need to fall back to a v16 build, and a separate distinct backup file in case you end up upgrading both or rendering one corrupt on one of those rare occasions. See, DaVinci Resolve doesn’t have a subscription, you pay the 300 once and you own it forever, including future versions. Upgrade one of the two copies on the first startup of v17. ![]() back up > restore a copy of the v16 database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |