Whow. I'm pretty sure that your set is way too large to handle all this with 4 GB RAM. A normal Live set is just a very few Megabytes large. How many tracks and how many clips do you have in those sets which you can still open? To find the total number of clips, double click on a clip to display the clip view at the bottom, then hit APPLE+A. This will show you the total number of clips. Check Arrangement and Session View (if there are more clips).swivet wrote: Yes, this is the actual .als file size, not the project file size.
.swivet wrote: It is not uncommon for me to have upwards of 130 tracks, all with effect presets on them.
Well, if you run into the limits of your computer or resp. of what's possible with the currently available technology, then I'm afraid there's not much we can fix for you. 130 tracks sounds way over the limits to me. Note that Live is generally more demanding on the CPU and RAM than other DAWs, which is due to the Session View architecture. Other, streamlined hosts can look ahead in time and schedule their tasks more efficiently in advance. If you need to do extremely large arrangements like these, then you are perhaps better off using a different DAW for such a job. (although I'm quite sure that a 130-track project will be problematic in other DAWs, too).
It might just be sheer luck that you didn't get this problem in Live 7. Try to open such a massive set in 7 and add some more stuff. I'm sure you're not far away from a memory overload / crash.swivet wrote:the fact remains that Live 7 never even ran into even the slightest hitch with .als sizes wayyyy higher than 149mb.