A quick update to this, as I continue to struggle through the project I have in Audacity. I find that if I am editing and the CPU rockets, I can normally recover by undoing the last change I made (Ctrl-Z), then the CPU returns to normal. I think there is an issue when I delete large sections of audio, although sometimes just crossing some little boundary seems to be a problem.
When I have a damaged project, I've been able to reassemble all the parts by pasting them in the order listed in the project file, manually one by one into one complete file. The audio data itself does not seem to be damaged. The project file does not look strange either, but on opening it will force the CPU to 100%. If you have the same problem as me, try the Ctrl-Z trick to see if you can recover from an editing problem that forces up the CPU and damages the project. -- Audacity uses 100% CPU on opening any file dialog https://bugs.launchpad.net/bugs/250367 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
