Logic Pro 9 will not find some EXS instruments

Question

I recently updated to Logic Pro 9.1.0, and today tried to load a project I've been working on for a few weeks (prior to the update), only to be greeted by the message "EXS24 Instrument 'Name.exs' not found."
A few sites have suggested re-indexing my Spotlight and restarted, and I have tried that to no avail. I also tried setting the EXS options to "All Drives". What's strange is that some instruments are loaded, but others are not. If I search for the filename using Spotlight, I can see they are located on the drive where they always have been.
What's potentially unusual about my installation is that I have a symlink at "/Library/Application Support/Logic" pointed at one of the other internal drives where I store all my Logic data. This has always worked before, and I don't really have enough space on the boot drive to put all of Logic's samples in /Library.
Does anyone have any clues how I could get my project loading again?

Answer 1

one shouldn't move installed content from the default places
It's not that so much, it's that you must understand Logic's behaviour in how, why and what to move, as it varies depend on the content.
I for one have used symlinks with Logic (and other apps, too) for years without a hitch until v9.1.
As I've said - for some of Logic's content this always used to work fine. For others, it *does not work*. I'm not going to list all the various types of content and paths that don't work with symlinks, but it's enough, trust me.
There are several reasons why one would have content elsewhere even without such novel application as Dropbox makes possible, for instance harddrive space and simply organization.
Of course. I'm not saying there isn't. I'm simply that that in some cases, Logic does not make this easy, and it's a bit of an unsupported hack in some cases. For other content, such as samples, Logic has always been designed to be flexible and there aren't many problems moving it or aliasing/symlinking it.
Personally I have all the factory content on the system disk in the default location these days, but I prefer to have the user content elsewhere.
Me too. And I've invested some time in understanding what can and can't be moved, what works and what doesn't, and have set up my system according to this and to my needs.
It is absolutely aggrevating for Apple to overlook such a thing, or a fix to take so long
Sure.
to read on a forum "just don't do it like that if it doesn't work"
Sure. but these help forums are to get people going, not to endlessly wallow and moan about why it doesn't currently work the way I want it to. I can moan with the rest of them, but I mostly choose to deal with it in the best way I can for the time being and revisit it if the situation should change in the future.
I'm not a coder, but based on what I've read on forums and asked a couple of coder friends, this shouldn't be the most complicated matter to make work. Many of them have suggested that it's probably only an overlooked thing in the API change, not a huge ordeal.
Yes, probably so, however sometimes things that seem simple on the outside aren't always trivial to implement.
All you can do in the meantime, is report the behaviour, and set up your system the best you can to work in a practical way. If this is impossible, revert to an older version, and hope that a future version changes the behaviour.
But I don't recommend leaving things broken and expecting it to be fixed imminently, because this may not be the case.