Subject: Re: [linux-audio-dev] Freeze?
From: Steve Harris (S.W.Harris_AT_ecs.soton.ac.uk)
Date: Thu Feb 26 2004 - 17:17:31 EET
On Thu, Feb 26, 2004 at 10:04:47AM -0500, Paul Davis wrote:
> the problem is that in a typical DAW session, you can potentially
> freeze most tracks most of the time. so how can you tell what the user
> wants frozen and what they don't? More importantly, freezing consumes
> significant disk resources. Can you afford to do this without it being
> initiated by the user? A typical 24 track Ardour session might consume
> 4-18GB of audio. Freezing all or most of it will double that disk
> consumption (and its not exactly what you would call quick, either :)
No, but you can do it (semi-)transparently when the user presses play. I
dont know if that would be acceptable or not, but if you imagine adding a
few effeects, auditioning, rinse, repeat it might work out ok.
I'd always go for more CPU if possible - I'm not a huge fan of multiple
code paths :)
- Steve
This archive was generated by hypermail 2b28 : Thu Feb 26 2004 - 17:19:37 EET