Krita Weekly Update - November 2022 - week 46

Welcome to this week’s edition of the Krita Weekly Development Update, brought to you by the @Krita-promo team! This meeting was led by @halla.

Statistics

  • Downloads: 76,317 (74,260) unique downloads last week.
  • Web traffic: 173,416 (171,633) visits, 378,849 (374,876) unique page views last week
  • Donations: 6865 in the past month
  • Fund.krita.org: 192 subscribers (peak was 202, last week 195)
  • Krita-artists.org: Pageviews last week - 242,000
  • Twitter: 59,088 (59135)
  • Mastodon: 4770 (4103)
  • Peertube: 503
  • Krita subreddit: 68,496 (68,275 last week)

Highlights of the week

  • Bugs have piled up a bit and we also have 3 new regressions in master.

  • The devs are targeting 5.2 for porting Krita to QT’s newer version and with KDE’s patches for it.

  • The team is discussing if some libraries like libraqm (a library for complex text layout) will pose any problem. There is still some work to do to get the text branch into master.

  • The team is planning for a bug fix release in mid December.

  • @emmetpdx and @eoinoneill audio related work is targeted for 5.2 release. They are trying to get FFmpeg merged first.

  • The YouTube channel is at 60k subs and growing, @RamonM has prepared video tips and tricks in general section and colors that he wants to release next week.

  • @Halla prepared the release the weekend before last, then she picked up work on the palette docker again!

  • @wolthera worked on preparing the release last week and she handled all the announcements on Mastodon and other places. She also mentored @Reinold for their GSOC project.

  • @Tiar’s work on ellipse assistant continues. She has replaced part of the code that is based on a scientific article with her code, it has passed all her manual tests and works fast enough in Krita. All that is left to do for the tool are mirroring over the horizon line and making a prettier preview, for which she already has code prepared.

  • @Sh-zam fixed some bugs and regression related to empty palette files on Android, they also worked on the resource database location bug on Android.

  • @dkazakov fixed bugs in the new Lager branch after taking feedback from the KA community. Now he is gearing up to write developer documentation for the branch

  • @IvanYossi worked on getting the developer tools on macOS up to date and also Apple’s notarisation process. Ivan will be trying to get kritarunner the command line utility for batch processing bundled in the DMG.

  • @amyspark worked on getting @wolthera’s text branch up to date with all required libraries. They are also working on getting FFmpeg ready for the audio branch.

Summary

By now you’ve seen last week’s releases (5.1.3 for most platforms; 5.1.2 for Android). These were mostly bug fixes. The team is now focusing on triaging and fixing bug reports, finishing the audio work with FFmpeg, and preparing to update to a newer QT version. There is also continued progress on the new Lager-based brush editor and the text tool upgrade. This is by no means a complete list—it’s just a taste of the dev team’s activities and progress.

Krita’s YouTube channel continues to show growth but we’re all wondering what will happen with Twitter in the near future. Many are turning to Mastodon. Here’s how you can find Krita there. Krita (@Krita@mastodon.art) - Mastodon.ART

If you’re enjoying Krita, we invite you to contribute through the Krita Development Fund.

Commit report

This is compiled by @freyalupen.

Commits (Click to expand and read)

What follows is a list of changes made to Krita’s code over the last week (November 7 - 14, 2022). These changes are available in the latest nightly builds:

Major changes (new features, major bugfixes):


5.1.x branch (Krita Plus):

** Data loss bugfixes:

5.2.x branch (Krita Next):

** Crash fixes:

These three crashes were only present on recent Nightly builds.

** Shortcut actions:


Minor changes (small bugfixes, small tweaks to features):


5.1.x branch (Krita Plus):

** Tools:

** File formats:

5.2.x branch (Krita Next):

** File formats:

** Tools:

** Keyboard shortcuts:

** Layers docker:

** Misc


Technical changes (mostly invisible to users; code refactors, build fixes, tests, logging):


5.2.x branch (Krita Next):

** macOS build:

** Android build:

** MSVC Windows build:

** Build:

** Cleanup:

7 Likes

Does this mean that ffmpeg will be built in to krita?
I thought there were problems with license incompatibility.

1 Like

I am not sure but @emmetpdx and @eoinoneill have looked at how some distributions like OpenSUSE distribute it. May be they can shed some light here.

1 Like

In addition to Krita foundation you can also follow our forum account at @krita_artists@mastodon.art

3 Likes

Yes, FFMpeg will be built in, but only “safe” formats will be enabled- that is, formats without any license issues, according to OpenSUSE. The (technical) discussion about it is here: Let's talk about... FFMpeg!? (!1599) · Merge requests · Graphics / Krita · GitLab

4 Likes

From the linked MR:

I think the consensus here is that in the long term we should continue to provide users with the option of supplying their own external ffmpeg if possible, keeping KisFFMPegWrapper around and building on top of that should make that relatively painless in most cases I think.

That should cover things nicely, “if possible”.

1 Like