You have to close the Davinci task via the taskmanager.*On macOS (Intel) and macOS (M1), GPU encoding is available via the Metal framework if it is supported by the hardware.įor example, under Windows, there are AVC/H.264 software as well as hardware encoding options for both Intel Quick Sync Video (IQSV) and NVIDIA NVENC, whereas on Linux there is no H.264 software codec but only NVENC hardware encoding for NVIDIA GPUs. FYI, the corrupted file can be deleted once Davinci is closed properly. Melvinpao wrote:Most excited to have h.256 hardware accelerated rendering in the free version! But.it doesn't work! It starts rendering at much higher framerate than h.264 but doesn't complete the render. Hope it helps.ĪMD Radeon 5600XT with the latest driversġTB nVME SSD Attachments DaVinci-Resolve-logs-20211024-025829.zip (44.99 KiB) Downloaded 56 times It's basically a corrupted file.Īttaching the logs after the "crash" but generated after restarting Davinci Resolve. The "crashed" output video file cannot be deleted in Windows until a system restart. None managed to reliably be rendered out in h.256. So far all my source material is in h.264 from various cameras and video capture devices at 50 or 60 fps. Sometimes it completes the render, but other times it doesn't. I tried rendering at a slower frame rate timeline (a 24 fps timeline seems have the greatest chance of success), but it's also a hit-and-miss. I can quit Davinci Resolve but it prompts me to either continue the render or to stop and quit (which I have already did). I can stop the render but the rest of the UI is unresponsive. The playback head just gets stuck and the progress percentage and time remaining doesn't progress. The h265 renderer seems to be stuck when it transits between cuts or clips. h.264 rendering is OK but it's so much slower. Most excited to have h.256 hardware accelerated rendering in the free version! But.it doesn't work! It starts rendering at much higher framerate than h.264 but doesn't complete the render. Must be a bug that needs to be squashed with 265. Rendering out an h264 with old settings now to see if the issue also appears here. It's happening on my latest Dell XPS 13 with Tiger Lake i7 CPU. I can't seem to submit a bug report since most of the UI is unclickable so I can't submit an error log. It always gets stuck in between and I can still cancel the render but the UI is mostly unresponsive.
AndyGalster wrote:h265 rendering keeps on crashing for me.
0 kommentar(er)
