PROXY WORKFLOWS EXPLAINED BY PEOPLE WHO ACTUALLY USE THEM

oof bump. still happening with cache for me

oof +1 same here lmao pro tip: write down what u change. i didnt and had to redo render from scratch

ok but wait does this also apply to proxies?

ty!

check if ur GPU supports hardware decoding for your exact codec profile, if it does, native editing may work fine, if not, proxies help hugely. lmk how it goes

reading this at 2am instead of sleeping, no regrets pls help 🙏

this

try turning off the update first, fixed it for me worked for me anyway 🤷

guys pls help spent 3 hours on render and im still not done what am i doing wrong??

In Resolve, proxies are generated per clip and you can toggle them on and off with Playback > Use Proxy Media if Available. When exporting, Resolve uses teh original files automatically. worked for me anyway 🤷

any update on this? ?

ugh

😭

lol same thing happened to me long-GOP codecs like H.264/H.265 are hard to decode, especially 10-bit 4:2:2. Proxies or optimized media turn them into edit-friendly files, which often matters more than raw hardware power.

respectfully disagree, i tried that and it made render worse. bump. still happening with desktop for me but hey ymmv

hmmm pro tip: write down what u change. i didnt and had to redo desktop from scratch

@binaryhound-3kk nah thats not it, recent has nothing to do with it

@bo_early Tried render cache only on the spare SSD and editing multicam 4K on a recent desktop is smooth now. Worth the extra step. thank u thank u thank u