Skip to main content
heartsnoopy
heartsnoopy
Participant
May 6, 2026
Answered

“DaVinci Resolve and Premiere H.264 Proxy Compatibility Issue – Need Advice”

  • May 6, 2026
  • 6 replies
  • 129 views

Hi everyone, I’ve run into an issue with my workflow and would appreciate some advice.

I created proxies from my original footage in Premiere using H.264 encoding, and then I tried to work with them in DaVinci Resolve for color grading/editing.
However, when I attempted to relink the proxies to the original media, Resolve gives the following error:

“Frame rate and timecode do not match”

I’m wondering:

  1. Is this a mistake on my end during export or relinking?
  2. Or does DaVinci Resolve not support relinking H.264 proxies to original media?

If anyone has experience with this or a workaround, I’d really appreciate your input!

Correct answer heartsnoopy

Hi Kevin,

Thanks for following up. Yes, when I export proxies using H.264, the timecode starts at 00:00:00:00.

I also tried exporting proxies using ProRes, and in this case, the timecode seems to match the original media. However, DaVinci still cannot relink them.

If I import both H.264 and ProRes proxies into DaVinci, it seems that the H.264 proxies have no timecode information, while the ProRes proxies do. So I’m starting to think that this might be a limitation or issue with DaVinci Resolve itself.

Thanks again for your time and help!

6 replies

Uv28171828i8eg
Participant
August 25, 2026

Hey, I’ve run into a very similar Premiere → Resolve proxy workflow issue.

From what you’re describing, the timecode starting at 00:00:00:00 is likely the key problem. If the proxy doesn’t preserve the source clip’s starting timecode/frame rate, Resolve can have trouble matching it back to the original media.

One workflow I’ve been working on is automatically matching the Premiere proxies to the original media, checking FPS/timecode, then generating Resolve-compatible proxies before linking them in Resolve.

I actually built a small tool called Proxy Bridge around this workflow because doing the matching/linking manually was becoming repetitive. It’s specifically designed for Premiere Pro → DaVinci Resolve proxy workflows.

Hope that helps — the important part is making sure the proxy metadata matches the source rather than just matching the filename.

heartsnoopy
heartsnoopyAuthor
Participant
August 31, 2026

Thanks a lot for your reply!

I eventually came to a similar conclusion — the issue was most likely caused by the proxy files not matching the original media in terms of timecode and frame rate.

At this point, I think the simplest solution may just be to generate the proxies directly in DaVinci Resolve, especially if you already know you’re going to finish the edit there.

In any case, I really appreciate you sharing your workflow and the tool you built. Your answer was very helpful to me, and I’m sure it could also help other people in the community who run into the same Premiere-to-Resolve proxy issue.

Thanks again!

Uv28171828i8eg
Participant
August 31, 2026

Glad to hear you found it helpful! And yes, matching the proxy and original media’s frame rate and timecode is an important part of making the workflow reliable.

Generating proxies directly in Resolve can definitely be the simplest option when the entire finishing workflow is going to happen there. ProxyBridge is mainly aimed at cases where editors already have an existing Premiere proxy workflow and want to carry that workflow over into Resolve without rebuilding everything manually.

Thanks again for taking the time to share your experience!

Community Manager
Kevin-MonahanCommunity Manager
Community Manager
May 6, 2026

Hey ​@heartsnoopy,

Thanks for writing in. Sounds very frustrating. Tell me, do the proxies start at 00:00:00:00 instead of matching the camera originals? That could be the issue. Let us know.

 

Thanks,

Kevin

    heartsnoopy
    heartsnoopyAuthorCorrect answer
    Participant
    May 7, 2026

    Hi Kevin,

    Thanks for following up. Yes, when I export proxies using H.264, the timecode starts at 00:00:00:00.

    I also tried exporting proxies using ProRes, and in this case, the timecode seems to match the original media. However, DaVinci still cannot relink them.

    If I import both H.264 and ProRes proxies into DaVinci, it seems that the H.264 proxies have no timecode information, while the ProRes proxies do. So I’m starting to think that this might be a limitation or issue with DaVinci Resolve itself.

    Thanks again for your time and help!

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices