<uswitalski@...> wrote: > ... just as a reminder (and i know i am repeating myself, but knowing this > fact really helped me a lot), when you all are moving and renaming and > aliasing files of the exs you will loose _a lot_ of its load speed. once you > moved, renamed and whatnot-ed the files you will have to load each of your > instruments for the exs to update the initial filepath it searches. so > depending on how big your library is it should be thought of before > reorganizing files. As sad as it is: Reorganizing files under LAW is almost no issue. The EXS will relocate its samples for all my patches (around 4500) in 2 hours, using the "original Andrea Gozzi trick" (setting up a sequence doing the "next" patch job). Let alone that there is the brilliant EXS manager (again by A.Gozzi). Mac users apparently suffer WAY more whenever they're reorganizing their files. Using aliases has no impact on the EXS speed on Windows either, it's just loading patches almost as instant as a hardware device, if not faster. A lot of these things apparently have to do with LAM (or the EXS) not caching any file directories or whatever. Under Windows, for example, the last used filepath is cached, so if the EXS needs to "refind" a second bunch of samples it will start straight at the place it located the previous patch's samples which makes the whole process a LOT faster. Just recently I've been at a friend's place, he's got a (wellconfigured it seems) DP 1GHz Mac and it was truly dissapointing to see the EXS instrument menu being as slow as on a P133 with 32MB of RAM or so. The same was true vice versa, when he was over at my place he was simply amazed about HOW fast the EXS would load its patches. FWIW, we have around the same amount of patches. But well, we're moving on to the superior OS, aren't we? Sorry, couldn't resist... Sascha (now concentrating on the x-mas/family deal, actually a very nice thing, see you folks in a few days)
Message
Re: [exs] Re: How to Organize the files
2002-12-23 by Sascha Franck
Attachments
- No local attachments were found for this message.