Garage Band Will Not Open, plz plz help Options

[Dasa Soul]

when i try to open Gb i wet this messege < assertion falce fail in ''proxiy.c''line 122> this hapens whit some of the music programs ,but not whit all of them. i have to force quit . plz plz help!!!

[Dasa Soul]

finaly i fix the prob ,it was a demo that had expired ,the apple suport was no help. but the native instruments demo people where great in helping me , so happy to be back making ,music aloha!!!!

[Nels]

So, how exactly did you get GB to open back up again?

What steps did you have to take to get rid of the expired NI demo error message?

Thanx

[nreyes]

Not wanting to butt-in here, but I also had a similar problem in the past. In that case I had to move all the Audio Units out of the Plug-Ins/Components folder, and then add them one by one to see which one crashed GB. I soon weeded out the offender by then deleting it and restoring the Audio Units back to their original locations.

I have since found a freeware called Audio Unit Manager which allows you to select 'groups' of Audio Units that will be launched depending on the program that uses them. In general this is very useful for speeding up loading times for programs like LIVE, GB etc., who search for Audio Units on startup. Obviously, the other use is to use it for 'troubleshooting' by deselecting the audio units and clicking them on one-by-one to fix the launch problems in GB.

Unfortunately I don't remember the website, but you should be able to do a search in the Mac Music software section or Versiontracker, Macupdate etc. I think it only ever came out as version 1.0.

[Nels]

So which AU was the offender? Did you make note of the AU name for future reference?

Thanx

[nreyes]

I am not at my Mac at the moment, so I don't remember exactly, but I should point out I had the problem on at least two occasions with different plug-ins (one was a shareware, the other was a demo). I can't really say that I have had any problems with my 'Premium' plug-ins. However, after certain OS updates or third-party updates, it is not uncommon to get some sort of conflict, even with well-developed software.

In some cases, just repairing permissions etc. & rebooting sorts these problems out, but if not, the second technique of testing them one by one will eventually root out the 'offender'.

Depending on the circumstances leading to the 'corruption' of the Audio Unit, however, it should be known that the situation could occur at any time with any of the plug-ins. There is no single 'offender' to be named and shamed

Similarly, I once had a problem with the VST plug-ins when Ableton Live was launching (it searches for Audio Units & VSTs at startup). In that case, I wasn't 100% sure (even reading the crash log) which one was causing this, so I ended up having to check both plug-in folders. A bit long when you have loads of freewares, demos & sharewares !

In general, if you have many plug-ins, take a long hard look at which ones you use, and toss the others one away. You will improve launch times (even if only slightly) and avoid conflicts. Likewise, remove all the other residual folders in the Application Support folder, Preferences folder, Presets folder etc. to avoid accumulating junk.

[Nels]

Appreciate you taking the time.

I'm sure others will benefit as well.