Hi,
I've just moved to Live 6.07 for gigging (from Live 4) and been having the same problem with large Live Sets.
My gigging set contains 1.7Gb of clips and is 128 tracks wide x 339 scenes deep. This represents 11 "songs" as multitracks combined into one large set.
The set will play happily until about the 5th song then start glitching, staggering, dropping out etc. We have had to resort to splitting the showload into two halves of 5 and 6 "songs" respectively, and using a 60 second ambience played off an iPod to cover loading the second half.
We just got back from our first ever gigs/tour with Live 6. We played 10 "songs" (5 in each load) each night until the last gig of the tour when we played all 11. And wouldn't you know it, on the 11th song Live started to stagger and drop out. Fortunately not badly enough to stop the show, but definately noticable to everyone in the club. (I had to make a little joke over the mic about our computer being tired and needing a sleep).
My question to the Abes is:
what fundamental part of Live's design is being exceeded here? Some form of cache limit somewhere? Can you let us know without breaching any NDA about Live's internal architecture? I am just a musician and not a coder so I don't know about these things.
In closing, check the contrast between the specs of our old gigging system (which was loaded with as many tracks and clips as possible before dropouts would occour) with the new one:
Old Rig:
Powerbook G4 single 500MHz
1Gb RAM
OS 9.2.2
Live 4.02
RME Multiface/PCMCIA
110 tracks x 250 scenes
1.3Gb of clips
New Rig:
MacBook Pro C2D 2.33GHz
2Gb RAM
OS 10.4.9
Live 6.07
RME Fireface400/Firewire
128 tracks x 339 scenes
1.7Gb of clips
(has to be split into two halves)
So the new rig can only handle roughly HALF the showload of the old rig without glitching! I accept that not all conditions are equal in the two cases, but I would have hoped to at least stay the same, and not move
backward in capacity.
Please, is any Ableton at liberty to shed any light on this?
Best,
Paddy