A little background:
I have been working on a remaster of an indie feature film shot decades ago in SD for almost three years now. Around 800 clips, shot on two cameras, some very long takes (like 8 min.)
The source footage is a progressive 4:3 23.976p packed into 29.97 interlaced with synced timecode.
I got the edit as Premiere Pro project (16:9 23.976p), the clips got a 3:2 pulldown treatment and cropped at the top & bottom.
Later on (already in the middle of the project) I decided to move the project over to Resolve, for its much better color grading abilities. Export via FCP XML. -> Resolve 17.4.6
Only after a while a realized that the pulldown settings did not translate over to Resolve and while Premiere Pro does a very good job to auto recognized the correct pattern, Resolve has no auto feature at all. So I had to sit through hundreds of clips and test through A/B/C/D/E patterns - and the worst: no preview for the settings. That means open the clip attributes, change the pattern, close the window, check if it is the correct pattern. If not, rinse and repeat. That means a few thousand times to go through this, while in After Effects for example it gets this right in 98% of all clips.
Well, ok then. Super easy, barely an inconvenience...
The next trap was that all the new remastered clips have not retained their timecode. Which makes it impossible to easily exchange and re-link.
So after importing the HD 23.976 clip to Resolve I set the timecode start to the same as the SD clip.
Only to find out that because of the 3:2 pulldown the timecode you retrieve from the SD clip does not match the timecode from the HD clip, because Resolve shows me a 23.976 timecode but based on the 29.97 timecode (or smthng like that).
Well, ok then. Super easy, barely an inconvenience...
Position playhead at the IN point of the source clip. Press F for Match Frame.
Switch from timecode to frames in the source viewer.
Only to find out that "Copy Timecode" does not work when this is set to show frame #
So I have to memorize the frame #
Then I open the HD clip in the source viewer and enter that frame #
Now with the source clip on the timeline still selected, I can initiate a replace command.
That does the job.
So to reduce the manual steps for this I started to create a Lua script.
But it seems there is no way in the API for Resolve 17.4.6 to correctly readout the timecode of the IN point of clip in the timeline. I only get the timecode from the playhead at its current position.
The release notes for DVR 19.02 said:
• Scripting API support to get and set per-clip custom metadata.
• Scripting API support to get and set source start and end frames.
• Scripting API support to get and set source start and end timecode.
So it looks like that I am stuck with my script as long as I am on DVR 17.4.6 - is that a correct assumption or is there any known workaround?
I have been working on a remaster of an indie feature film shot decades ago in SD for almost three years now. Around 800 clips, shot on two cameras, some very long takes (like 8 min.)
The source footage is a progressive 4:3 23.976p packed into 29.97 interlaced with synced timecode.
I got the edit as Premiere Pro project (16:9 23.976p), the clips got a 3:2 pulldown treatment and cropped at the top & bottom.
Later on (already in the middle of the project) I decided to move the project over to Resolve, for its much better color grading abilities. Export via FCP XML. -> Resolve 17.4.6
Only after a while a realized that the pulldown settings did not translate over to Resolve and while Premiere Pro does a very good job to auto recognized the correct pattern, Resolve has no auto feature at all. So I had to sit through hundreds of clips and test through A/B/C/D/E patterns - and the worst: no preview for the settings. That means open the clip attributes, change the pattern, close the window, check if it is the correct pattern. If not, rinse and repeat. That means a few thousand times to go through this, while in After Effects for example it gets this right in 98% of all clips.
Well, ok then. Super easy, barely an inconvenience...
The next trap was that all the new remastered clips have not retained their timecode. Which makes it impossible to easily exchange and re-link.
So after importing the HD 23.976 clip to Resolve I set the timecode start to the same as the SD clip.
Only to find out that because of the 3:2 pulldown the timecode you retrieve from the SD clip does not match the timecode from the HD clip, because Resolve shows me a 23.976 timecode but based on the 29.97 timecode (or smthng like that).
Well, ok then. Super easy, barely an inconvenience...
Position playhead at the IN point of the source clip. Press F for Match Frame.
Switch from timecode to frames in the source viewer.
Only to find out that "Copy Timecode" does not work when this is set to show frame #
So I have to memorize the frame #
Then I open the HD clip in the source viewer and enter that frame #
Now with the source clip on the timeline still selected, I can initiate a replace command.
That does the job.
So to reduce the manual steps for this I started to create a Lua script.
But it seems there is no way in the API for Resolve 17.4.6 to correctly readout the timecode of the IN point of clip in the timeline. I only get the timecode from the playhead at its current position.
- Code: Select all
item:GetStart()
The release notes for DVR 19.02 said:
• Scripting API support to get and set per-clip custom metadata.
• Scripting API support to get and set source start and end frames.
• Scripting API support to get and set source start and end timecode.
So it looks like that I am stuck with my script as long as I am on DVR 17.4.6 - is that a correct assumption or is there any known workaround?
Saying "Thx for help!" is not a crime.
--------------------------------
Robert Niessner
LAUFBILDkommission
Graz / Austria
--------------------------------
Blackmagic Camera Blog (German):
http://laufbildkommission.wordpress.com
Read the blog in English via Google Translate:
http://tinyurl.com/pjf6a3m
--------------------------------
Robert Niessner
LAUFBILDkommission
Graz / Austria
--------------------------------
Blackmagic Camera Blog (German):
http://laufbildkommission.wordpress.com
Read the blog in English via Google Translate:
http://tinyurl.com/pjf6a3m