Bug or as designed? Proxies w/synced sound written MOS

I'm writing some proxy files from within Resolve.
The takes I'm proxifying have been synced with second system sound.
The proxies written are all without sound - either the synced or original embedded sound.

Feels odd. Seems like one or the other - probably the original embedded sound - should be in there.

That does seem odd to me. I would hope that the proxies had the original source media audio... I've never noticed this before.

If you take the same source clips without having sync'd them to external audio and generate proxies, do those proxies have original audio? Also - does it depend on the proxy format?

I just gave it a try with my proxy format set to ProRes 422 HQX and did not observe this issue (this is on my M1 Max). The proxies were generated with the linked sound, not the original camera audio (as observed when playing the proxy file from the Finder).

My camera originals had stereo PCM 48kHz as did my external sound recording.

OK - this is part user error, part very strange behavior which makes me wonder about the logic of the proxy system.

I wanted to create proxies for everything in a particular timeline. Since there's no Generate Proxies... command for a timeline, my workaround was to grab all the clips and dump them into a temp bin and generate proxies for them.

BUT! I just grabbed the video clips. Seemed reasonable to me as they point to the same files, right?
Well... you know what happened. Proxies were generated for the clips sans audio.

This seems VERY dangerous to me.
If I go back to the original "master" clip in the bins and generate a proxy I'll now have two proxies next to each other that don't match. One has audio, the other doesn't.

So Resolve isn't giving me a source file<->proxy file mapping. It's giving me a source file<->clip mapping.
Wanna relink proxies? Good luck! Who knows which will be the right ones.

Yikes! That does certainly leave us with plenty of rope to hang ourselves. I didn't realize proxies were related at the clip level but I guess it makes sense considering everything else we've heard about things like frame rate when creating proxies (since frame rate is also a clip-level interpretation of source).

Seems like you've been particularly 'lucky' finding the dozens of gotchas in Resolve.

Being a former - and recovering - software developer I like to explore things and figure out how they behave. That plus syncing poly wav files is probably most of it.


Sent from my iPhone using Tapatalk