These videos by Tantacrul are sooooo good to watch, from the perspective of making product decisions for a software product. They are really well made, too
The privacy policy now reads
For the purposes of this Notice, MuseCY SM Ltd., a Cyprus company with an address at Spyrou Kyprianou, 84, 4004, Limassol, Cyprus (“Audacity Team“, “us“, “we“, or “our“) acts as the data controller for the personal information that is collected via the App and through the use of the App, as further outlined in section 2 (“personal information”). As a data controller, the Audacity Team makes sure that any processing of your personal information complies with applicable data protection law, and specifically with the General Data Protection Regulation (“GDPR”).
I know accessibility for low vision users was mentioned, but I wonder, with all these changes, whether version 4 will be accessible to screen reader users, and if so, whether any major features will nevertheless remain inaccessible.
We're using the framework my team on MuseScore Studio created for the UI in Audacity. This allows us to port over the significant amount of screen reader support we built over there too.
We'll need to spend time making sure it's applying correctly to every corner of the app - but when it's done, the app will be far more broadly supported than V3.
I would guess accessibility will be similar to the current version of MuseScore since the same company (Muse Group) is leading both open source projects. So maybe look at MuseScore.
I don’t know when it happened, but earlier in the week a non-tech member of staff, who was trying to install Audacity, called me really confused because it was asking about installing and then saving to some sort of cloud storage that was being pushed during the installation process. I personally haven’t used Audacity for a couple of years, so the cloud storage stuff added in 2024 is new to me showing up during install. It appeared again in the choice of save locations even after rejecting it during install and I have no interest in someone calling me in two years asking where their files are after the cloud storage shuts down or gets paywalled. For 95% of casual users looking to just split/combine/trim/etc some basic audio files, I’m just gonna tell them to use Ocenaudio.
I think Musehub.com is a sister project within Muse Group that helps mitigate the cost of paying professional developers to work on Audacity and MuseScore.
In the case of Muse Score it also provides a marketplace for third parties.
I don’t use it but I can see why it exists…ordinary folks expect cloud services these days. And if I had a different use case, it would help me get stuff done.
But for what it’s worth with Audacity I don’t see it pop up as a location on my computer.
having worked with wxwidgets only a tiny bit, things simply don't look or even work the same across operating systems with wxwidgets. It tries to use native widgets wherever possible, but that also means things behave slightly differently across systems, and if the toolkit doesn't provide a matching widget, it sometimes just uses the next best thing. All this also makes it rather hard to style things in a way that looks good. It's good for simple applications but you run into the limitations quickly if you actually try to use it cross-platform in my limited experience.
Readit News
https://github.com/audacity/audacity
The application privacy policy is here
https://www.audacityteam.org/desktop-privacy-notice/
Deleted Comment
We'll need to spend time making sure it's applying correctly to every corner of the app - but when it's done, the app will be far more broadly supported than V3.
https://en.m.wikipedia.org/wiki/Muse_Group
In the case of Muse Score it also provides a marketplace for third parties.
I don’t use it but I can see why it exists…ordinary folks expect cloud services these days. And if I had a different use case, it would help me get stuff done.
But for what it’s worth with Audacity I don’t see it pop up as a location on my computer.
A lot of projects propose cloud storage without trying to force it on you. More the How than the What which is questionable here.
As someone who's never worked with either (only web UIs), I thought this would be a good chance to understand: why is wx bad, what makes Qt good?
More, what is better for this specific project at this point in time given the objectives…it’s just an engineering judgement.
WXwidgits got Audacity through twenty odd years of intense development and helped millions of users.
Dead Comment