Audacity Forum

Involving split-file Projects seems to not be the best, most stable way to do that. It may not seem like the best, most stable way when looking from the ruins of a broken project, but it's virtually universal for DAW type applications. Pick any of the big names: Cubase, Sonar, Logic, Reaper, Auditi...

The sample rate of the track is not relevant to the sample rate of the exported file. The sample rate of the exported file is determined by the "Project Rate", which can be found in the lower left corner of the main Audacity window. Example: If you have a project with 3 tracks, and: The fi...

Try importing the file that you exported, back into Audacity. If it plays OK in Audacity, then the problem is with the playback system. If it does not play correctly in Audacity (but the original project does), then the problem is with the exported file.

so you can only have one metadata thingie per recording? One set of metadata per project (a "project" being, everything that's in one Audacity window, which, when "saved", creates one AUP (Audacity Project file) and one "_data" folder). It would be difficult to manage ...

flynwill wrote: The "equalization" tools is probably the easiest to do this, build a EQ curve that is 0db from 14kHz up and -120 14kHz and down.

Like this:

Are you referring to Plot Spectrum (http://manual.audacityteam.org/man/plot_spectrum.html) or the track spectrogram view (http://manual.audacityteam.org/man/spec ... _view.html)?

The way I'd do it would be include only the metadata that is common to all tracks (if any),, then export all of the files, then use EasyTAG or MP3Tag to tag the files.

I'm pretty sure there is no Auto Save There is, but it's a machine readable file, not a human readable file. The very last thing you need on a borderline powered machine is for it to start managing a save cycle in the middle of a recording—or worse, an overdubbing session. I'd guess that's why it i...

The files are randomly named?? Why not name them sequentially? I don't know all the technical details, but I do recall that when block file writing changed from sequential numbering to partially random numbering, Audacity suddenly became much more stable and automatic data recovery improved immense...

is there any way to detect if any of the tracks are duplicated based on the audio "pattern"? There are "Music Recognition" (more generally "Content Recognition") applications such as Shazam and GraceNote, though I'm not aware of any Linux implementations. this 2.5 hrs ...