#Current behavior

If any other codec (via the -f option) than apng is used, such as gif, taiga crashes with the following message :

[gif @ 0x56186259d800] Specified pixel format rgba is invalid or not supported

Also, trying to set an unsupported codec (like a text codec) leads to a segmentation fault :

$ taiga -f xsub
[NULL @ 0x5589e3b94540] Requested output format 'xsub' is not a suitable output format

Segmentation fault (core dumped)

#Correct behavior

taiga should output an error message if an unsupported codec is used instead of crashing, and support for more codecs should be added (like gif, mjpeg, ...).

I'm particularly interested in the gif format since it leads to much smaller files than apng.

#Fix

As I understand, the format given to main() is just sent to taiga_cap() which uses it to get the encoder with avcodec_find_encoder_by_name() without processing. The format should be checked in main() against a list of supported format.

To support gif encoding, it seems we need to give a RGB pixel format to the encoder instead of RGBA when the gif format is selected, but I could be wrong here.

It would be great to support smooth transition from Plymouth as others display-managers do.

I'm currently using greetd to autostart sway with this config :

[terminal]
vt = 1
[default_session]
command = "tuigreet --cmd sway --time --remember --asterisks"
user = "greeter"
[initial_session]
command = "sway"
user = "myuser"

There is a short black screen shown between Plymouth and sway in this case. Ideally it should transition smoothly between the two (without black screen).

Also when launching a graphical greeter instead of autologin, the transition should also be smooth for people using a greeter for the first login.