perhaps someone here can shed some light on this for me...this has been happening to me a lot recently and its very frustrating... towards the end of a project my resources are fairly maxed, but i'll be working away and my computer is handling, ie playing the track fine...then ill save, open up another day and i can't play even a split second without an overload error...wtf is up with that!???!!?
one the bright side it forces me to bounce down more elements of the track freeing up even more processing power and allowing me to work a little farther, a little freer..but at the same its big time fucking annoying :S
Today, I am working on one project, and its playing 100x better than yesterday! I haven't reopened the one that was really bogged down though..
Funny thing is, when i was having problems yesterday, it was fresh after turning on my computer..i left it on over night, today i open logic and its working much better...
Nu, I had similar problem before with Logic acting up when loading a heavy project done the day before. When playing at first attempt 'overload' text just pop-up. Try to play the whole project from start to end if possible. By second run it should be ok. Im not sure of the reason for this but some producers has also encounter this problem. After updating to OSX 10.5.8 i don't have this problem any longer so you might wanna try this too.
Hope it works out
ed
__________________
There Is No Magic Silver Bullet
Glenn Meadows
I also have had to sometimes run a session in Live through to the end to help cache it all so it runs better.
Maybe if you are on dual processor then when you open it the second time the cores might not be as evenly distributed, could account for the difference.
I've seen Cubase have up to 10% variation on this so if you're near the top it would make a difference in playing or not.
processor maxed after project reopen
Linear Mode
