Source Clip BPM & Saving 3.4

To adjust the bpm of a clip to the project bpm you need to use %, most DAW just lets you set the bpm of the source clip that then fits to the project bpm.

You are using non destructive editing now, you should have an option to save just as a reference file (like .xml) to just reference the file locations and not save a massive big *.aup3 file that includes all the audio data.

A previous version of Audacity had an option to associate external .WAV files and such with the project. This became a problem when the user moved or deleted their .WAV files, and the feature was removed.

That assumes that the DAW knows what the actual bpm of the source clip is. Currently, Audacity does not know that, but I believe it is being worked on.

Not me. Maybe “You” are using non-destructive editing now, but “I” am using destructive editing. I have a full featured DAW for non-destructive editing, so I have no need of Audacity to do that, but I do use Audacity extensively for its original purpose as an audio editor.

In fact, not so much “a previous version”, but every previous version up through Audacity 3.0 had that (optional) ability — the new .aup3 project format eliminated it.

The biggest problem was, as @jademan said, it only worked with .wav files. Users who wanted to externally reference audio data often had it in some format other than .wav, meaning it would have to first be converted. If you’re going to convert to an external .wav file and then reference that, it makes way more sense to just import the audio data into the project so that Audacity has complete control over it.

Or externally modified the referenced .wav, which just made things unnecessarily difficult for Audacity.

Agreed, though this entry in the Audacity FAQ isn’t helping your/our case:

Is Audacity a DAW?

Yes. Audacity is a DAW just like GarageBand, FL Studio, Ableton Live, Logic Pro and others. Many musicians use Audacity to record and produce their tracks.

The Audacity team is always looking for new ways to improve the experience for musicians and music producers, so look out for new features in future updates.

“On demand loading” as it was called, was introduced by Michael Chinen in around 2008/9.
The motivation was, in Maichael’s own words:

…the ability to handle and do
simple edits on large files. Currently when you open a large file in
audacity, a modal dialog takes over the UI and makes me wait about 30
seconds for a 15 minute 16bit 44.1khz wave file on my G4 powerbook.

(I’ve just tested importing a 75 minute 16-bit 44.1kHz stereo WAV file on my budget laptop and it took about 12 seconds)

The feature was removed in 2020 in version 2.3.3, so there were three releases of Audacity 2.x without “On Demand” before the AUP3 format (Audacity 3.x). The main reasons for removing the feature was because of the common occurrence of “dependency can’t be found” when users inadvertently trashed their projects by moving, deleting, renaming or otherwise modifying external audio files required by the project.

The big thing that Audacity 3 introduced was the single file project format (.AUP3), which had been requested for many years (to solve the all too frequent “missing blockfiles” problem).

Now that Audacity is owned by a commercial company I think we can expect a bit more hyperbole in how it is advertised. Audacity is not “just like [insert name of DAW]”, at least not yet. DAWs typically support MIDI, virtual instruments, channel mapping, and other features that Audacity does not yet have. Also, DAW’s typically provide a much more flexible non-destructive workflow than Audacity provides, and many include grid editing, controller view, score notation and other integrated features.

It would be good to have an option. I use a 2TB library of recorded session musicians in wma and wav format, it starts using too much hard drive space if you render all the files to new wav files unnecessarily. I can script Reaper to write all the sections used in Band In A Box as wma or wav (or flac aiff mp3 etc) without having to render tracks down to wavs on the hard drive then import them. Reaper plays all the formats direct without decompressing to wav first, so no new files are created.
I haven’t looked at Audacity’s scripting yet to see if I can do the same using wav ? but how it works now it would have to create a copy of the whole file of each section that would be massive.
I’m here as I watch the new video “Audacity 3.4 - New Musical Features!” and they said you can come here and help improve it.


“A new file format absolutely is coming in the future and being able to do that would be a requirement from my side. It’ll be a while until that happens though, we have an Audacity 4 to make first.”