as long as the app stays 32bit, there's always danger at the 2gb boundary, and at the 4gb boundary is the obvious "not enough memory - crash - die" limit. to a lesser limit, a boundary is at the 3gb range, too.Pitch Black wrote:Thanks for testing man!
congratulations on destruction first time out of the box!![]()
hmmmmm, perhaps access to copious quantities of RAM is not the salve for bigger sets? Was wanting to see what might happen if you could get everything pre-loaded into RAM and maybe any potential disk-access skips in unfriendly gigging conditions...
it will be interesting to see if silly RAM allows us to grow our current upper-limit Live Set that our 4y/o machine will allow, using normal disk-loaded/some RAM clips Live Set. 110 tracks/250scenes/3.2GB of clips with 3GB RAM on our machine. Hope so!
until live is 64bit, i'd suggest you an ssd as the "fix". going from up to 15 - 20ms down to 0.065ms max accesstime fixes most disk-access skips
![Smile :)](./images/smilies/icon_smile.gif)
it looks like, for some, a 64bit version of live could be of interest by now.