Battery 3 Suddenly Crashing Every Live Set!

obscurityknocks · Post by **obscurityknocks** » Sat Jun 21, 2008 3:40 am

Tonight at rehearsal I opened up a new MIDI track and went to add Battery 3 to the track--something I have done hundreds of times before--and suddenly the Live Set crashed.

No big deal, I thought, and tried to open the set again, and add Battery 3 again--same thing.

Then I tried opening up other sets that had Battery 3 in them. Live crashed just when trying to open the sets!

I tried restarting the computer, unplugging all peripherals, everything that was remotely different from what I do all the time--every time it crashed. (I had no problem when loading Zebra 2 as a VST.)

What the hell????

I am on a first generation Macbook 2 Ghz, with 2 GB RAM. All of my Battery 3 samples are stored on the hard drive, and I have made no changes whatsoever to my operating system, or added or updated any programs.

(The first time it happened the Macbook was hooked up to an M-Audio Firewire 410, a Novation X-Station, and a powered USB hub hooked up to a Trigger Finger, and a wireless mouse. (Again, I rebooted and unplugged all of these the second time._))

Any thoughts?

kleine · Post by **kleine** » Sat Jun 21, 2008 10:01 am

Hello obscurityknocks,

Please send me your Log.txt and Crashlog to check it.
You´ll find the Log.txt here:
/User/Library/Preferences/Ableton
and the Crashlog here:
/Users/Library/Logs/CrashReporter/Live.crash.log
• Please send the files as .zip attachment.

-> [email protected]

Best,
Christian

Poster · Post by **Poster** » Sat Jun 21, 2008 10:51 am

@ obscurityknocks

you might want to try if deleting Battery's preference file helps..

I had similar problems with Reaktor which were solved by deleting the prefs file..

/User/Library/Preferences/battery preference fille

if you're not sure about deleting the file you can first try to move it to another location..

cheers..

Tarekith · Post by **Tarekith** » Sat Jun 21, 2008 12:20 pm

This happened to me last year halfway through writing an entire CD's worth of tunes, was the last straw for NI and I. Try reinstalling Battery3 if nothing else works, when I was looking into this and read about others with the same issue, some of them had luck with this working. Not me though sadly.

obscurityknocks · Post by **obscurityknocks** » Sun Jun 22, 2008 5:45 am

Thank you to all who responded--and of course to Christian @ Ableton for checking out the error logs and giving some advice so quickly.

So, I basically went partway through the suggestions then, just for the heck of it tried to open Battery 3 as a standalone, and noticed that it immediately crashed.?

I was about ready to try to uninstall and reinstall the whole thing, when I noticed a little file/folder in the Battery 3 folder called "library-cache.b3c". On a hunch I removed this file and just placed it on the desktop.

Bingo--suddenly the problem is gone and all works as before.

What exactly is this file, and why would it cause this behavior? Is it ok that I've removed this, or is it something that I should put back in and clean out somehow? (How would one even go about this.)

Any thoughts??

Again, thanks for all help so far on this issue.

rvltion909 · Post by **rvltion909** » Fri Aug 22, 2008 5:53 am

sorry about the reincarnation of the dead post as Im sure Im clearly violating some subsection of a forum etiquette manual somewhere but....

I tried deleting that battery cache file and it didnt make a bit of difference. However...not sure just yet that the problem is with Ableton as I tried opening a FL Studio project with battery as a VST channel within and got the same crashing results.

However...it was running rewire slave mode in Ableton at the time so...

Im interested in what the OP got from Ableton support with the log file info? My next step is to reinstall battery....which is a bloody pain since my DAW is not online for the stupid activation.

Anyhow...my 1st inclination is to blame NI as they have some very seriously buggy products in my experience...which is a shame for a company that puts out VSTs with such GREAT sounds.

ewistrand · Post by **ewistrand** » Fri Aug 22, 2008 4:16 pm

obscurityknocks wrote:What exactly is this file, and why would it cause this behavior? Is it ok that I've removed this, or is it something that I should put back in and clean out somehow? (How would one even go about this.)

It's a database for your library. If it's corrupted, Battery will crash- guaranteed.

As to putting it back, it should have regenerated itself the first time you started Battery in standalone after deleting it.

@ rvltion909- does it crash in standalone as well? Plugin and standalone versions match?

Your NI forum moderator,
ew

rvltion909 · Post by **rvltion909** » Sat Aug 23, 2008 6:24 am

ewistrand wrote: It's a database for your library. If it's corrupted, Battery will crash- guaranteed.

As to putting it back, it should have regenerated itself the first time you started Battery in standalone after deleting it.

@ rvltion909- does it crash in standalone as well? Plugin and standalone versions match?

Your NI forum moderator,
ew

Stand alone seems to work fine. However...the cache file didnt regenerate at all. It seems to only be a problem with VST mode

ewistrand · Post by **ewistrand** » Sat Aug 23, 2008 6:46 am

And do the versions match?

ew

rvltion909 · Post by **rvltion909** » Sun Aug 24, 2008 7:14 am

ewistrand wrote:And do the versions match?

ew

?

Sorry, I dont catch you? Stand alone and VST? Is it possible for them to be different? I thought the "service center" updates both with any updates? Maybe this is not what you mean.

Anyhow...upon 2nd look, the file did regenerate. I was looking in the "program files" Battery folder...and although one was there and I deleted it...it never regenerated. However, I then went to the custom folder I installed Battery in, deleted that cache file and it regenerated.

The problem does seem to have left too. I'll post again if it changes

Thanks for the info.

ewistrand · Post by **ewistrand** » Sun Aug 24, 2008 6:04 pm

rvltion909 wrote: :? ?

Sorry, I dont catch you? Stand alone and VST? Is it possible for them to be different? I thought the "service center" updates both with any updates? Maybe this is not what you mean.

?

The Service Center itself doesn't update anything- the installer for the update does. And, if you've changed plugin folders or something along those lines, the installer might not write the plugin to the folder you expect.

While NI installers are better about determining the proper plugin folder than they were, glitches still happen on occasion. Unless specifically told otherwise, NI plugins on a Windows machine (and you're Windows if I remember) will install to the system default, which is the folder named by the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\VST

ew