https://bugs.kde.org/show_bug.cgi?id=443105
--- Comment #5 from Eoin O'Neill <eoinoneill1...@gmail.com> --- So there are some improvements I've made here that I will try to get into 5.1's branch. Canceling the frame export will now properly clean up any files that were made during the progress of exporting. Additionally, there have been improvements made to the unique frames and frame sequence deletion properties that should make this bug less likely to occur. The key word is less likely though since changing the number offset will still occasionally causes this issue. In order to fix this, we will need to migrate some of our FFMpeg calls to use the "concatenate" codec where we specify files in a text file, which will take some time and probably won't make 5.1. If you do a lot of "Start numbering at" value changes, which is admittedly better suited for image sequence only export circumstances, my recommendation for now would be to change the sequence "Base name" entry for circumstances where you want to export the same file multiple times with different time offsets while also needing a video of said frames. I'll let you know when there are any updates. For now, I've updated the title of this bug to better reflect the current problem. -- You are receiving this mail because: You are watching all bug changes.
