Bug 416 doesn't work like that, rather on the number of samples stored in the waveform. For example, if you have 14 hours of audio in the waveform @44100 Hz, that is "over the limit" of 2^31 stored samples that you can save as a single project. When attempting to reopen the project, the entire data (every single .au file) will be "orphaned" (but none missing).steve wrote:You may be starting to run up against this bug: http://bugzilla.audacityteam.org/show_bug.cgi?id=416
1 hour 4 minutes stereo at 96 kHz is about 750 million samples
If you process that file, for example if you normalize it, the number of samples in the project will double as Audacity copies the data so that you can undo the process. That will take you up to 1.5 billion samples. 2^31 is about 2 billion.
If you really need to use 96 kHz, try splitting the project in half before you start editing and see if that makes a difference.
But if you have 7 hours of audio and normalize it (which gives you the same number of .au files that you had with the 14 hour track), then save and reopen the project, it will reopen OK.
@Cwluc, I didn't see any of the posted files, so I am not clear what happened? What was the corruption after the edit - was it something other than the silenced audio that you later found further down the track?
You may in fact have been hit by a rare bug where projects don't save or reopen correctly, resulting in missing and/or orphaned block files and silenced audio. It is distinct from the 2^31 samples issue:
http://wiki.audacityteam.org/wiki/Relea ... n_projects
Note also from those release notes that 2.0.0 (to some extent) fixed an issue where:
These corrupt samples may not be easily visible (or even last long enough to be audible) unless you enable View > Show Clipping. However look at this image that you posted:Excessively high or corrupted sample values in the audio could corrupt exports from the start of the problem for the rest of the file, and could corrupt the rest of the project.
I assume the peaks were needle drops(?) but if that was some faulty peak recorded by your sound card it could possibly cause the problems you found.
Are you getting Audacity with ASIO support to compile/link without modifying the code? If so then we probably cannot claim any issues are related to the build. If you have been modifying the Audacity sources, then of course you haven't got much comeback.
Gale