EXS 24 Logic Sampler Users Group group photo

Yahoo Groups archive

EXS 24 Logic Sampler Users Group

Index last updated: 2026-04-28 23:25 UTC

Thread

sample loading time

sample loading time

2006-07-05 by forums@logic-users.org

Message posted by Sinan Bokesoy <sinan@...>:

Hi,

I am facing huge sample loading times on EXS24 on my Intel mini-mac with
Logic V7.2.1 with 1GB ram and OSX10.4.7

I am using a library where the samples instruments are stored in
Library/Application Support/Logic directory and the samples are stored on a
firewire external hardisk.
The sample loading time is too long, where it is impossible to work with.

I did try the same thing/setup on my old G4 mini-mac with Logic7.2 and OSX
10.4.6. It works very fluent, the samples are loaded instantly. 

So I can't see the possible solution and share please your experience if you
had similar problem.

thanks,

Sinan

Re: [EXS] sample loading time

2006-07-05 by Eli Krantzberg

On Jul ,5, 2006, at 9:30 AM, forums@... wrote:

> Message posted by Sinan Bokesoy <sinan@...>:
>
>  I am facing huge sample loading times on EXS24 on my Intel mini-mac 
> with
>  Logic V7.2.1 with 1GB ram and OSX10.4.7
> [snip]
>  I did try the same thing/setup on my old G4 mini-mac with Logic7.2 
> and OSX
>  10.4.6. It works very fluent, the samples are loaded instantly.


Is this just happening the first time you load a new instrument? Or is 
it also happening even after it has already been loaded in previously? 
Because on a new system, it takes time for Logic to find the associated 
samples the first time it is locating them. If it is just on the 
initial search/load, then EXS Manager from Redmatica will help 
immensely. It links up the instruments with the associated samples in 
advance, so that the first time you load them they are already "linked" 
and load quickly.

If the problem is occurring even after the samples and instruments have 
been linked up, then it is a different problem. Check out the speed of 
your external FW drive(s). Are they daisy chained with other drives or 
audio interfaces? Also, 1 GB of ram in todays world is not really a 
lot. More ram would certainly help the situation - although this itself 
is probably not the cause of the problem.

--------
Eli Krantzberg
http://www.nightshiftorchestra.com
Almat Productions

Re: sample loading time

2006-07-05 by forums@logic-users.org

Message posted by Sinan Bokesoy <sinan@...>:

Hi again,

It is not just happening the first time I load a new instrument. 
Sometimes the first two load operations seem to be normal, 
but then the third one takes ages to load, although the sample sizes are fairly light.

My ex-drive is a Formac Disk 500XTR which is operating just fine (I recommend it highly)

Memory shouldnt be a problem since I try the same setup with a G4 mini-mac 512MB. EXS24 loads there
a Bosendorfer huge piano sample in 20sec. It never stucks.

One interesting things is, I dont see on the EXS24 on my intel mini-mac the sample load bar, which shows the sample
loading process. Are Logic files corrupted? I did reinstall Logic again withour uninstalling the former, but the problem remains.
Should I re-install all the system? I have installed bootcamp and Windows on the same harddisk, does this cause any conflicts for the
sample search operation? 

best,


Sinan

Re: [EXS] Re: sample loading time

2006-07-05 by Eli Krantzberg

On Jul ,5, 2006, at 1:58 PM, forums@... wrote:

> Message posted by Sinan Bokesoy <sinan@...>:
>
>  One interesting things is, I dont see on the EXS24 on my intel 
> mini-mac the sample load bar, which shows the sample
>  loading process. Are Logic files corrupted? I did reinstall Logic 
> again withour uninstalling the former, but the problem remains.

Sounds like this might be an Intel version specific problem/situation. 
Sorry, I can't be of any help. I'm still running on a G4.


--------
Eli Krantzberg
http://www.nightshiftorchestra.com
Almat Productions

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.