Audacity….for the double lose
Jan 29
So when Shade wrote his post the other week about Audacity crapping out on him in the middle of the show, I’ll admit that I chuffed a little bit. Clearly it must’ve been an issue with his computer and not the audio editing darling of the open-source community. I mean, there have been 38 developers putting in almost as many person years in creating this widely used application and working to make it stable. Nightmares of being chased down dark alleys by machete-wielding unit and regression tests surely must’ve haunted a few of these coders until they delivered an app which was so stable it could take a bullet, catch it in it’s teeth, spit it back at you, and then karate-chop you in the throat.
You would think…..
So imagine my shock when in the middle of my show last week Audacity gave me a whiny error message and promptly closed, taking about 1 1/2 hours of my set along with it. After checking outside, to make sure the universe wasn’t unraveling at the seams, I came to the sudden realization that Audacity was a steaming pile of shit….leaving my faith in open-source and humanity both irreparably shattered.
This is my long-winded way of telling you not to expect a dubstep podcast from last week. My apologies.








I TOLD YOU!
I honestly think the program might be fine for handling smaller audio files but when you start dealing with 1 or more hour long files, it chokes hard.
Just be a man and switch back to Soundforge like the rest of us.
“Just be a man and
switch back tosteal Soundforge like the rest of us.”Ahh, that’s more like it
*fixed
(-illeffect)
oh lame…strikethroughs don’t work? How un-standard.
Strikethroughlets see…Use the <del> tag, you nonstandard fuck.
Bias Peak FTW!
Wavelab and SF for you Personal Computer guys.