Sun Dec 05, 2021 6:30 pm
Yeah, it's because Resolve is designed from the ground up to use a database as it's storage mechanism - this is because it's intended for large scale use where several people might be working on different aspects of a project at the same time. The database allows concurrent use by enforcing access locking and consistency across the different resources in a project.
A ".DRP" file is a kind of "frozen" stand-alone version of a project that's been exported from the database. The reason you can't just fire Resolve up from it is that while Resolve can understand the ".DRP" file contents, double-clicking the file doesn't give it any information about which database Resolve should be using as it's live store. And without the database, Resolve can't do anything.
What you need to do is just run Resolve, select the database you want to use, and then import the DRP file into the database. To do this, right-click in the right-hand part of the project manager window (the part that shows thumbnails of the projects) and select "Import Project". Once you've imported it into the database you can open it in Resolve.
DR Studio 18.6.4 Build 6, Win10Pro x64 22H2/19045.3570
Asus C246 Pro Motherboard, Xeon E-2278G@3.4GHz, 64GB ECC RAM
GeForce 3060 12GB, "Studio" driver 512.15
OS,Library: 1TB NVMe SSD - Project,Cache: 1TB NVMe SSD