Audacity 4: a glimpse of a new, more modern UI for the free audio editor
Discussion Activity
Moderate engagementFirst comment
11m
Peak period
8
Day 1
Avg / period
4.3
Based on 13 loaded comments
Key moments
- 01Story posted
10/6/2025, 9:04:07 PM
43d ago
Step 01 - 02First comment
10/6/2025, 9:15:29 PM
11m after posting
Step 02 - 03Peak activity
8 comments in Day 1
Hottest window of the conversation
Step 03 - 04Latest activity
10/8/2025, 11:41:02 PM
41d ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
When I decided to record an audio version of my book, I started with Audacity. But it quickly failed me when I started losing track of what files I was using, and if I deleted a file from the timeline, it was impossible to track what was what. All this because Audacity doesn't have a media manager. Instead, you have to open a folder on the side and manage media yourself. I've written a blog post about it, didn't get much traction. But as of a few days ago, one of the developers commented that a media me is "on our shortlist of new features to include".
I am really looking forward to version 4.0, I hope Audacity gets its Blender moment.
Linear vs non-linear is kind of hard to describe in the modern era, we aren't splicing tape anymore, the original audio is still safe on the disk unless you overwrite it. It's really just that Audacity doesn't give you the kinds of features that a true non-linear DAW has. There's no reason why it couldn't have those features, it's just not the focus of what Audacity needs to be (simple audio recording and editing).
The DAW did not solve anything, it just choose a different set of problems which are less of an issue for the tasks the DAW is designed for but can be fairly irritating if the tool you need is a capable editor. Something like recording an audiobook can be done effectively and efficiently in either a DAW or an editor and I can make a case for either. In the case of an audiobook, my choice would be to assemble it in an editor and polish it off in a DAW.
This isn't how the vast majority of operations work in the two DAWs I'm the most familiar with (Ableton Live and Logic Pro) work, most actions are non-destructive and don't result in extra files on your computer (e.g., the original file is referenced, and edits are applied on top of that without modifying the underlying audio file [a la Lightroom for photos]). There are certainly situations where new audio files are written, but it's usually crystal clear when you're doing so.
For the record, I agree with your overall point. DAWs abstract away a lot of the details of the underlying audio files, and there's definitely space for tools like Audacity that are designed to edit audio files staying closer to their export formats. So just clarifying that I wouldn't phrase the downside of DAWs (or at least not all DAWs) around creating a bunch of extra files (although I'd be curious to hear which DAWs actually do work that way [i.e., create new audio files based on edits], just for my own learning).
Making a new file for a reverse makes sense, only simple/efficient way to do that without a copy is to dump it backwards into a buffer but that eats RAM. I have only started in on doing realtime audio programming but I think to just read the file backwards in realtime would require you to create a counter specific to each reverse? But I am not much of a programmer and just starting in on the audio stuff, I could be missing something obvious.
Also I can do all of these options in an NLE like Adobe Premiere with video (i.e., I can split, join, reverse, etc... without creating any new media files), why wouldn't a DAW work the same way?
I don't know much about video but, video editing is simpler, you probably have a GPU to take a good chunk of the load off of the CPU and latency is less of an issue. How often do you do you have two dozen video tracks playing at once with each going through a dozen effects while trying to record a few more video tracks in real time all on your CPU?
> I don't know much about video but, video editing is simpler, you probably have a GPU to take a good chunk of the load off of the CPU and latency is less of an issue. How often do you do you have two dozen video tracks playing at once with each going through a dozen effects while trying to record a few more video tracks in real time all on your CPU?
I wouldn't characterize video in general this way (although NLEs maybe), e.g., a couple of dozen layers with effects in Adobe After Effects is common, and After Effects utilizes more CPU than GPU generally. After Effects can do all these operations without creating new files as well (although it has extremely aggressive caching both in RAM and on disk). (And real-time isn't as much a priority for video of course.)
I think this is partially an implementation detail, I think Ableton probably creates the extra files to help a bit with live performance since that's their focus. Whereas Logic Pro is a more generalist DAW. There are options to deliberately create new files, any time you want, in both (same with NLEs and After Effects).
1 more comments available on Hacker News
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.