Bug 468431 - ffmpeg error "Unrecognized option 'start_number'" when rendering gif
Summary: ffmpeg error "Unrecognized option 'start_number'" when rendering gif
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 5.1.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Emmet O'Neill
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-12 18:41 UTC by merlindanner
Modified: 2023-09-30 03:46 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description merlindanner 2023-04-12 18:41:42 UTC
SUMMARY
When rendering an animation as a gif, it fails with the error message:

Could not render animation:
Unknown error.

I logged the output of ffmpeg using a wrapper script and it reports these errors:

Reading option '-start_number' ...Unrecognized option 'start_number'.
Error splitting the argument list: Option not found
Unrecognized option 'start_number'.
Error splitting the argument list: Option not found

STEPS TO REPRODUCE
1.  New custom document (I did 64x64, but I don't think that matters)
2.  Add a blank frame in the animation view
3. Try to render animation as a gif (ffmpeg is installed of course)

OBSERVED RESULT
Error window:
Could not render animation:
Unknown error.

EXPECTED RESULT
Renders animation to gif file

SOFTWARE/OS VERSIONS
ArchLinux
Krita Version 5.1.5 (flatpak install)
Running on gnome (xorg)
ffmpeg version (archlinux repo):
configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libjxl --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-shared --enable-version3 --enable-vulkan
libavutil      58.  2.100 / 58.  2.100
libavcodec     60.  3.100 / 60.  3.100
libavformat    60.  3.100 / 60.  3.100
libavdevice    60.  1.100 / 60.  1.100
libavfilter     9.  3.100 /  9.  3.100
libswscale      7.  1.100 /  7.  1.100
libswresample   4. 10.100 /  4. 10.100
libpostproc    57.  1.100 / 57.  1.100
Comment 1 merlindanner 2023-04-12 18:49:59 UTC
Actually I just tried rendering other output formats than gif and they also failed with the same errors (tried apng, webm, webp).
Comment 2 amyspark 2023-04-12 21:06:32 UTC
Emmet, can you take a look? I don't yet have the new dependencies set up here.
Comment 3 Dmitry Kazakov 2023-08-31 13:04:55 UTC
Hi, Merlin!

Could you please test Krita 5.2.0 Beta2 appimage package from the offical Krita website?

https://krita.org/en/item/second-beta-for-krita-5-2-0-released/

I guess the problem is in the usage of flatpak that has some issues with calling external apps.

Also make sure that you use ffmpeg that supports both palettegen and paletteuse. E.g. the one that is shipped with Krita (on Windows) doesn't support that.
Comment 4 Bug Janitor Service 2023-09-15 03:45:32 UTC
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!
Comment 5 Bug Janitor Service 2023-09-30 03:46:18 UTC
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!