I've read though the documentation and watched some tutorial videos, but with the many export/import project and archive options, still trying to get down the workflow I would like.

The main thing I would like to do is have everything in one folder, load the project in from that folder, and save it back. Then when I am done with the project, move it to a backup hard drive, where I can open it up at a later date if I need to tweak it.

I feel like the program with the Project Manager screen wants to figure all that out for me and place files where it deems best for convenience. It also seems like as soon as I move a project file, all the links break.

Exporting a project archive seems to work a bit better, although I can't seem to double click on one of these project files, it only opens a copy. Unless I always have to import the .dra file from within the program whenever I want to work on it.

What I have done with other video programs is create a folder (a template with a blank project file and empty media folder) and just copy the folder and double click to open it when I want to start a new production. Not sure if I can do that folder based workflow with DR.

Anyway...love all the export and import options..but can't decide which I should be using? Should I stick with .dra archives or some other method?

Thanks!

It all depends on your workflow and type of footage, there is no one size-fits-all. Those who have a central database which is always connected can rely on that if they have a safe backup strategy for that machine.

Archive (.dra) is good for storage of a project when finished for possible later modifications.

Just keeping a .drp and all the media on one external drive works fine for moving projects around on the Mac.
Under Windows you may need to take care that the drive is getting the same letter assigned or you will have to relink your files.

Cache and other temporary stuff can always be reconstructed and don't need to be archived, but take good care of your stills.

Maybe this is helpful too: https://www.dropbox.com/s/9i3x06004w0jp ... d.pdf?dl=0

frankmcma wrote:The main thing I would like to do...

That makes sense when using a program like Premiere Pro, which creates independent project files on the hard drive as a matter of course. I don't think it makes as much sense when using a database program like Resolve. So here's how I do things.

1. Copy the media cards to a backup location as a first step.
2. Copy the media cards to your internal Media drive as a second step.
3. Edit the project.
4. Delete the media from the Media drive. (You already have the backup from step 1.)

Databases are backed up and individual projects are exported to a Dropbox folder for security.

Graphics and music for all projects are imported from a Common folder, which also gets backed up regularly.

To restore a project, all I need to is re-copy the media from the backup location to my Media drive. Everything else is already in place.

So this is what I have done...

Have a dedicated video folder on my HD for DV projects
Opened a blank project, tweaked a few resolution settings, exported it as a project archive .dra
Saved it in the dedicated folder

That's it. Now when I start a new project, I go into the folder, option drag the blank .dra folder and rename it to the new project, drop in any media files, then from within DR import it as a project archive. It's now in my dashboard.

Does this make sense? I think one issue I have it that when I just boot up and create a new project, I have no idea where the project or the media is residing. Can I set the program to the dedicated video folder?

The software has set up a media folder in my macOS movies folder, but this is listed as only storing stills and cache files.

I do appreciate how DV just handles the files to make things easy, I just need a way to save, backup and move project files.

frankmcma wrote:Does this make sense?

To me, no. You're still thinking the old way, which I see as...not the best way...when using a database program like Resolve.

I am the media producer for a company, and if I was in the office (have not been for a year) then yes, absolutely would go database way with a video server. But now, solo workflow in a solo home office, just thinking of ways to make my projects portable, in case of a half-time in each location becoming a possibility. But I will explore your recommendation, so I know all the options available

I like you process. Just one question...

Jim Simon wrote:Databases are backed up and individual projects are exported to a Dropbox folder for security.

The individual projects are .drp files?

And when you say backup databases, do you mean via Resolve, or straight copying DB files or using Postgres?

wfolta wrote:when you say backup databases, do you mean via Resolve

Yes.

wfolta wrote:The individual projects are .drp files?

Yes.

frankmcma wrote:solo workflow in a solo home office

That's how I work, and it was from that perspective that offered the above work flow.

Resolve uses a database. Period. There's no way to use Resolve without one. Given that, the "project file" method of thinking just doesn't work as well, I think.

Jim Simon wrote:So here's how I do things. ...

I've done a little bit of wordsmithing -- I hope it still reflects your approach -- and have adopted your plan.

Jim's backup workflow:

1. Copy the media cards to a permanent backup location!

2. Copy the media cards also to your internal Media drive.

3. Edit the project (using the Internal Media).

4. Back up the database from within Resolve’s Project Manager via the Database sidebar, to a .resolve.backup file.

5. File > Export Project the project as a .drp file to a Dropbox folder.

6. Delete the media from the Media drive. (Already backed up in step 1.)

Graphics and music for all projects are imported from a Common folder, which also gets backed up regularly.

During longer projects, you should regularly back up databases (step 4) and export the project (step 5). Failures don't wait to happen until you're done.

When we say "backup", above, we mean one or more external locations so there is no single point of failure. If you export your database to your internal drive, you do have a backup in case of database corruption or other mistakes, but an internal drive failure or corruption will lose the database and the backup. To take safety to the next level: make another copy to an external drive. But a fire or flood could take out your computer and this drive. So to be industrial-strength safe: have an offsite copy -- either physically moving a hard drive or using something like Dropbox, One Drive, etc.

The media takes up the vast majority of a project’s space, so the rest of the items (music, graphics, timeline, etc) are left in place indefinitely. (They are backed up for safety — disk failure, mistakes, etc — but the originals can generally accumulate over time without taking too much space.)

To restore a project, copy the media from its backup location to the internal Media drive. If only the Media was deleted (step 6), everything else is already in place and you’re good to go.