So I had to relink some footage on a project in Davinci Resolve, but it's starting EVERY single cut that I have in the footage at the 00.00 timecode of the relinked footage, rather than working like normal?
Luckily I had an old save to revert too but this could cause horrible issues in the future is there a reason this happened that I can avoid?
Maybe someone else has an idea, but I don't have enough information to even begin to guess.
Does the media have timecode? Are externally created proxies in use? Do they have timecode? How did the files go offline? Are network or removable drives in play?
Details.
My Biases:
You NEED training. You NEED a desktop. You NEED a calibrated (non-computer) display.
Yes we need more details of your workflow. When you say you’re “relinking”, do you mean an existing Resolve project that previously linked correctly? Or do you mean you’re trying to link an imported XML sequence from another app like Premiere?
If your clips even show a TC with all zeroes I assume they don't have TC in the first place. Add some with a tool like EditReady before using them in any NLE!
My disaster protection: export a .drp file to a physically separated storage regularly. Please visit digitalproduction.com/author/uliplank/
Studio 19.1.3 2017 iMac, MacOS 13.7.4, eGPU MacBook M1 Pro and M4 Pro mini, MacOS 14.7.5 SE, USM G3
Mel Matsuoka wrote:Yes we need more details of your workflow. When you say you’re “relinking”, do you mean an existing Resolve project that previously linked correctly? Or do you mean you’re trying to link an imported XML sequence from another app like Premiere?
I just had a project that I had cut up, one of the video files had a name changed by someone else so I had to replace the footage with the same base footage of a different name now, and that's where the issue happened.
I'm only confused as to why it happened like this as I've done it countless times in Premiere and never had this issue
I'd agree if there was any logical reason that it was happening this way I know they're all different but that doesn't change a weird behaviour haha
Thanks Jim that was the first thing I tried it's cool I worked around it for now just made sure everyone at work knows not to change things once an edit has begun