bismuthdrummer
Active Member
- Joined
- May 13, 2011
- Messages
- 534
Well I'm not even sure I proved that fully, there may be some application that consumes a bit of memory without eating up all the CPU cycles. Just not sure what that would be, I'm open for some ideas, I know some may suggest VMs, but they are a bit of setup and I'm not sure I'll get to any time soon.
As I already mentioned it's pretty trivial with Audacity. A couple basic tests on my 1GHz 512MB Pandora eats up all the available memory.
I recorded a 4 minute sample at the default 44.1 kHz and 24 bit PCM, mono channel. That eats up 31 MB just for the data plus any metadata Audacity stores. Copied the track five times, adding various effects that affect the waveform. Audacity reports no space left. I'm at something like 50 MB in the OS according to the free command; guessing I've used about 256 MB after system overhead. (I tried taking screenshots but none of the repo apps work anymore.)
I've worked on much larger compositions with many more tracks, stereo audio, 96 kHz... more RAM is always useful. I'm just speaking from experience that a 2GB ceiling would definitely be felt in some cases. 4GB much less so. Are there workarounds like working with multiple project files or zRAM? Yes. That doesn't make 4GB useless, and people saying as such are betraying their lack of objectivity.
The same argument can be extended to 8GB, but again it all depends on the costs. Certainly there is diminished return from 4-8 in comparison to 2-4. If it were $4 more, I'd say hell yes. If it's $40 that would probably not be worthwhile. It's all a matter of price point and return.
We don't even know price points and we're getting 2GB anyway, so I don't have a firm stance on the matter.
Last edited by a moderator: