Created attachment 133983 [details] Usage Log from Krita and the Log encode, copy and paste SUMMARY I am trying to render an animation but when I do either of two things happen 1. Instead of an animation I will get frames (even though I chose video) and the gif or mp4 (I tried with both) will not work - the file says there is 0 bytes and I looked at the log encode file but couldn't figure out the issue. 2. The same thing happens when I choose the 'both' option but no frame images appear. STEPS TO REPRODUCE 1. Set up the animation (frame by frame) after importing frames 2. Press Render animation and click ok after choosing a file destination 3. Wait OBSERVED RESULT Instead of an animation I will get frames (even though I chose video) and the gif or mp4 (I tried with both) will not work - the file says there is 0 bytes EXPECTED RESULT A watchable gif should appear after rendering is completed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This might not be a bug but I couldn't find an answer online so I thought this would be the best way to figure out the problem The version I am using is 4.3.1 - it was not an option (gita7cf991) (Usage Log and Log encode are attatched)
Thanks for the log... unfortunately I don't see anything wrong there, either. Can you please: - update your Krita to Krita 4.4.1, and then if it still doesn't work, you can check out Krita 4.4.2-beta1 (https://krita.org/en/item/first-beta-of-krita-4-4-2/) although if 4.4.1 won't work, the beta won't work either, probably. - try this: https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#krita-text-output-logviewer - in point 3. it says "Do the thing you want to get the output of.", of course here you need to (try to) render the video. - check out Windows settings. Recently there was an update that disables program's access to non-standard directories, please make sure that both Krita and the ffmpeg has access to the directory you want to save your video to.
Created attachment 134017 [details] KritaLogwithnewversion I have downloaded the newer version and the problem is still there, I'm attaching two Log files - one (KritaLog) is from the old version and the second (KritaLogwithnewversion) is from the beta (4.4.2). I'm not quite sure how to change the Windows setting though On Thu, Dec 10, 2020 at 11:37 PM Tymond <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=430239 > > Tymond <tamtamy.tymona@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |tamtamy.tymona@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Tymond <tamtamy.tymona@gmail.com> --- > Thanks for the log... unfortunately I don't see anything wrong there, > either. > Can you please: > - update your Krita to Krita 4.4.1, and then if it still doesn't work, you > can > check out Krita 4.4.2-beta1 > (https://krita.org/en/item/first-beta-of-krita-4-4-2/) although if 4.4.1 > won't > work, the beta won't work either, probably. > - try this: > > https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#krita-text-output-logviewer > - in point 3. it says "Do the thing you want to get the output of.", of > course > here you need to (try to) render the video. > - check out Windows settings. Recently there was an update that disables > program's access to non-standard directories, please make sure that both > Krita > and the ffmpeg has access to the directory you want to save your video to. > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 134018 [details] KritaLog
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Created attachment 134031 [details] attachment-19074-0.html The problem hasn't been fixed, I don't know what else to do to try and fix it On Sat, Dec 12, 2020 at 4:34 AM Bug Janitor Service < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=430239 > > Bug Janitor Service <bug-janitor@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #4 from Bug Janitor Service <bug-janitor@kde.org> --- > Thanks for your comment! > > Automatically switching the status of this bug to REPORTED so that the KDE > team > knows that the bug is ready to get confirmed. > > In the future you may also do this yourself when providing needed > information. > > -- > You are receiving this mail because: > You reported the bug.
Hi Lauren, Could you please give me more details I would be glad to help further. Could you please supply me with the following details: - What is your current operating system? - Are these issues still occurring on Krita's `Krita Plus` version available on our website? - Does this issue occur on all files? If not, could you please provide us with a file so that we can reproduce the issue and fix it?
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 mark the bug 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!
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!