home.social
  1. Not too long ago, we discovered there was a fake "mirror" of #Tenacity to #SourceForge. As of today, it looks like SourceForge took it down, along with the account impersonating @gperson.

    For now, we have no plans regarding SourceForge, except for the possibility of creating a legitimate redirect to prevent this from ever happening again. We are still debating that, however.

  2. IMPORTANT: There appears to be an unofficial mirror on #SourceForge that attempts to be legitimate. THIS IS FAKE.

    What's more concerning is the fact that there appears to be an impersonator of @gperson. This is NOT them as they are NOT on SourceForge. The fake project also distributes both the 64-bit version and a fake macOS Universal 2 binary also well. The latter is almost certainly fake; we do not plan on distributing a universal binary (more on that later).

  3. Starting in 1.4, we plan to upgrade #Tenacity's license from the GPL v2 (or later) to GPL v3 (or later). Most source files going forward, unless otherwise stated, will be available under the GPL v2 or later and will continue to be that way. However, if we want #ASIO support, we would probably have to backport some changes to 1.3.5 to allow for making GPL v3 (or later) builds. This shouldn't be much of an issue, but we're not completely sure how well this would work.

  4. Hey everyone! It's been a little bit since our last post, so we'll detail what's happening here!

    Unfortunately, we don't have a whole lot to report, but we have been readying a new release of #libmad. The last thing we have will be for source packaging via CPack as we will now start providing our own source tarballs.

    Once we get libmad 0.16.5 released and in #vcpkg, we'll get going on #Tenacity 1.3.5, which will feature updated dependencies mainly. That also means we'll update our Flatpak too!

  5. #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: codeberg.org/tenacityteam/libi

    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!

  6. So...today (EDIT: or yesterday?) #simdjson 4.3.0 was released!

    Yep, we're going to switch to this library for any #JSON needs.

  7. #rapidjson sounds great until you realize it's not had a release in almost 10 years at this point 😳

    Well, at least #simdjson has had a better release record, the latest release being in December 2025 👀

  8. Hey everyone! Not much activity to report on this time, but just some house keeping that's just been done, mainly two PRs that were merged!

    The first PR: fixes an issue where #Tenacity would crash on startup after going back to the latest stable version and resetting the toolbar layout. Toolbar preferences are also now properly reset when upgrading to 1.4.

    The second PR: more cherry picks from upstream, but this time they're from the latest development version of AU 3.

  9. Hey everyone! @gperson here with a few things. First, I now have a new laptop, so I'll be able to do many more things with #Tenacity now. Second off, some things are moving recently, so baring university classes, you may see a little more activity on Tenacity.

    Thanks again for everyone's support! We have a bit of a backlog of work to address, so we'll try to work on that while also getting releases of Tenacity, libid3tag, and even libmad out.

    - @gperson

  10. Hey everyone, @gperson here. Just a quick update on why there hasn't been much #Tenacity activity recently.

    Unfortunately, the last month of 2025 has been *very* hectic for me personally, and I do not expect it to get better this year. I'm not going to say what's going on, but just know that it's going to take time away from what I can do with this project and other things in general. There will still be others around, and I will still be around, just less frequently.

  11. Previously, an unofficial #Tenacity #Matrix room used the #tenacity:matrix.org room address, and our official room had to use #tenacity2:matrix.org. Now, that has changed, and our official Matrix room is now #tenacity:matrix.org!

    Our website has been updated along with anywhere else we mentioned our official Matrix channel. Meanwhile, the old, now semi-official channel will be repurposed for something else.

  12. This is perhaps the biggest article written about #Tenacity in quite a while: makeuseof.com/audacity-too-clu

    Yes, we were only made aware of this recently. Either way, it's still pretty neat, except one thing: you can record desktop audio on #Windows (it was a past limitation).

  13. No, we won't have a new Tenacity release by New Years (either in a few hours or so). However, we will try to add one more thing for 1.3.5 before releasing it: #ASIO support on #Windows.

    Unfortunately, this release won't have #macOS builds yet again because of other unforseen issues (the builds seem to get stuck somewhere, but at least they will properly build and package now). However, we will have new Windows on ARM builds without FFmpeg, so that'll be new!

  14. 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!

  15. So an update regarding floss.social/@tenacity/1158097: #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.

  16. 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.

  17. 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.

  18. 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: codeberg.org/tenacityteam/libi. We appreciate any and all feedback on it!

  19. 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!

  20. 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.

  21. Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.

    The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!

  22. We have a quick question: how is #HiDPI support in #Tenacity compared to the latest version of #Audacity on #Windows? What about on #Linux?

    Just a little curious to see how the state of HiDPI support is between the two right now 👀

  23. It appears that the #ASIO SDK is now available under the GPL v3. This is quite a big deal and means we can have official ASIO-enabled builds on Windows from now on.

    This is awesome! 🎉

    EDIT: To clarify, the ASIO SDK is available under the GPL v3 in addition to its proprietary license. Still, this is huge!

  24. @k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄

  25. Wait, #wxWidgets has a new dark mode on Windows now...

    👀

  26. Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.

  27. For the first time in years, #nightly builds are back! Download them here: nightly.link/tenacityteam/tena

    #macOS builds aren't available yet, but we'll work on it! However, we now have a #Windows on #ARM build available! It requires Windows 11 or later.

  28. @tauon Tenacity already supports #MIDI right now in a limited capacity. For the new project format, we would not include MIDI support as we would have to figure that out. We still haven't thought that through, but it could be possible. (Edit: so yeah, it'd be more so a 'yet' right now).

    Unless #Matroska already supports MIDI. Then that's a different story...

  29. The idea behind this new format is simple: what if we returned to the older AUP format, but we put everything in a binary #XML representation? After all, an #AUP project is just an XML file with a directory containing block files, so why not merge all this data in a binary XML representation?

    It turns out we can, and what better format to use than #EBML? #Matroska uses it, and since it's a container that supports audio, we can use it as a starting point for our new project format.

  30. CW: Today's Random Idea

    TAP: #Tenacity #Audio Project. An extension to #Matroska, it would replace #AUP3 in Tenacity.

  31. #Mastodon polls are nice, but we'd like to use something more formal. Does anyone have an idea about a #polling service or so?

    #Disroot apparently used to have one, but it no longer exists as far as we can tell. #Google Forms, well...you can fill in the details. There is #StrawPoll that we're aware of too. Any thoughts?

  32. Great news! We now have a working #Matroska exporter on our rebase branch! It hasn't been merged yet, but it will be soon! Hooray! 🎉

    Last up is our dynamic compressor, which will be more challenging since that will need some preliminary work first.

  33. Apparently, #KiCad had said some things about #Wayland support and how they don't work under #wxWidgets quite yet. Since we are also a wxWidgets program, we'll say a few things about our Wayland support, which isn't perfect:

    - Toolbars don't work under Wayland.

    - As of the latest stable, the track panel works, but needs to be optimized.

    - Tooltips work.

    This requires explanation, however (1/2).

  34. What's kind of funny (but unsurprising) is how even after #Audacity had their initial telemetry controversy, we're seeing them go down the path of #enshittification. Of course, these features can be disabled at build time, but (heads up: promotional) We Do It For You™.

    Either way, it can be an #anecdote that with a bit of...#tenacity, you don't have to justify a #fork. Just let your upstream do it for you.

  35. 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! 😄

  36. Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

    On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

  37. Happy New Year everyone! Just in time to start off the 2025 new year (over here on the pacific coast anyways), Tenacity 1.3.4 has been released! This release contains numerous bug fixes and improvements across all sorts of platforms. Please see codeberg.org/tenacityteam/tena for more information. (The changelog is quite long to list here).

  38. Another update regarding the 3.7.1 rebase from your local @gperson:

    Unfortunately, I've decided that our light and dark themes will not be re-added during the initial rebase. I'm quite done dealing with upstream's theming system, which has only gotten...better, I guess?

    Instead, they'll be added once the theme system rewrite is complete. That way, themes will be much easier to deal with.

  39. And this build is now public! Visit codeberg.org/tenacityteam/tena to try it out for yourself.

    WARNING: Things *will* be broken. Test at your own risk.

  40. Heads up: if you are building off our latest main branch and use vcpkg, be sure to reinitialize the submodule because you may encounter an error. To do so, run the following commands from the root of the source tree:

    $ git submodule deinit -f vcpkg
    $ git submodule update --init vcpkg

  41. 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! 😄