Dealing With Timecode : When The Rushes And Proxies Don't Match

Dealing With Timecode : When The Rushes And Proxies Don’t Match

January 27, 2014

When the rushes and Proxies don't match due to lack of timecode conforming in Resolve can be a nightmare. Here's how I approach that subject

Dealing With Timecode : When The Rushes And Proxies Don’t Match

The worst thing that can happen when time is against you is that when you try and conform a job. You click to load the XML and nothing relinks at all. This can be for many reasons but I find more often than not these are always timecode based. Then you have that fear inducing moment when you look at the EDL and realise all the timecodes are 00:00:00:00 and your camera rushes have the correct timecode.

This insight focuses on the issue of when media has been badly or mis-transcoded and the timecode tracks are either wrong or don’t exist.

Obviously the first plan of action would be to call the editor and see if it can be worked out on their end but if the editor is unavailable or you simply don’t have enough time to get your timeline resupplied then this insight is for you. I used to eye-match edits that had issues like this but I found that trying to emulate the error with the Proxy files used in the edit has given me much quicker and easier fixes.

Check out the video below to find out more!

– Dan

Member Content

Sorry... the rest of this content is for members only. You'll need to login or Join Now to continue (we hope you do!).

Need more information about our memberships? Click to learn more.

Membership options
Member Login

Are you using our app? For the best experience, please login using the app's launch screen

1,200+ Tutorials, Articles, and Webinars To Explore

Get 7-day access to our library of over 1,200+ tutorials - for $5!
Do you like what you see? Maintain access for less than $5 per month.

Start Your Test Drive!