Audacity 4 arrived on September 3 with the largest interface rewrite in the editor’s history. Qt replaces the old UI framework. Clips can be selected, grouped, stretched, and moved with fewer rituals. Workspaces reorganize the toolbars. Track meters finally live beside the tracks. The waveform editor looks like software made in this century.
The release also makes Audacity’s ownership structure legible. Muse Group can keep the editor under GPLv3 while building the default download, effect marketplace, cloud destination, and product roadmap around its own commercial system. The source license still matters. It guarantees that another group can carry the code away. It cannot make that alternative the path encountered by a beginner searching for an audio editor.
a serious editing rebuild
The technical work deserves credit before the governance argument eats the release whole. Audacity 4 adds direct clip selection, multiselect editing, clip groups, free movement between compatible tracks, dedicated splitting, alignment guides, sample-boundary snapping, improved looping, per-track meters, movable panels, and saved UI workspaces. The application now supports native high-DPI rendering through Qt. Official Windows builds gain ASIO playback and recording.
The editor also replaces several old interaction modes with contextual controls. Clip gain exposes envelopes. Zooming to individual samples exposes drawing. Holding S exposes splitting. Delete, cut, and paste each offer variants that either preserve a gap or move later material. Those decisions reduce tool-state archaeology, one of Audacity’s oldest taxes on casual use.
Peter Kirn’s first run for CDM found the application fast and the new editing model substantially easier to use. He also verified a useful escape hatch: the standalone application bundle remains available below the recommended MuseHub download and can be installed offline. The ecosystem layer is prominent, but it is currently avoidable.
the missing tools define the migration cost
A rewrite this large ships with a ledger of absences. Audacity 4.0 lacks Time Tracks, Note and MIDI tracks, the Mixer, Macro Manager, scripting pipes, VAMP and LADSPA hosting, and play-at-speed. The release notes also acknowledge missing export and rendering functions, analyzers, and effects.
The first replies in the official launch thread immediately found practical consequences. One user could not locate Change Speed and Pitch. Another found that exporting every track to separate files had disappeared; the project already has an issue tracking its return. These are working habits, automation paths, and batch operations. A cleaner clip model does not compensate for a production pipeline that depended on scripting or multi-file export.
The project-format boundary adds another one-way door. Audacity 4 opens .aup3 projects and converts them to .aup4 without modifying the original, but converted projects cannot be saved back to .aup3. That is sensible engineering for a rewritten data model. It also means collaboration and rollback require keeping the old project intact and deciding who crosses the new format boundary.
the license governs code, the product governs arrival
Audacity’s official release page places “Project paradise” beside direct audio.com publishing and advertises thousands of free and paid plugins, samples, and one-shots through MuseHub. The same page correctly states that the editor remains free, GPLv3, auditable, and redistributable. Both conditions can coexist without contradiction.
GPL controls what recipients may do with the covered source. It does not guarantee equal placement on a download page. It does not supply a competing marketplace, cloud account system, signing pipeline, release cadence, onboarding funnel, or support budget. A fork receives legal permission and a mountain of operational work.
Tenacity demonstrates the distinction. The volunteer project offers prebuilt releases, source on Codeberg, scripting through Nyquist and named pipes, VST/LV2/AU support, and packages for several operating systems. It is a genuine exit, maintained outside Muse Group’s commercial bundle. Yet Audacity owns the familiar name, the mainstream search result, the recommended installer, and the new interface investment. Forkability prevents total enclosure. It does not create symmetry.
interface quality can strengthen the center
Open-source politics often treats a polished interface as uncomplicated progress. Audacity 4 shows the sharper version. Better editing lowers friction for millions of users. The same improvement increases the gravity of the official build, especially when the official build also routes users toward a marketplace and cloud service.
That does not make the rewrite suspect. It makes interface work a form of distribution power. A user rarely chooses among source trees. They choose the application that installs cleanly, recognizes the microphone, explains the timeline, loads the project, and gets out of the way. The organization financing that path controls the practical meaning of “Audacity” even while the repository remains legally portable.
The useful test for future releases is concrete. Keep the standalone installer visible. Keep offline editing complete. Make cloud and marketplace services optional in behavior as well as policy. Publish migration limits before users convert projects. Restore scripting, batch export, and specialist plugin formats without forcing those workflows through a commercial account layer. Preserve a build path that downstream packagers can reproduce without proprietary infrastructure.
Audacity 4 is a better editor with an honest escape hatch. The long-term question sits in the distance between those two facts: whether the escape remains usable after the official route becomes cleaner, richer, and increasingly connected.