D5 Render Version: 2.11 Graphics Card: Nvidia RTX 4070 Super Driver Version: Nvidia Studio Driver Version 577.00 Issue Description: Can’t create video render properly. Created videos are always corrupted. Screenshots/Videos Description: Steps to Reproduce (optional):
I use Render Queue after creating 100 seconds animation with the settings: 1080p, mp4, 30 fps… It goes though the render and took 22 minutes and 9 seconds. when I open the video file, my video players (Media Player and VLC) cant open the created file. I’ve tried to render 10 time already and wasted quite some time. Also set the video quality lower but D5 render still cant create a video I can use.
I also disabled Super resolution and FPS Booster and still cant open the video created. Always have this “video corrupted” issue.
Can you please help?
BTW This wasn’t the case before when I was using version 2.10 and 2.9.
Please try placing the rendered videos in another file location? Perhaps in downloads?
I would also want to collect your files (scene and logs) and test it on my end. Please send it to support@d5techs.com and have it titled ‘2.11 Clov-Forum Rendering animations videos don’t work. Video files are always corrupted.’
I deleted the video clip and recreated a new clip and it worked. It seems problem happen while creating clip shots. I will definitely do your recommendation on reporting in case it happens again. Thanks for the help. Cheers!
I just tested your file from the email you sent a few days ago. Basically, I rendered the clips (mp4 format and not .avi) that were already ready to be rendered and changed their quality to 2k just to see if a higher quality yields video corruption.
Video corruption typically occurs when the rendering process is interrupted before it can be fully completed. (Please confirm if any of these were done.) This interruption can be caused by different reasons:
A software crash: The D5 application crashed while the clip was being rendered.
A user-initiated closure: The file was closed while the render was still in progress. This often happens when a render gets stuck at a high percentage (e.g., 99%) for a few minutes and is prematurely closed by the user, who assumes it has already finished.
You can try rendering in a different file location, just to test if there are any differences. If issues still persist, then we may need your log files.
