#libid3tag — Public Fediverse posts

#libid3tag 0.16.4 has been released! This is one of the largest releases, if not the largest release, of libid3tag ever since we started our fork. Check out the relesae here: https://codeberg.org/tenacityteam/libid3tag/releases/tag/0.16.4

In this release are many bug fixes, namely with PIC and UTF-16LE frames, a bump in the minimum required CMake version, and others too. See the above changelo for more info. We also thank mitchblank on Codeberg for contributing a lot of neat things to the library and helping move it forward too!

Initially, we planned to make a small release of #libid3tag that would contain just a few fixes and not too many changes from the current stable version. That, however, has changed thanks to a contributor stepping up and helping tackle all sorts of work that needed to be done.

All in all? libid3tag 0.16.4 will contain quite a few fixes and changes. Stay tuned for the final release!

So an update regarding https://floss.social/@tenacity/115809772540994485: #libid3tag won't be changed because it's genre list is actually for legacy compatibility. We will still look to add new genres in #Tenacity, however.

We need everyone's thoughts on this: should we add K-pop to #libid3tag's known genres? If we do it, it'll be for the 0.16.4 release, which we're actively working on at the moment. We'll do the same thing on the #Tenacity side too.

Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

Hey everyone! We're back working on the next release of #libid3tag. The next release will feature build fixes and more patches integrated.

Some of the patches we want to integrate come from an older version of Perl's Audio::Scan, which did use libid3tag at one point before switching to its own solution. You can view the PR integrating the patches here: https://codeberg.org/tenacityteam/libid3tag/pulls/12. We appreciate any and all feedback on it!

In other news, we're looking to finally get to improving #JACK support by making some minor changes in the audio engine. We don't suspect this impacting anyone a whole lot, but as always, holler if you need to after it happens. We're also looking to finally complete the theme system rewrite just to get to 1.4 alpha 2 finally. Finally, we also need to make new releases for #libmad and #libid3tag.

We've been busy with other things, including Real Life(TM), but we're still working on things!

It's been a little while since we last made releases on #libmad and #libid3tag. Since then, we've received a few contributions and fixes alike, and we think now makes a good time to put them in a release.

Turns out that we might be in your router too. If you use #FreshTomato 2024.1 or later then you'll likely have a copy of #libid3tag 0.16.3.

Yay! 😄

Turns out that we might be in your router too. If you use #FreshTomato 2024.1 or later then you'll likely have a copy of #libid3tag 0.16.3.

Yay! 😄

Turns out that we might be in your router too. If you use #FreshTomato 2024.1 or later then you'll likely have a copy of #libid3tag 0.16.3.

Yay! 😄

Turns out that we might be in your router too. If you use #FreshTomato 2024.1 or later then you'll likely have a copy of #libid3tag 0.16.3.

Yay! 😄

Turns out that we might be in your router too. If you use #FreshTomato 2024.1 or later then you'll likely have a copy of #libid3tag 0.16.3.

Yay! 😄

We recently found out that libid3tag is now packaged in Debian testing! Hooray! 🎉

We consider this a major advancement since quite a few distros are based on Debian. This will help with development as more and more programs will end up using our fork, so we can work with them and improve the library like never before! 😄

#debian #debiantesting #libid3tag