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-25 by Mac Duff

But are not the buffer values really effect input only?? I know they impact
playback, but once you're playing back, doesn't Logic simply get itself
together of its own accord? It's the real-time interaction with the
sequencer as it tries to handle a heavy load at the same time where latency
come into play? I'm probably wrong on that.

The following may not effect disk performance much (definitely try
defragging the disks, as suggested), but these settings helped to increase
Logic's overall efficiency when handling virtual instruments, perhaps
reducing your dependency on freezing tracks:

Audio driver:
12 tracks
64 Busses off
Process Buffer Range Large
Larger Disk Buffer on

EXS24 prefs (open an EXS24 edit window -- where you can see the samples laid
out across the keyboard -- and from the Edit menu of that window select
preferences):

SR Conversion: "Normal". "Best" is better at stretching samples across wider
keyboard ranges, but demands more processor. If you're already using
converted Giga sets, the sample ranges are most surely quite small. So,
"Best" is probably unnecessary.

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.

And finally, really scope out the polyphony assignments for your EXS24
patches. Logic is fixated at importing patches to a polyphony setting of 64
NOTES!! This is in most cases RIDICULOUSLY HUGE! Polyphony kills your audio
driver -- even if you're not using all the notes assigned.

Hope this helps!

MacDuff


PS: If you can get more RAM in your Powerbook (some 1GHz books can take
2GB), I'd suggest maxing it. I have 2GB of RAM, and I am well over 1GB with
large banks (current one is 1.6GB in size!). These days, I have all 64
instruments active, all of them EXS24 except for one EVP88 and one EVB3,
using one instance of Space Designer. While I do have dual 1.3GHz G4
processors, I'm not sure Logic is as dual processor savvy as OS X itself is.


On 7/25/04 8:07 AM, "Brio Taliaferro" <logic@...> wrote:

> It sounds a bit like these problems have crept up on you just recently, so
> my first guess is that disk fragmentation is to blame. Try using norton's
> speeddisk or similar to defrag all your harddisks. Run Diskdoctor while
> you're at it to make sure all the disk catalogues etc are in ship shape.
> 
> Secondly, try to spread the load over many disks (i.e. have the streamed
> samples, the audio, and the freeze files on up to 3 different disks for very
> heavy projects). You could also set the freeze files to a lower bit depth
> (not sure where this is done).
> 
> Thirdly, you can try tweaking the buffer values in the audio driver section
> of the Preferences. I am mentioning this last, because it will have adverse
> effects on latency. However it might be worth fiddling with to get that
> extra bit performance out for a very heavy session.
> 
> Hope this helps,
> Brio
> 
> On 25/7/04 4:05 am, "Julie Larson" <julielarson@...> wrote:
> 
>> Hi all,
>> I'm using a 1ghz TiBook, 1gig ram with a Digigram Vx pocket.  I have
>> fast external drives that contain my audio files and samples.  The Vx
>> pocket has been a little trogan and I've used it for years.  But I'm
>> having frequent audio overruns as well as Disk I/O failures recently.
>> The music is orchestral....the instruments are large....  GOS, Sam
>> Brass, Dan Dean Winds, Post BOS290 etc.   I'm not a techie.... I'm not
>> even sure I spelled it right but could my audio card be causing these
>> problems....or I guess the better question is....What is the most
>> probable cause of these problems?  When I look at my system
>> performance....the "audio" side is maxed out...it chokes.  So...I
>> freeze some files.  Almost imediately the Disk I/O is maxed.  When I
>> Solo the "frozen" tracks... no disk labor.  When I mute the frozen
>> tracks....the Audio side is at manageable  levels.  But when I un-mute
>> the "frozen" tracks I get Disk I/O failures.  Then I unfreeze the
>> tracks....Audio overruns.   I would really appreciate some insight into
>> this.
>> 
>> Thanks in advance,
>> julie

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.