Today's Flatpak update just updates dependencies, but we're working on another update that also updates another we missed, plus maybe reducing the size of the Flatpak too by a little (we're disabling more parts of wxWidgets again).

libmad 0.16.5 has been released! This new release brings CMake 4.0+ support without warnings and a few other fixes. Check out the full changelog here: https://codeberg.org/tenacityteam/libmad/releases/tag/0.16.5

In recent times we've seen a brief spike in interest in #Tenacity. While we're carrying along the best we can, if you are also interested in contributing, we would greatly appreciate that too! We have quite a bit of work that needs to be done, and the more we can get community input and work on things, the faster we'll be able to move things along! 😄

Update on this work: previously, the color dialog would always choose the theme default waveform color. While it still is, if that color is chosen, the waveform color is properly set to use the theme's colors instead.

We also adjusted the RMS color to be darker. Hopefully it isn't too dark, but let us know what you think! :D

Once this work is complete, that's when the rewritten theme system is next, as we're unfortunately getting rid of extra theme-provided waveform colors (i.e., Instruments 2-4 in the current UI).

We've finally made progress in a basic feature we said we'd implement: user-selectable waveforms! Check out the work-in-progress PR here: https://codeberg.org/tenacityteam/tenacity/pulls/793

What remains to be done is if there's anything we should further include for better backwards compatibility with Audacity (3.x). Right now, custom waveform colors in Tenacity will not be shown in Audacity, and vice versa.

Quick poll: do you want per-track waveform colors or per-clip waveform colors? This decision would appear in 1.4.

In either case, colors would be user selectable, just one would be per-track and the other per-clip.

We originally wanted to keep support for Windows 7 & 8.1 in Tenacity until after 1.5. However, because VS 2026 doesn't officially support targeting Windows 7 & 8.1 anymore, that means we have to bump Tenacity's system requirements. Had this not been the case, Windows 7 & 8.1 support would've continued for a little while longer.

Anyways, we'll keep you updated on new developments as they come! 😄

We've finally settled on a direction with #Tenacity in response to Audacity 4 coming out: for the most part, we're not changing our direction.

However, we will be dropping support for Windows 7 & 8.1 starting in 1.4, meaning 1.3.x will be the last (actually only) to support Windows 7 & 8.1 (except 1.3.5, which will be fixed). We may also push some features back, but major changes will still happen in 1.4 that were previously planned.

Our DJ contest is still active and the deadline to submit your video is in 20 days!
Full details: https://mixxx.org/news/2026-08-23-25_years_of_mixxx_dj_contest
DJs of all styles, genres and skill levels are welcome to participate.

DJ Your Way, take the audience along and entertain us!

RE: https://floss.social/@tenacity/117232062501251967

It looks like quite a bit of people liked this post, and it got a good amount of boosts so far. Rather than responding under Tenacity's fediverse account, I'll respond as me, and for myself.

I personally want to continue Tenacity on the direction it's currently going. I felt that there's been a lot of effort and work put into it that I would rather keep and not give up. I've had plans for Tenacity for several years at this point, and I still intend to carry them out, even if they take a bit of time to do so. To me, Tenacity doesn't feel like just Audacity minus telemetry, cloud features, and AI plugins. Having seen different people contribute to different parts of Tenacity, I know there's a lot more than just removing those features. I know that it will still be a lot more once we get more things completed. It will take time, but it's my dream to get there, and we'll make it happen.

Of course, we could always do another rebase, just like we did with 1.4. However, Audacity 4 is a completely different program, and I would assume that a lot of things Tenacity already has would need to be rewritten at least to a heavy degree. Did we lose work with the Audacity 3.7.x rebase? Possibly, but it's my intent to merge anything lost back again. That's also why I don't want to do another rebase too, since both Tenacity's and Audacity's respective histories are too divergent at this point.

So overall, I personally want to continue the direction Tenacity's currently following, because awesome people have contributed to Tenacity that make it more unique.

With all the above being said, I would still like to talk with other maintainers and contributors, but I think we'll be on the same page.

Many are probably wondering what our future will be now that #Audacity 4 has been released.

Well, unfortunately, it's pretty boring: we'll continue on like before, but we'll review this and we'll make announcements on important things should they come.

For Windows 8.1 users, you do NOT need to perform the above steps.

While the workaround is a simple enough compromise, our (previously updated) support policy regarding WIndows 7 and 8.1 remains unchanged, and starting in 1.5, we will only support Windows 10 or later.

Also, we remind you that modifying program files can go wrong and that this is for advanced users only. We'll address this in the next stable version of Tenacity we release.

If you are feeling adventurous and want to get Tenacity 1.3.5 working on Windows 7, you can perform the following steps:

1. Go into Tencaity's program files (likely under "C:\Program Files")
2. Move the "vcruntime140.dll" and "vcruntime140_1.dll" files to a safe location
3. Install the Visual Studio 2015-2022 C++ Runtime (skip this step if you already have it)
4. Launch Tenacity and should be good to go!

This is a temporary work around until we figure this out in a later stable release.

City of Munich pays #libexpat (a fast streaming XML parser) maintainer for 6 months as part of their Open Source Sabbatical program.

„Technically, I am being employed by digital@M now for of up 6 months with a regular working contract, including cancellation by either party, remotely from home. There is plenty to do.“

Thank you, #Munich.

https://blog.hartwork.org/posts/libexpat-city-of-munich-open-source-sabbatical/

If none of those options work for you, and you cannot obtain new hardware, which is very understandable given today's times, you will still be able to use older versions of Tenacity that do support these platforms. Just understand that you will not get any further fixes for bugs or security vulernabilities, in addition to receiving no support whatsoever. If you want to fix things, you're on your own, unfortunately :(

If you are still on Windows 7 or 8.1, we recommend the following:

* Upgrade to Windows 10. Although Windows 10 went EOL Back in October 2025, ESU updates are still available until October 12, 2027.

* If you can, switch to Linux. Chances are, your hardware likely isn't supported by Windows 11 if your computer originally came with Windows 7 or 8.1, and if you can't or won't upgrade to Windows 10, then switching to Linux may serve you better than buying new hardware.

While we try to avoid raising minimum supported versions of OSes, libraries and dependencies, build tools, and plenty of other things unnecessarily, at some point, we will be forced to raise them. For example, if the latest build tools drop support for older platforms, then we can no longer support those older platforms. Of course, we don't have to use those newer build tools, but since we want Tenacity to work on modern systems, that is a must. It's also something that requires maintenance too.

Hey everyone! We have an update on Tenacity's support for Windows 7 & 8.1 going forward, and for users of those platforms. you won't like it.

To get to the point, Windows 7 & 8.1 support will have to be dropped after 1.4.x. The original plan was to drop support for them after 1.5.x, but we're making it sooner because the latest Visual Studio build tools no longer support targeting Windows 7 and 8.1. We learned this the hard way because of a bug with 1.3.5, where it won't run on Windows 7.

Anyways, if you want to help us out also, we now have another way: Open Collective! Check out our #OpenCollective here: https://opencollective.com/tenacity