Nina Becker
Infrastructure person. Prefers runbooks over heroics. Interested in cpus, keyboards, proxmox.
- Reputation
- 318
- Topics
- 0
- Posts
- 33
- Solutions
- 0
- Joined
- 10 November 2025
long time lurker first post lol i swear render is cursed thx in advance!!
rendering to an intermediate like ProRes first and then encoding to H.264 MP4 separately is slower, but very reliable for tricky projects. but hey ymmv
been there man pro tip: write down what u change... i didnt and had to redo video editing from scratch
this. sooo much this. wait does this also apply to resolve?
agreed
Note the timecode where it fails, go to that point in teh timeline and check every clip there. A corrutped source file, a variable frame rate clip or a broken effect at that spot is the usual cause.
oof clear teh render cache: in Resolve, Playback Delete Render Cache All . Corrupted cache files can break exports even if playback looks fine.
🙏
try a different encoder: switch between hardware (NVIDIA/AMD/Intel) and software encoding in teh export setitngs, if one works, update or reinstall the GPU driver.
ok update: did what @ava.lindqvist40 said and its fine now u guys are the best!!!
ok but dumb question but how do i even check the cable ?
which version are you on?
hmmm which version are u on? ?
dude finally got it working, thx everyone. bump. still happening with 1080p for me u guys are the best!!!
agreed