Hmmm... I've never been able to be sketchy but I'll try.
I'm "less is more / less for more" thinking guy.
BUT, what I'm working on for months is like one track from Halo 4 Soundtrack, by Neil Davidge, a great "sound scientist" since whatever you like or dislike, he is and I hope we are still a lot, hoping that NO, we haven't invented "all sounds and musicals tools, types" etc.
So to be sketchy : an orchestral track, mixed with Xfer Records plugins : Nerve for drum sequencing, LFO Tool for effects (it should be renamed "WTF Tool this one it does a lot) and Cthulhu for arps when I'm lazy. I tried to be able to keep my working-precious-config reliable but >>> F***ING 4GB RAM LIMIT (in fact, 3192MB, and no way to do the "smart but stupid" guy who will immediatly break the 2GB per thread, I know what it meand, like 64 to 32 bridges for VSTs : it ca, work so well you would - why not - think about you're NOT thinking it's unreliable.
Sorry Sibanger, I may look like a geek or whatever, no I lost hours of work despite constant savings, if you know how it feels to have had "that thing", and then loose it and can't redo it,
>>> BTW even if I always make realiability as a priority, and have been fooled because, you know, constant vs. variables etc blahhhh :
A good answer could have just be this : "if you often have to the DAW and the system on their knees, and D'oh you lose your work or worse (published VSTs specifig tricks or hours on a Max for Live patch the joke being you I mean I, don't master all this coding stuff.
Cycling'74 is honest : Max 6.1.1 x64 doesn't have its brother's abilities for the moment and comparing changelogs between Max 6.1.1 x86 and x64 is mostly "bugfixes" focused.
Then, the reason that helped me for that choice is that Suite 9 has the full 4-packs from OIC, + Grand Piano ... Suite 8 has just EIC2. Since I'm allowed to have both, OK HDD space matters, but I'm as I'm finishing to write this pôst, satisfied for the "more for more", instead of using a shitty imported '8' Library into '9', I did that and I'm surprised, in fact.
In case of someone want to check him/herself that it works more than expected, the only thing is that when I work @ 9 then switch on 8, OK. The contrary doesn't work or there's a crash IMHO linked to the godd/evil/good/but evil indexer.
And my ending words will be that this indexer, after about 20h for downloading, installing, erase ALP to free space and DL the next ones, re-drag, waiting etc ... I knew Live 9 indexes. So my customs folders were created at first launch before any pack installation. Then, when all is in "PLACES", I just left the notebook indexing and waited the next evening. And believe me or not, anyone talking about browsing time loss is a liar or just can't be smart enough to understand that it's not a game and an indexer takes 100% HDD/SSD until the end. Waiting for the end without doing anyting seems therefore a great solution to a recurrent topic which shouldn't troll every places @ Ableton.com (forums, community answers, etc). And if some are affected by a real bug, like "indexer in an endless loop", then, I'm just can feel bad and be sorry for these musicians.
If you want, you could think about this idea I've had, strange 'cause I'm an asshole 6,9 days a week but about L8/S8 x86 + M4L x86 (forced to, 5.0.9 isn't x64) AND L9/S9 x64 for RAM eating stuff, dude, + the "leave that indexer and prepare your workplace into the DAW before running to the wall" ... It might be the only thing in this world I consider as "pretty sure" despite being the guy who has got that, and since the release NO TRACE of even ONE guy having done everything this way
Warm regards to all.