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] optimum set-up with TiBook 500

2003-09-02 by Jeff Fisher

On Tuesday, September 2, 2003, at 05:37  AM, exs-users@yahoogroups.com 
wrote:

>>> Subject: [EXS] optimum set-up with TiBook 500
>>>
>>>
>>> Hello, I've just joined and happy to be here!
>>>
>>> I have just gotten the PMI Bösendorfer from Michiel Post and it
>>> seems just fabulous. Only thing is, I can;t use it!
>>>
>>> I suppose that it is just too heavy for my system.  So...please
>>> gove me advice. I want to learn how to use samples kike this. I
>>> have a TiBook 500 running OSX  10.2.6 with 768 mb ram. I'm
>>> using Logic Platinum 6.2 with the ESX24II. I am storing the
>>> samples on external 7200 oxford 911 drives (not sure of the
>>> caches).
>>>
>>> Any expert recommendations would be greatly appreciated.
>>>
>>> Thanks,
>>>
>>> Franklin

		Hi Franklin,

			I have the exact hardware as you..except for the Metric Halo stuff. 
Seems Emagic
doesn't recommend using Firewire Audio boxes with Firewire Hard Disks 
for streaming audio.
		Try:     a) moving the PMI to an internal audio partition, if you 
have one.The Ti500 has a clunky
				Firewire implementation compared to subsequent PBks.
			  b) Changing to CoreAudio  (In Logic) and using the internal audio 
instead of the Metric   				Halos.
			  c)   enabling larger disk buffers and large (or jumbo) process 
buffers in Logic.

			  d)  Use Diskwarrior to fix and optimize directories
		
			  e)	repair OSX disk permissions using the boot disk
	
			  f) from the ESX24II plugin window, limit polyphony to 32 or 24 
voices

		I have had a few problems with the pianos with release-trigger 
samples, try the 8 layer no release for starters.
                                  HTH,
				Good Luck,
						Jeff
>>>

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.