Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve How do you manage versions between revisions?

  • How do you manage versions between revisions?

    Posted by Drew Lahat on April 30, 2013 at 2:33 am

    I have to use versions in Resolve, and I have to deal with revised edits (EDL/XML/AAF ‘s).
    Besides being obviously convenient, versions are a required when the same take requires separate grades (which happens every time the camera kept rolling but the framing changed significantly). You can use local versions but they suffer from essentially the same workflow limitation.

    Conforming a new edit means that everything reverts back to version 1. What do you do?

    My current workaround is manually copy-and-paste all “beauty” grades to version 1, then copy and paste and keyframe/tracker nodes, then flag all the shots that have version≠1, then filter by that flag and manually go back and forth between the last edit and the new one, and make sure the versions are set correctly. Seems cumbersome and dumb to me. I’m just working with 1-10 minute short form pieces, I shudder to think about doing this for features.

    Is there any better way? Is there any new related features in 9.1 (I’m still on 9.0)? What about the upcoming 10?

    My issue is very similar to this feature request from 2 years ago. I’m missing a “set as beauty grade” option, “set all current grades as beauty grades”, and adding the ability for Resolve to actually analyze the EDL in an attempt to match clip instances and reassign versions to different instances of the same media.

    Sean Ross replied 12 years, 11 months ago 7 Members · 11 Replies
  • 11 Replies
  • Teo Rižnar

    April 30, 2013 at 6:06 am

    Having same problems/ideas how to solve it. But hay I have done it one time on 2h30min feature 🙁

    How to make all current versions as default versions? Would love that feature.

    Color grade reel: https://vimeo.com/15480583
    Cofounder of https://nuframe.si postproduction

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Brandon Thomas

    April 30, 2013 at 6:32 am

    Import new sequence, batch copy, then color trace?

  • Drew Lahat

    April 30, 2013 at 6:44 am

    Except that ColorTrace, too, works only with version 1…

    (I haven’t tried ColorTrace in person yet, but page 265 of the manual promises “During ColorTrace operations, only the default grade is copied from one timeline to another. All other grade versions are ignored.”)

  • Brandon Thomas

    April 30, 2013 at 6:52 am

    It’d be worth attempting to batch copy your timeline, import your new sequence, batch copy the new sequence, then color trace and see if that accomplishes what you need. That way, in theory, every shot has your beauty grade as the local grade. Hopefully Resolve is smart enough to realize you’re using local grades and copies that over to the new timeline?

  • Drew Lahat

    April 30, 2013 at 7:01 am

    Thanks Brandon, I’ll give it a shot tomorrow.

    Found this article that discusses a very similar issue and solution:
    https://vanhurkman.com/wordpress/?p=1086

  • Michael Stirling

    April 30, 2013 at 10:24 am

    Been a while since I’ve done this but yes, if you ‘copy all grades to local’ which is what ‘batch copy’ is now then you can use color trace of the sequence into a new version of the project though you must ‘make local’ (batch unlink) in the new sequence before color tracing or you will still get errors

    Here’s an untried refinement of it which may been even more helpful:

    In v8 I used to sometimes move clips into a new track and mute the main track if I wanted to batch copy or unlink some clips but not others as the batch copy(unlink) only affected the un-muted tracks. IF Resolve v9 still works this way then you MIGHT be able to do this process with flags and filtered views. That way you could flag clips that you knew needed this process awhile grading as you created the versions.

    Michael.

  • Jake Blackstone

    April 30, 2013 at 7:44 pm

    You didn’t mention the camera used. If it’s Red, good luck with that. Colotrace doesn’t copy the metadata. It’s a bug, that I reported a short while ago.
    So, back to the original dilemma. How to manage versions, simply and efficiently?
    How about bringing the whole versions and timeline concept out of 1980s to a year 2013?
    First, we need to get rid of Master Timeline pronto. Don’t need it.
    Create a timeline, using XML, EDL, AAF, take your pick.
    Grade it. Now we need another version of that timeline. Simply create a new copy of graded timeline and name it appropriately. Do the changes to the new timeline, without worrying that the original will get affected.
    Now the good part starts. You get a new edit and a new version of XML, EDL or AAF. Import it as usual and a new window pops up, asking which timeline Resolve should inherent grades from? Pick the appropriate timeline and you’re done. BTW, you still should be able to create a “local” versions of grades of the individual shots on a given timeline, like director’s version, agency, approved etc. Selecting it means it will be rendered and inherited by the new conform.
    Simple…
    And BTW, I’m not reinventing the bicycle, I just simply described the FilmMaster way of managing versions.

  • Brandon Thomas

    May 1, 2013 at 5:15 am

    I often find uses for the Master Timeline, but I do think it’d be incredibly useful to be able to duplicate a timeline or ColorTrace from inside a project.. which adding those two things would essentially get you to the FilmMaster way..

    You can always import the same XML again to get a copy of the sequence, but then you have to verify you have the correct versions applied throughout.. definitely not as graceful.

  • Kevin Cannon

    May 2, 2013 at 4:06 am

    Hi Drew,

    While I’ll second the “copy to local > colortrace to local” approach as the most automated, I like to keep the other remote versions handy (sometimes I’ve kept something useful in the other versions, or have issues with Red Metadata). Unfortunately that means going through the whole project and comparing the version numbers to the old edit.

    To speed that up you can go into the lightbox view of your first edit, enable the info (which puts the version name/number on the thumbnail) and then screen capture the lightbox. That can work as a visual list, Then put that screencap on a second screen or laptop and you can go through relatively quickly.

    KC

    Prehistoric Digital

  • Sean Ross

    June 3, 2013 at 3:58 pm

    My solution is to copy and paste from one timeline to another; I literally go into one timeline, copy all of the elements of that timeline, make a new blank timeline, and then paste into that new timeline. The limitation of this is that Davinci 9 crashes often when I do this on a multi-layered timeline. To fix this, I copy the timeline one video layer at a time. A pain for sure, but all of the color info, including versions works seamlessly. The one thing that doesn’t copy is horizontal and vertical flops.

    Duplicating a timeline would make the most sense; as all of the metadata is right there, and it should just be easy to do. Come on BlackMagic, help me with this!!! I have even tried “create a new timeline with handles”; and it makes a beautiful new timeline, not only does all of my color and version data not come across, but I also have to manually reassign blending modes.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy