Created attachment 112570 [details] Log created when rendering On Windows 8.1, I am trying to export 500 frames at a time out of about 9500 frames. The first 500 frames went fine when exporting as a ".ogg" file. The next set of frames (501 through 1000) and the next (1001 through 1500) did not render properly. It gave me the error "Could not render animation: FFmpeg failed to convert the image sequence" error. I have used the "20180508-293a6e8" nightly git build of FFmpeg (log linked) and the 4.0 release build. I did find the log in the folder where I set the files to go when rendering. My animation is in 1080p (1920 x 1080) with a bit depth of 8 and the lowest layer is white (dunno if that counts as transparent or not). The entire animation is about 9500 frames long, but I only tried to render 500 of them, specifically frames 1001 through 1500.
Created attachment 112571 [details] Log created when rendering with 4.0 version of FFmpeg The other file made by the other version of FFmpeg
Hi, mastertobygaming! Could you check if there are actually .png files generated in the following folder: C:/Users/dlee9_000/Desktop/Animations/English Project/English Project Part 1/1001 to 1500/ (don't forget to clear a checkbox near "Remove PNG files after conversion")
Setting to needinfo.
(In reply to Dmitry Kazakov from comment #2) > Hi, mastertobygaming! > > Could you check if there are actually .png files generated in the following > folder: > > C:/Users/dlee9_000/Desktop/Animations/English Project/English Project Part > 1/1001 to 1500/ > > (don't forget to clear a checkbox near "Remove PNG files after conversion") When the process fails, the .png files do remain and I have to delete them manually. They do show up where I want to export the animation
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!