Bug 485666 - Animation Renderer doesn't remember file type used last
Summary: Animation Renderer doesn't remember file type used last
Status: RESOLVED REMIND
Alias: None
Product: krita
Classification: Applications
Component: Animation (other bugs)
Version First Reported In: 5.2.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Emmet O'Neill
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-17 09:19 UTC by mbcnve
Modified: 2025-05-14 21:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Animation Renderer (59.25 KB, image/png)
2024-04-17 09:19 UTC, mbcnve
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mbcnve 2024-04-17 09:19:57 UTC
Created attachment 168606 [details]
Animation Renderer

SUMMARY
Animation Renderer doesn't remember file type used last. The initial selection of file type is always MKV.

STEPS TO REPRODUCE
1. Open an animated document. Click "File"-"Render Animation...." to invoke animation renderer.
2. Select "MPEG-4 video" for "Render as" option and click "OK" to render animation.
3. After animation render finished, click "File"-"Render Animation...." again to invoke animation renderer.

OBSERVED RESULT&EXPECTED RESULT
The initial selection for "Render as" option is "Matroska video" rather than "MPEG-4 video" which is used to render last time.
Comment 1 Emmet O'Neill 2024-04-17 22:22:41 UTC
You're right, and it should. Confirming this.

Thanks for the report.
Comment 2 Emmet O'Neill 2024-09-06 21:03:49 UTC
Git commit 94072709d3de2c503f59f66a06fd011c947150ae by Emmet O'Neill.
Committed on 06/09/2024 at 21:00.
Pushed by emmetoneill into branch 'master'.

AnimRender: Make render dialog remember previous video container format.

There were a few different pieces of code setting and re-setting
the video container format, as well as an improper use of KisConfig.
This commit fixed that.

M  +13   -2    libs/ui/animation/KisDlgAnimationRenderer.cpp

https://invent.kde.org/graphics/krita/-/commit/94072709d3de2c503f59f66a06fd011c947150ae
Comment 3 BabylonAS 2025-01-29 17:15:10 UTC
Appears to still be an issue, can confirm that the bug still happens as of 5.2.9 (tested on Linux).
Comment 4 Emmet O'Neill 2025-05-14 21:31:54 UTC
The previous fix appears to still be working in Krita's master branch, so I think it didn't make the cut for 5.2.9 (probably my fault for not back-porting it to the release branch in time for the last release). Sorry about that...

Unfortunately, that means that you'll likely have to continue waiting for Krita 5.3, or opt for using the Krita Next nightly branch in the meantime. Alternatively, you could build Krita from source (either using the master branch, or the last release branch + the cherry-picked commit containing the fix.) 

Granted, none of these are ideal, but at least you have a few options. :/

(I'm marking this as Resolved/Remind for the next release, though its inclusion in the next release branch should happen automatically.)