Resolve 17 Proxy Linking Bug

Hi, everybody, I was hoping v17.2 would fix this bug that occurs when linking proxy media. It's triggered by a certain filename structure. My temporary workaround is mass-rename files, adding letters to the end.

For example, DJI files are always linked incorrectly:

Proxy1.png (12.28 KiB) Viewed 2391 times

With my workaround linking works fine:

Proxy2.png (10.31 KiB) Viewed 2391 times

The other workaround would be linking those proxies one by one. But that's crazy, if you have too many files. So, my DJI files always qualify for twisted linking, and also my Panasonic GX80 files. They have the following structure:

P1020651.MP4
P1020654.MP4
P1020658.MP4

Again, mass-linking turns out to be a disaster. Please fix this in the next version.

It seems you've got more than one file of the same name. Maybe try creating the proxies from within Resolve?

...Maybe try creating the proxies from within Resolve?

It helps. But when trying to link to proxies, even those created within Resolve, the problem returns.

...It's triggered by a certain filename structure....

And probably all of these files have the same timecode 00:00:00:00?

And probably all of these files have the same timecode 00:00:00:00?

DJI drones does not have timecode - exept inspire 2

when trying to link to proxies

The native proxy process doesn't require you to link them, they get linked automatically.

Sooo...huh?

when trying to link to proxies

The native proxy process doesn't require you to link them, they get linked automatically.

Sooo...huh?

But if you want to move or to share...

But if you want to move or to share...

Well, I would say don't move.

And for sharing, share the original and let the other guy make his own proxies.

Differing timecodes don't help anyway.

But if you want to move or to share...

Well, I would say don't move.

Thanks for the tip, Jim. But let's treat bugs as bugs, and not as something to avoid. Bugs gotta be extinguished, wouldn't you agree?

I create proxies within Resolve via Media Management. This provides a lot more flexibility (like setting format, bitrate, etc). The Generate Proxy Media method is definitely not my go-to - it creates huge files. And I need my proxies to be small for several reasons. So, Media Management is the way to go.

But anyway, the bug is there. So, obviously, a little code tuneup will bring justice to this functionality. Until then, I'll just use the rename tool.

And I suppose bugs are to be reported elsewhere, right?

Why would you suggest something like "just dont move"?!?!

You dont know the reasons, why someone might have to move his proxy files.
I needed to restructure a project, now I have several hundred proxy files that didnt relink properly. Its Resolves Original Proxies, made within the Software itself. It should be able to recognise.

Of course Id prefer to also never change the structure of a running project, but it happened, and therefore to suggest just not to do it, is absolutely unnecessary.
Its a bug and there should be a solution offered ASAP. I mean we are all paying customers.
Relinking one-by-one or rendering all proxies again is both really time consuming and within a time sensitive project this could cause a lot of trouble to ones work-timeline.

So please, it would be appreciated, if someone from BMD could pick up this topic and forward it so it will be taken care of with the next bugfix update.

Hi,
I had the same problem trying to do proxy on my Ninja V ProRes 422 file. At first I tried using the Davinci built-in proxy generation, and it doesn't link properly (all files just linked to a random clip, most of the time to the same first clip xxxx_T001).

I successfully troubleshooted the problem by matching the file names (including extension) exactly as the original.

I discovered the Ninja V ProRes 422 file were named as XXXX_001.MOV (MOV in uppercase)
and all my failed try was either XXXX_001.mov (lower case mov) or XXXX_001.mp4.
I just renamed every file to exactly MOV using the replace rename.
It works fine now.

Hope this help

Heya, will this ever get fixed? I mean, it's such a lame bug, and it's probably so easy to fix it.

All filenames that end with numbers are incorrectly linked with the proxy media. I sometimes forget to rename my files to include letter in the end, and here we go again.

So, it's P1050250.MP4 --> P1050250A.MP4
Or, it's C0109.mp4 --> C0109D.mp4

Only if renamed, as in the above example, will the linking between MP4 and proxy MOV happen correctly.

Just found this thread, running 17.4.2 and creating proxy footage with AME. I'm using mostly Canon C300 footage for which the proxy linking works just fine, but for some footage shot with DJI this is a nightmare.

In a folder with 50 items, "DJI_0001" should link to "DJI_0001_ProRes Proxy 960x540" etc, which should be logically done by name (or at least have an option to select the type of pattern matching).

I've tried adding random letters after "540" so that the filename doesn't end with a number, but it doesn't help. I get 20 items linked to "DJI_0003"_ProRes Proxy 960x540", seemingly chosen at random, and the rest in complete chaos.

Is there a quick fix, short of linking them one by one (I have 3 folders of 50 files each)?

I have trouble believing this could be the current situation, in an application such as this.

Why, oh why, DJI can't write TC? Even a GoPro does.
There are apps which can add TC to a clip, based on the creation time. On the Mac MP4_to_QT can do that.