Win10/1.3.1Corrected: Win 10, Audacity 3.1.3
I respect Audacity enough to have faith that Checkpointing has a use, but from time I am puzzled about the time it takes, as well as the reason for its existence.
Today, as a listener of an audiobook (82 MP3 files in a Zip file) I am using (Tools, Apply macros, Palette, …) a one-line macro to remove a persistent hum from all 82 tracks.
As each track of the 82 tracks is processed, a little window pops up announcing a delay:-
I say to myself, if the checkpoint is to secure the integrity of each track, then I care about that, but if the checkpoint is there to secure the integrity of the project, then I could do without it, because once all 82 tracks are NoiseReduced, I shall close Audacity and discard the project.
I see this pop up too when I am completing a recording, but after a two- or three-hour session of reading text and editing my audio, five seconds is not a big deal.