FA+
Shop
Issue resolved... and I feel stupid.
4 years ago
General
Okay, so here goes. The issue with Audacity has been fixed. And the fix itself was so stupid that I feel foolish for not getting it on my own.
I had been working on stuff for the next episode of Arturos Academy last week, and had done all of my recording then. Several days later, I started edit work on it. Everything seemed fine. A couple days into the edit workl, I noticed that ANY editing would cause the program to become unresponsive. At first, I thought the issue was because I was using up a lot of my net bandwidth for redownloading games onto my new Switch (a stupid thought, in hindsight, since that has absolutely nothing to do with Audacity), but the issue still continued even when my downloads were done.
So the next thing I tried to do was copying all the tracks AT ONCE (This fact is important) to a new audacity file, saving to a new place, then doing edits from a new one. Same issue.
Then I tried a fresh installation of Audacity. Still no change.
By this point, I had taken notice of the fact that my cpu was running at 100% processing speed. I became worried when I saw this, because the last time I saw it, it was what forced me to have to go through several hours, with the help of my friend
timidgrizzly to reformat the computer and create a new partition on a different drive because the SSD in the computer had failed. I became disheartened and went into a panic attack over it. This though, turned out to be some sort of fluke though, because within half an hour, it was back to normal, and Timid even confirmed that there are cases where the PC will do that for extended periods.
This left me falling back on my thought something was wrong with Audacity, but I couldn't, for the life of me, figure out what. Timid and I tried a few different things to see what would happen. Tried doing what I mentioned above, which produced the same result, but it was done to confirm it was still happening. We then tried moving the tracks over ONE AT A TIME rather than all at once. This seemed to work, as the tracks would transfer over without Audacity going unresponsive, but the moment I tried to do ANY actual editing on the files, even in the new Audacity window, it would lock up again.
As a final resort, Timid suggested EXPORTING the tracks, so the tracks were on my computer directly, then making a new Audacity file, then bring the tracks in that way, ONE AT A TIME.
That, surprisingly, did the trick. They all imported in properly, no locking up, no unresponsive program, and I could edit/save the file and things were back to the way they should be.
So yeah.... after all that... after a depression episode and a panic attack, and my mood getting worse by the day, everything is FINALLY back to the way it should be.
I should not have let it get me that upset, but I tend to panic when my computer starts showing problems, but the fact that the answer to the issue was so simple, only makes me feel stupider.
EDIT! I almost forgot. One of my thoughts on what I think actually happened is that one of the tracks within the file became corrupted during the occasional brief power flash we get when it rains here sometimes. Enough of an issue to cause the power to quickly blink off then back on again. Not enough to fully knock the power out. I can't say for sure, but I believe this MAY have happened during one of my edit sessions and I just didn't notice it.
I had been working on stuff for the next episode of Arturos Academy last week, and had done all of my recording then. Several days later, I started edit work on it. Everything seemed fine. A couple days into the edit workl, I noticed that ANY editing would cause the program to become unresponsive. At first, I thought the issue was because I was using up a lot of my net bandwidth for redownloading games onto my new Switch (a stupid thought, in hindsight, since that has absolutely nothing to do with Audacity), but the issue still continued even when my downloads were done.
So the next thing I tried to do was copying all the tracks AT ONCE (This fact is important) to a new audacity file, saving to a new place, then doing edits from a new one. Same issue.
Then I tried a fresh installation of Audacity. Still no change.
By this point, I had taken notice of the fact that my cpu was running at 100% processing speed. I became worried when I saw this, because the last time I saw it, it was what forced me to have to go through several hours, with the help of my friend
timidgrizzly to reformat the computer and create a new partition on a different drive because the SSD in the computer had failed. I became disheartened and went into a panic attack over it. This though, turned out to be some sort of fluke though, because within half an hour, it was back to normal, and Timid even confirmed that there are cases where the PC will do that for extended periods.This left me falling back on my thought something was wrong with Audacity, but I couldn't, for the life of me, figure out what. Timid and I tried a few different things to see what would happen. Tried doing what I mentioned above, which produced the same result, but it was done to confirm it was still happening. We then tried moving the tracks over ONE AT A TIME rather than all at once. This seemed to work, as the tracks would transfer over without Audacity going unresponsive, but the moment I tried to do ANY actual editing on the files, even in the new Audacity window, it would lock up again.
As a final resort, Timid suggested EXPORTING the tracks, so the tracks were on my computer directly, then making a new Audacity file, then bring the tracks in that way, ONE AT A TIME.
That, surprisingly, did the trick. They all imported in properly, no locking up, no unresponsive program, and I could edit/save the file and things were back to the way they should be.
So yeah.... after all that... after a depression episode and a panic attack, and my mood getting worse by the day, everything is FINALLY back to the way it should be.
I should not have let it get me that upset, but I tend to panic when my computer starts showing problems, but the fact that the answer to the issue was so simple, only makes me feel stupider.
EDIT! I almost forgot. One of my thoughts on what I think actually happened is that one of the tracks within the file became corrupted during the occasional brief power flash we get when it rains here sometimes. Enough of an issue to cause the power to quickly blink off then back on again. Not enough to fully knock the power out. I can't say for sure, but I believe this MAY have happened during one of my edit sessions and I just didn't notice it.
We all feel confused and overwhelmed when we are outside the solution or knowledge bubble of an issue. Outside the knowledge bubble, it is not obvious; all is unknown, all is confusion. Once we are inside the knowledge bubble, the solution seems obvious. Only changing one thing at a time and testing can carry us from outside the knowledge bubble to inside the knowledge bubble.
Such is the journey of leaning in any field. This journey precedes the video game and is one of the greatest of games to play. Your reward is that good feeling when you are inside the knowledge bubble of an issue and understand the issue enough to manipulate it. Defeating the game boss of ignorance and gaining the treasure of knowledge is a wonderful feeling.
Just a thought on a different perspective.
TG