![]() I just would like to take advantage of the hardware acceleration since it's an option. My videos have been going through up to 3 passes and successfully saving to disk. I have hardware acceleration turned off and multi-pass turned on and it seems to be more stable than previous versions. With hardware acceleration on, encoded failure or not, the performance is impressively fast! It's unfortunate that it can't be used concurrently the multi-pass option to get a better quality export.Ĭurrently I'm running version 17.3.2 Build 8 and I'm still running into these same issues. But there are instances where the encoder goes through up to 6 passes, and appears to finish successfully, but when you check the file it's only a few kilobytes in size, resulting in a failed export. With hardware acceleration off and multi-pass on, things sometimes go smoothly. ![]() With both hardware acceleration and mult-pass disabled, videos encode successfully but will result in lower-than-standard image quality. It took me a long time of troubleshooting, but I figured out that using hardware acceleration and multi-pass encoding together was the problem. Then I would have to uninstall the newer versions and reinstall 17.1 Every version after that, the encoding would freeze at the end of the first pass and then give the "Failed to encode the video frame" error. In version 17.1, videos would do two passes of encoding and then will save onto disk. I'm guessing 17.1 is the last version before M1 support because since then, h.264 encoding with multi-pass and hardware acceleration has always been failing. Just wanted to address an issue I've been experiencing with every DaVinci Resolve release after version 17.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |