Soundtrack Pro unexpectedly quit

Question

I recently upgraded to Logic Pro 08. from 07. Just tried to open Soundtrack Pro, but keep getting an error message telling me the application quit unexpectedly. So I went to downloads, and was successful with Logic 8.0.1 update, but when I try to perform the Soundtrack Pro update as per the order of their instructions, I get caught between the two available Pro Apps updates (2007-01 and 2007-02), the earlier one saying I can't download it because I don't need it, and the later one saying I need the first update in order to proceed.
Does anyone understand my problem?
Thanks so much.

Answer 1

You're Welcome.
1. This one was really relatively simple, about as easy as they get actually and very common for AUs that crash the host.
Thread 0 Crashed:
0 <<00000000>> 0x00000000 0 + 0
1 com.tcelectronic.Fabrik C 0x15977b07 ComponentEntryPoint<GPFAU>::Dispatch(ComponentParameters*, GPFAU*) + 47
First, find the thread that crashed and see why it crashed. Look for clues from there.
The crashed thread in this report was 0. Within that thread there were calls to Fabrik C. So try disabling the culprit and see if it works.
2. Well, there's not much I can say without much speculation. The apps will likely handle AUs differently. There's a good chance SP would be the most different from the others in the bundle regarding AU hosting. Another thing it could be is the AU cache used by apps. Because of the cache, hosts can store info about an AU and refer to it when launching. What it boils down to is apps will do some checks, such as:
Has the AU's version updated since the cache last updated?
Should the host bother to load it? (i.e. user requested it not to load)
Did it pass validation?
Other pieces of info, perhaps supported channel layouts and on and on.
This way, the host can launch faster/safely. If no update is detected and it passed validation, it will assume it still passes and plays nicely.
Sometimes the cache is wrong - for various reasons, i.e. if an update crept through. It rarely happens. You may want to clear SP's cache if you really like this plugin, then it will be forced to update the cache. Maybe an update did slip by? I'm already far enough into speculation realm...
J