Note on the New Community
Hey everyone! It turns out we made a mistake in the community name. It's actually @tenacity@programming.dev.
We apologize for the confusion.
We are the creators of Tenacity, the sparkling new, easy-to-use, privacy-friendly, FLOSS, cross-platform audio editor and recorder based on Audacity. We also maintain libmad and libid3tag forks, which most Linux distros are adopting.
This account is managed by various contributors.
Website | https://tenacityaudio.org |
Main repo | https://codeberg.org/tenacityteam/tenacity |
Need Help? | https://matrix.to/#/#tenacity2:matrix.org |
Announcements Mailing List | https://lists.sr.ht/~tenacity/tenacity-announce |
Note on the New Community
Hey everyone! It turns out we made a mistake in the community name. It's actually @tenacity@programming.dev.
We apologize for the confusion.
Ok, another question: if we were to fork #MuseScore: would you join us to help develop it? One program is enough, but two is an even heavier load.
I should stop playing with this idea before it's too late. (It might already be) - @gperson
Honestly, if we had more contributors, we could be more powerful. ๐
๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐
Here's a reminder that this exists: https://github.com/Xmader/musescore-downloader/issues/5
Look, for legal reasons, we don't condone piracy. However, this response appears to be...a bit much, to say the least. We'll let you spread the word on this.
@TenacityAudio It seems like the mention didn't work on Mastodon's end. Guess the community profile hasn't federated enough quite yet.
Also the community icon might get a bit confusing. We'll update it a little later.
This Community Has Migrated
Hey everyone! This community has migrated over to https://programming.dev/c/TenacityAudio, or @TenacityAudio@programming.dev. Please follow that community instead of the old one.
Thank you for your understanding.
Sent a pull request to Audacity fixing a crash bug I'd been running into frequently. The cause was an out-of-bounds memmove. Classic C++ areas.
Anyway I got a fucking copilot review on my PR which left two comments, both completely wrong, one of which suggesting I reintroduce the out of bounds memory access. I'm furious!