Crash Issues

[londonsoundlab]

Hi everyone,

I will continue to comb the threads here for an answer but I wanted to get this question out there.

I am new to audacity and chose to use it because it is great for batch editing using Chains

My friend on PC is able to batch process 2000 files without a crash on the latest build on my mac pro tower running mountain lion, if i do over 30 files it crashes every time.

i have many vsts running in my other audio software. My gut is saying this is the issue. Audacity imported all of my vsts. Im wondering 1. if there is a way to not use any plug ins - to bypass this? and 2. maybe there is an older version of audacity that will work better?

Unfortunately I am on a deadline and need to get this work done. I will be here at my computer all day if anyone can help me?

Thank you all in advance for the help

[kozikowski]

Audacity is a pretty simple program and likes running on simple computers. Many of the tools that Audacity uses demand that they be held up in the air in memory while they're running. If you're starved for memory because you're trying to edit a 6-hour HiDef video show at the same time, then that's going to be a problem. I don't think Audacity actually launches any plugins until you need them. If Audacity crashes on launch, then, yes, you got program or plugin problems.

We actually have multiple Macs at work so we could process intensive tasks and still get other jobs out. We found it easier and simpler than setting up ultra high-speed network and remote and batch processing.

Koz

[londonsoundlab]

thanks for the reply

what do you suggest? i dont need any of the plugins except the mp3 encouder - im dealing with tiny mp3 files contingin one spoken word each - but thousands of them - i have to process abotu 20,000 files

[londonsoundlab]

id like to add that it does crash on launch sometimes.

how can i set it to not add my plug ins?

[kozikowski]

Wait. I know this one.

Audacity > Preferences > Effects: [_] De-select everything.

How much on-board memory do you have? Did you put the memory in yourself? You can get problems like this if you have a ratty memory stick. There is a Mac memory checker and any second I'm going to remember where it is...

Koz

[londonsoundlab]

thank you!!!!
i dont know how i missed this in preferences...
this worked on my initial test with 50 files good sign...

about to push it further

question: when i am exporting "multiple" i have to hit enter for each one
is there a hidden "apply to all" button that i am missing?

[steve]

when i am exporting "multiple" i have to hit enter for each one

Is that for the "Metadata Editor" ? If so. you can disable that in "Preferences > Import Export > Show Metadata Editor prior to export step"

[londonsoundlab]

excellent - thank you - will try it now.

also wondering - while i am trying to push the limits of this batch processing

i have to change 20,000 very short mp3s. - it seems i can do 300 at a time - it crashes when i try 1000
going to try 500 next...

is it possible it can do more then this at once if i do anymore tweaking?

[steve]

What processing do you actually need?
If it is just MP3 encoding then Audacity may not be the best tool - some ideas here: http://www.discogs.com/groups/topic/151711

I presume that you are aware that MP3 encoded files always have a short bit of silence at the start (just a fraction of a second, but with short files that may be important).

[londonsoundlab]

I need to compress and normalize each of the 20,000 files - while maintaing the same file name
audacity is the only tool i know of that can do this

the trimming can be done one at a time after the fact because each file is different

the amount of space i need to leave is more signifigant then that
i need a half second or so of silence before each file