Roman Hankewycz
Forum Replies Created
-
Neither actually. Since the project isn’t for film, the vfx guy gives me back quicktimes. Would that make a difference?
roman hankewycz
harbor film company // colorist -
Right I’m talking about 60i.
Since posting I discovered some of the footage in the source sequence was XDcam and some was prores(HQ). Also I can’t be sure that that my shared storage isn’t a factor in the problem. When I had a moment I did a little test where I transcoded some of the source sequence to prores(HQ) to my internal stripe (instead of shared storage) and that seemed to play back correctly when I created a default session in Resolve. I’ll test more when I get a chance. Thanks for the responses!roman hankewycz
harbor film company // colorist -
Questions about how long conforms will take always make me laugh because clients swear that their projects are well organized and that conforming shouldn’t take as long as you say. Fact is it’s never as easy as they think. Today with so many elements coming together within an edit I feel that each conform brings with it a slew of issues to work through. It just makes me laugh.
roman hankewycz
harbor film company // colorist -
The project I experienced it on was an FCP project. I don’t know what AVID would have done on EDL export. The weird thing is that this is an issue with EDL creation, not FCP nor Resolve. Why doesn’t the EDL record that the TC switches to 00 hour?
Good thing is that these situations don’t happen too often so it’s not a big deal to manually deal with.
Roman -
I hear you but you don’t always have control over the timecode of the media you’re getting. It’s a common practice to shoot with time-of-day TC or to start each shoot day’s TC with a different hour (ie. day one is 01:00:00:00, day two is 02:00:00:00).
The question is when it happens, what do you do?
Roman -
Great point Dwaine.
Actually this is what I’ve resorted to for now. I can create a duplicate of the project by doing “save as,” and thus get a duplicate of my session but this doesn’t seems like a good method.
In terms of organization it’s messy. Having multiple projects floating around is messy and creates room for error in terms of mistakenly continuing with the wrong project.
Also I wonder what extra strain making a duplicate of a project has on the Resolve DB. In my mind you’re also duplicating all the sessions in a project, all grade versions, and all the stills which I’m sure adds up. Instead, duplicating a session within a project would share all of these elements, lightening the load on the DB, but maybe I’m wrong.
Roman -
Vladimir,
Thanks for the response. I’ve looked into these methods but the fact that the grades get switched to the default versions makes them impractical for me.
I’d like to create an exact duplicate of my session to serve as a sort of “back up” before I replace vfx shots, or if I want to grade a scene differently.
Definitely a feature request.
Roman -
Thanks for the reply Illya.
I’m checking out Textwrangler now, however what I was asking about is whether there’s a way to select clips in the Media Pool that are not used by a session so that they could be removed.
So far I haven’t found a way of doing this and I’m pretty sure the function doesn’t exist but it would be a useful option and one I assume would be easy to implement. Maybe a feature request?
Thanks all,
Roman -
I’ve come up with a solution that is pretty cumbersome but works, please let me know if anyone has a cleaner solution.
(1) First, I assume that the editor has been given a project that has all of the available clips in it, or that he has himself imported all of the clips into a project that he’s using. From now on it’s going to be very important that the project versions are kept track of very carefully; this whole thing hinges on the logging work being done on a copy of the project that already has the clips in it (the assistant can’t start his own project, it must be a copy). The assistant will log clips in a copy project, then dump the logged clips into the editor’s project, then make a new copy of the editor’s project when new clips are added, the assistant will log the new ones, dump the new logged clips into the editor’s project, and so on – keeping this organized will be a mini nightmare in itself.
(2) Open the editor’s project and use the save as command to make a new copy (this will enable the changes to ripple back into the editor’s project).
NOTE: the editor also can’t start new projects himself, he has to continue the lineage of the projects by using save as if he wants to archive a project.
(3) Now in the assistant’s version of the project log all of the clips as you normally would: rename the clips, add logging info, notes, etc.
(4) Once all of the clips have been logged, make a new sequence and cut all of the newly logged clips into the project (this is very important, every clip you changed has to exist in a sequence). If there are too many clips to cut into one sequence, make more than one, it doesn’t matter, just as long as each changed clip exists in a sequence. Name these sequences something like “xfer_seq_01_[date]” because you’re going to have to keep track of these.
(5) Now for the merging. Take the assistant’s project to the editor’s system and open both projects side by side. In the assistant’s project, highlight all of the “xfer” sequences and copy them, then paste them into the editor’s project. Immediately you’ll get the Copy Master Clip dialog box (if this doesn’t appear then something is wrong). In this dialog box you want to enable the radio button next to the option The clip you are adding and also check the box at the bottom that says Apply to all clips with clip property conflicts and select Copy Clip. This action should add the “xfer” sequences to the editor’s project and change all of the master clips in that project to match the logging changes.
(6) Now to check everything. Go through his project and check that things have properly changed. Both master clips in the browser and clips within existing sequences should have changed in the editor’s project. Obviously, the clips will not be organized into bins or anything, if you need to you’ll have to sort the newly renamed clips into appropriate bins at this point in the editor’s project. At this point you can delete the “xfer” sequences from the editor’s project as they are no longer needed.
(7) Moving forward. Lets say that since the last version of the assistant’s project that has been worked on, the editor has added new clips to his project that need to be logged. Make a new copy of the editor’s project using the save as command. Open the new project on the assistant’s system, put all of the unlogged clips into a separate bin (to keep them separated) and repeat the steps above.
WARNING: This process will have no affect on subclips that the editor has made, so ask him not to make subclips until the logging has been done. -
Very nice Patrice, I appreciate the tip!
Roman