I left my computer recording overnight and have a 25h recording, after stopping the recording, I considered amplifing but decieded to do it later (clicked cancel before starting), I attempted silence removal but stopped that because I couldn’t wait 1.5h (cancelling did not cause a hang), It only hung when I pressed “fit project” zoom, I decided to shut down the computer so I saved and exited. The next day I loaded the save file and it says that 30,000 block files were orphaned.
For some reason “delete” was there as an option, and makes it tempting to press by assuring the user that a block contains only a little bit of information – it was still able to say that even when 100% of the blocks were not loaded (It does not show basic statistics: how many blocks the project uses, how many were loaded or how many that were not found – only how many orphans). The log window was updated so fast listing the orphans, it crashed my graphics card (not that hard to do on this machine, a standby cycle fixes it).
I assume it means it never recorded block order, existance etc, the block’s date stamp appears to give order information. Apparently Audacity 2.02 is not designed to handle this kind of scenario – it does not have an option to “load orphans sequences in a new window” (or in current window as a concurrent soundtrack) as one of the options, using any of the “manual recovery” processes automated. Or let us load audacity data in the file menu (“raw data” does not seem to be it), cannot drag the folder in either. Why is audacity v1.2 “no longer supported”, yet the methods used for data recovery (as old as 1.2) still are good enough? Downloading a third party program for a simple rename task is very dodgy, especially when you can do the timestamp query and sorting in-code.
If you consider the mentioned problems of doing a recovery, solutions of varying value can be applied in audacity to make the process much easier:
Make it easier to fix stereo sound:
*With 3D video, the second image is encoded in the second half of the video. you can do the same with the AU files.
*If wanting to deal with date stamps only, the first piece of the left channel and last of the right channel can be recorded 1.25s shorter, so that the files are written to the drive one at a time rather than in pairs.
*(removed, I suggest two replacements later)
Fixing block order:
*perhaps: rename the files at each save, or: modify the modify/access datestamp to show the file’s order or position in the recording. (the modify/access datestamp can show the next/last save, this will assist in recovery if there is a power outage during the save)
*you have plug ins – use them! Allow plugins for sorting the data. Perhaps study the waveform of the start/end of each block (dc level, fourier transform, etc) and then match the frequency profiles and/or the phase of a few frequencies between the files - not unlike a jigsaw puzzle. The only time a mistake could happen is if the L/R blocks were recorded to disk together and the recorded material switched between mono and stereo sources.
*test-load the save file. Do a quick pass to see if the file is reloadable, the sound data is somewhat identical, or if all the blocks that were required were reloaded. If it fails (as in my case), ask if user wants to try saving as parts (if it was the file length that broke it, allow loading of parts), test each against original.
*As for more modified projects, (since save is obviously untrustworthy) perhaps do not modify the original file, instead record milestones, load the last milestone when user loads. If the milestone is corrupted, ask if the last milestone is sufficient (it can be a bit holey if some of the unneccessary blocks were removed, but that can make re-editing easier) and mention orphans that were added in the broken milestone. Half a pie is better than none. Older milestones could still be useful, allow deleting of them too (but milestone data is small compared to the sound data).
My recording is not exactly important - if audacity fails for my less important recordings, why should I trust it for the more important stuff? Even if I was able to get my recording loaded somehow, I am reluctant to save it again because obviously it could fail again. Since I cannot use audacity for mission critical stuff (because this orphan issue is not taken seriously), what programs could be recommended?