![]() I closed the file and re-opened it, just to see if it would re-open Alchemy again immediately or whether it would have to do that refresh. I have the full library but I imagine this would be hell for someone who had meticulously downloaded only stuff they needed because of disk space or whatever. So I think it will grab what it needs when it needs it but at this point, you'd think it would update the Sound Library Manager, such that once it "knows" the sounds are there, it checks it off in SLM as already downloaded. So clearly it found them on the drive and didn't re-download all those massive files. Alchemy showed me a progress bar (see attached) which probably lasted less than a minute, then all the sounds were available in the program. The Sound Library Manager still can't see the samples on the other drive, but I played around with it for a bit and opened Alchemy. Then I deleted the contents of the newly created "Library" folder and replaced it with the stuff that was in the renamed file. ![]() Could SLM's development have been outsourced? I don't know, but whoever came up with SLM in its present shape and form should probably look for another career.Īfter re-naming "Library" I was able to get the application to move the essential sounds over to the Data Drive. It's as if Logic and Sound Library Manager are two totally different apps developed by separate dev teams. And to add insult to injury, the installation status is defined through installation receipts which are stored in a separate system folder. For example, it cannot detect previously installed library content (say, after it had been moved to an external drive and after macOS has been freshly reinstalled, like in the OP's case), although Logic itself can load samples and presets just fine. In my experience, it's never worked properly, and the way it treats users' time is outrageous. Note: I personally find the Sound Library Manager a total mess. That should help everyone understand the whole process better. Please, report back on what worked and what didn't. You might have to combine these two methods. Can't guarantee it will work, though, since Logic apparently registers the sound library components as installed through installation receipts. After that delete the newly relocated Library folder and rename the existing (fully downloaded) folder back to "Library" (or whatever it's normally called). This creates all necessary symbolic links in macOS system folders, pointing to the library on external. After downloading the "Essential Sounds" (or some other small) library, relocate it to the external HD. Details here: Īlternatively, you could rename the library folder on the external drive (temporarily) to some other name. You could try library installation receipt transplant technique. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |