- Current version of audacity for mac how to#
- Current version of audacity for mac install#
- Current version of audacity for mac software#
- Current version of audacity for mac code#
- Current version of audacity for mac license#
Modernize it? What does that mean? Remove all the keyboard shortcuts, De-emphasize the mouse and add so many gestures that every single touch activates some unexpected menu item? That’s what everyone else seems to think of as a modern UI.īring it to a larger audience? So dumb it down then. “The company says their goal is to modernize the 20 year old GPLv2 program and bring it to a larger audience” No-kids policy? Like anybody follows the EULA. Telemetry? Well how much personal information are you giving it? Are you putting credit card numbers in the meta data of your audio files? You’ve all been focusing on the wrong thing.
Current version of audacity for mac code#
This also does not address the changes to code that has been submitted and the ownership and use of that.
Current version of audacity for mac how to#
I think the new owners of the name have shone the direction they want to go in and are now working out the roadmap for how to get there, perhaps more slowly. I suspect the year after when there were no free vouchers, if you too the time to call, they would forgo the fee, but I also suspect in a few years no one would call anymore and by that point in time they would figure they could afford to piss off the last of the hold outs by not being “free”. If they changed all at once many people would make noise, but this was a clever way to dilute the change. I canceled the card, it did not take a rocket scientist to see that the next year the voucher would be gone.
They were happy to tell me that there was a voucher for that fee in the newsletter they were sending out. One year I got a charge on my bill for a $35 annual renewal fee for the card, so I called them. Years ago I had a “forever free” credit card from my credit union.
Current version of audacity for mac software#
Posted in News, Software Development Tagged audacity, privacy, privacy policy, telemetry Post navigation
Current version of audacity for mac license#
Unfortunately the issue of Audacity’s inflammatory Contributor License Agreement (CLA) has yet to be resolved, meaning recently christened forks of the audio editor dedicated to preserving its GPLv2 lineage are unlikely to stand down anytime soon. Those worried their FOSS audio editor of choice would start spying on them can rest easy. Muse Group promised to revise their plans for adding telemetry to Audacity, and judging by the new Privacy Policy, it seems they’ve done an admirable job of addressing all of the issues brought up by the community. The clause about working with unnamed law enforcement agencies has been deleted, as has the particularly troubling age requirement.Ĭredit where credit is due.
Current version of audacity for mac install#
It’s further explained in the GitHub post that the automatic update feature only applies to official binary builds of Audacity, meaning it will be disabled for Linux users who install it through their distribution’s package repository. The new Privacy Policy makes it clear that Audacity won’t be collecting any user data, and what little personally identifiable information Muse Group gets from the application when it automatically checks for an update (namely, the client’s IP address) isn’t being stored. That sounds reasonable enough, but why where these same teams not consulted before releasing such a spectacularly ill-conceived draft?
Project lead Martin Keary, better known online as Tantacrul, says the team had to consult with various legal teams before they could release the revised policy. But it’s still difficult to understand why Muse Group publicly posted such a poorly constructed version of the document in the first place. Ultimately, the new Privacy Policy bears little resemblance to the earlier draft. It seems much of the problem can be attributed to an over-analysis of the situation with the company inserting provocative boilerplate protections (such as a clause saying users must be over the age of 13) that simply weren’t necessary. The announcement also came with an admission that many of the key elements from the draft version of the Privacy Policy were poorly worded and confusing. In a recent post to Audacity’s GitHub repository, Muse Group unveiled the revised version of their much maligned Privacy Policy. An already precarious situation has only been made worse by a series of PR blunders Muse Group has made over the last several months.īut for a change, it seems things might be moving in the right direction. The company says their goal is to modernize the 20 year old GPLv2 program and bring it to a larger audience, but many in the community have questioned whether the new managers really understand the free software ethos. Regular readers will likely be aware of the considerable debate over changes being made to the free and open source audio editor Audacity by the project’s new owners, Muse Group.
0 kommentar(er)
