![]() 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. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |