Once I make any edits in a project after about 20 minutes, so I don't lose any of my work I Export Project to the internal hard drive and name it that date or as I go along during that date add the number 2 then 3 then 4, etc. I see the word Database but don't mess around with it in fear of deleting something necessary. drp last saved on desktop hard drive or the external hard drive. When I open a Project in DR 17, I usually Browse to the. I'm still learning so many of the much appreciated time-savers in DR. I do the same thing it does by duplicating template folder structures in the Finder, and letting Resolve tokens handle variable filenames. It doesn't look like it would be incompatible with Resolve. It's a little redundant as long as you're good about versioning with timelines and using automatic backups, but it gives me peace-of-mind, and the ability to roll back the project to exactly the state it was in at any point where the client has a reference copy. Next time they hire you, double-click that to get started. drp template, and save this in their client folder. Leave intros, outros, graphics, SFX, etc which don't change, and export the remainder as a. When you've finished your first project for a new client (or your first *resolve* project for an old client), make a copy of the finished state, then delete all of the conditional elements all of the stuff that would change from job-to-job. DRP, they're good for two things: versioning, as I mentioned above, but also project templates. It has more advanced version control and collaborative features.īecause Resolve never saves back into or over top of a. If you're collaborating with other editors on the same network, don't use disk databases. Resolve 17 has Python/Lua scripting on export, so there's potential to automate. drp to the next, the first person should manually move the project file in the database into an subfolder to avoid confusion: call it "old" "expired" "out-of-date" "backup" or whatever. Unfortunately, it's up to the humans in this situation to keep track of the project state when one person passes a. If you're using disk databases and trying to collaborate with other editors or colorists, especially when you're not on the same network, you'll have to use. In the meantime, I use a Finer Action to do that. Unfortunately, you'll have to enter date and time manually until BMD acquiesces to a long-standing feature request. I usually name review candidates YYYYMMDD_HHMM_%ProjectName_%Timeline. If you start typing a percent sign in the name field on the deliver page, a list of candidates will pop up. Resolve can use tokens to name your output, so take advantage of that. Use Timelines to version within a single Project. Use folders in the database to organize clients. If you archive your projects to external, removable media, then you might consider a new database with every archive drive. Make new databases periodically, but not THAT periodically. Haven't looked into Post Haste, but this is what I do: I wondered how other 'rapid turnover' freelancers manage their project naming, structure, databases etc.? I'm always after the fewest clicks and manual tasks when I do this kind of thing. I don't know if I am looking at DaVinci in the right way? I want to replicate the more sequestered model of one-project one-project file, that Premiere uses. Does this sound sensible? I don't (intuitively) want one DB with endless client projects inside it. Each clients template was slightly different.Īm still working with this Post Haste system but manually creating a Davinci DB per project, and importing a project template each time. Auto increment project numbering, default asset creation, and custom folder structures with Post Haste. I whizz through probably 2 projects per week. I am moving from a very robust (IMO) workflow with Premiere, for corporate clients who need a fast turnaround. Looking for freelancer tips for workflows with DaVinci databases and projects.
0 Comments
Leave a Reply. |