Re: preferred disk api for high bandwidth sample reading
Re: preferred disk api for high bandwidth sample reading
- Subject: Re: preferred disk api for high bandwidth sample reading
- From: Paul Davis <email@hidden>
- Date: Sun, 3 Jan 2010 14:02:52 -0500
On Sun, Jan 3, 2010 at 1:49 PM, tahome izwah <email@hidden> wrote:
> Just my 2 cents: With memory getting cheaper all the time and MacOS X
> being (mostly) 64bit now I would read all the (relevant) samples into
> memory rather than streaming from HD. The way I see it your app is
> going to need a hi end Mac anyway so it could as well use the
> available RAM rather than read from HD (which is comparably slow). I
> guess there must be a clever way to figure out what data you need and
> when, so you can preload at least that part.
i am not a recording engineer, so i don't record "real sessions" as i
test my host app. nevertheless, i have test sessions of around 15-30GB
of audio data, way beyond anything that will fit into RAM. there is no
way to handle data on disk that provides any shortcut around careful
buffering&caching design. you might get away with "just put it all in
RAM" if your application is limited in scope, but otherwise, you're
just deferring the point at which things start to break.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden