recorder broken; each session gets separate folder, and cannot output full video STEPS TO REPRODUCE 1. Open beta2 appimage. Already have recorder set to auto-record. 2. Paint, close krita, start new session with same painting. 3. Try to output full video, but only the 2nd session outputs. OBSERVED RESULT Only second session of painting outputs, because each session's painting goes to separate folder, which breaks recorder output/not able to output full video of painting. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Doesn't seem like I can reproduce this myself in beta 2 nor beta 2 git 84eaf3c, with the appimages on Debian sid.
I've just tried today's nightly ... krita-5.1.0-prealpha-fbe192a-x86_64.appimage ... scribbled a short session, saving as psd, then closed down and re-opened the psd, continuing to paint. I've then exported the video, but it only exported the 2nd session. Am on Mint Mate 20.04, and not sure if there's anything external the appimage needs? Does the nightly include the latest beta2 fixes, or is there somewhere else to download the latest beta2?
PS have just found where the beta downloads are, but I can't see any dated since doing the initial bugreport. https://download.kde.org/unstable/krita/5.0.0-beta2/
Just to add that I enabled logging, while doing the 2-sessions test again ... in 2nd session, krita crashed (unfortunately without any recovery when re-opened), but log showed nothing about the crash, and no reference to recorder only having a few new seconds of scribble to output (the re-done 2nd session). Looked at Mate logs too, but can't see anything in them, except a few refs to "ForegroundNormal" - conversion from "0" to QColor failed].
Sorry, not able to edit posts, so another addition to say I've tested recording in the usual appimage that works, from July this year, and that isn't working either, which is really surprising, as it used to work fine. Wondering if it's to do with something from system impacting on Krita. System isn't modified; just installed, basic updates, and running the offered kernel 5.11.0-38 as well as usual 5.4.
Just to add that I've tested it on debian-based Sparkylinux 7 (Mate) rolling, kernel 5.14, which I'd just been having a look at on the laptop ... same outcome unfortunately. Both main PC and the laptop are AMD/Radeon.
Just to add that tried yesterday's Plus, krita-5.0.0-beta2-84eaf3c-x86_64.appimage, but same outcome.
I'm able to reproduce this only if I save the document as a psd and then reopen as psd. If I keep the document as a .kra file the exported video will have all the drawing sessions. @fae can you confirm if it works properly for you when saving as .kra file but not psd?
I doubt it's meant to work if you save as .psd file. Nobody probably tested it, and there might be reasons why it doesn't work. Probably doesn't have the same metadata Krita saves to .kra files. You shouldn't save your working files as .psd files anyway: .kra format is the only one that can save *everything* Krita produces. .psd export has limitations, there is plenty of things you can't save into .psd file: multiple transparency masks, multiple color spaces in a file, lots of blending modes are not available there, etc... Better save as .kra files and export as .psd files, the same way you export as .png or .jpg files. Can you please check (like @Reinold asked) whether the bug doesn't happen with .kra files?
Thanks for responses Reinold and Tiar I use Sai mainly, and choose psd for that reason, and prefer nothing extra in the save except the artwork, and don't use any of the extra features such as masks etc. For recording art done solely in krita, yes, saving a psd as well as the kra, after recording, would fix being able to have the psd ... may have saved as kra by accident the other day, and still had issues, but will test and report back.
On the krita forum, I'd said it was psd I was using, when reporting the issue, and I thought I'd put that here too; apologies that I hadn't. Working fine with kra, which is great, so I'll close the issue.
Not sure how to close the issue, oops.
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.