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

Message

Re: [EXS] CPU overloads

2004-07-29 by Mac Duff

On 7/29/04 8:19 AM, "Julie Larson" <julielarson@...> wrote:

> I ran the activity monitor yesterday and discovered that once my Song
> had played all the way through....I was using all...completely all of
> my ram.  I'm surmising that this is putting a crunch on performance.

It will definitely cause playback problems -- particularly if Logic is
passing the virtual memory chores on to the OS itself! When I had my EXS
prefs set the wrong way, it was damned nasty. In my previous post, I
mentioned what I found to be the best settings to avoid this, keeping ass
much of the RAM handling chores within Logic:

"Sample Storage: "Original". "Yes, 32 Bit Float" does load more of the
samples into RAM, effectively not using Logic's virtual memory. If your
sample banks exceed your Mac's RAM and OS X starts to use its own virtual
memory, however, things can get bad really fast."

So, try running EXS's prefs with Sample Storage set to "original". That
imparts a heavier load on the processor, but probably might be better than
OS X's virtual memory.

(also, did you reduce each EXS instance's polyphony down to each part's
acceptable minimum?)

> My only problem is that I can't add any more.

Recent Powerbooks can take 2GB of RAM.

> Soooo I'm afraid I'm
> coming to the grim realization that I'm in the market for a new
> computer.  I need portability so....Has anyone heard any rumors about a
> G5 powerbook?  I've heard Apple is having a hard time keeping them from
> melting.

I wouldn't expect a G5 Powerbook until AT LEAST Macworld San Francisco in
January (G5 iMacs are due for release in September, BTW). When that finally
happens, I too will be looking into moving to a laptop. It would be nice to
do a TV series score from a beach, somewhere :-)

Attachments

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.