Clips with changed video frame rate won't match to proxy

This bug involves Resolve 18 beta 5, and the Blackmagic Proxy Generator, and Cloud Store Mini (although that's probably not relevant).

macOS 12.4, Resolve 18b5
Database is stored in BMD Cloud

1. Footage shot 59.94
2. Media copied to Cloud Store, H.265 proxy media generated by Proxy Generator, and synced to Dropbox
3. On Mac #1, while connected to original (and proxy) media, clip changed to 29.97 in Resolve 18 b5 via Right click > Clip Attributes > Video > Video Frame Rate > change to 29.97
4. Resolve opened on Mac #2, and this media would not connect to proxy media, even when manually pointing one clip at a time to the correct proxy clip, reporting error "invalid proxy selected":

CleanShot 2022-07-01 at 19.29.20@2x.png (238.18 KiB) Viewed 485 times

5. Media changed back to 59.94 on Mac #2, and proxy media immediately and automatically connected
6. Media changed back to 29.97, and connection was maintained

-Joseph

I would expect that behaviour when the clip and proxy have differing frame rates. They do need to be the same for proxies to work correctly.

I would expect that behaviour when the clip and proxy have differing frame rates. They do need to be the same for proxies to work correctly.

But the framerate of the base clip hasn’t changed — that’s just metadata in Resolve.


Sent from my iPhone using Tapatalk

The Clip Attributes are "baked into" the Proxy, so you would have to change those before making proxies.

Which means you'll need to make the proxies from within Resolve, not using the stand alone program.

The Clip Attributes are "baked into" the Proxy, so you would have to change those before making proxies.

Which means you'll need to make the proxies from within Resolve, not using the stand alone program.

Fascinating… that's a bad design decision then. The proxy should identically match the source clip, not the settings in Resolve. What happens in Resolve stays in Resolve… it's just metadata.

The Clip Attributes are "baked into" the Proxy, so you would have to change those before making proxies.

Which means you'll need to make the proxies from within Resolve, not using the stand alone program.

I haven't used the external proxy generator, but is there a way to tell it the target frame rate?

The Clip Attributes are "baked into" the Proxy, so you would have to change those before making proxies.

Which means you'll need to make the proxies from within Resolve, not using the stand alone program.

I haven't used the external proxy generator, but is there a way to tell it the target frame rate?

The frame rate will match the original source media frame rate. It is not a converter.

The frame rate will match the original source media frame rate. It is not a converter.

Hence why I think this is a bug. If the source is 59.94, then the proxy is 59.94. If I tell Resolve to play the 59.94 clip at 29.97, that has nothing to do with the Proxy file. It's just metadata. It should still link to the file.

I maintain that this is a bug.

-Joseph