Whether Memory issue or performance glitch, as soon as a song has a certain amount of tracks/complication and instrument memory is getting tight, it seems like the sequence editor is breaking down.
One issue that can happen: The sequence editor doesn't open with graphics, but seems to grab the buffer of the song editor and doesn't refresh with its own graphics. Guessing where the close button is can close it, but MuLab by that time is practically dead and requires restart.
Worse issue: Inside a seemingly properly started sequence editor its no longer possible to do any editing. Cannot draw notes, for example, or controller curves. Saving the song afterwards can and will corrupt the file, leaving you only with hopes that the session.backup was recent enough.
Once the song is complex enough, it's nearly impossible to continue working, because it fails reliably in the above manners. That can be somewhat tragic, actually. I'm having some good fun with the song I'm working on right now, but it appears I have to cut it short now. That is, unless you have some idea what could cause it or a way around the troubles.
I'm using Kontakt 5 extensively and have about 11 subtracks with some heavy instruments. Memory usage is around 1.7Gigs right now. CPU goes up to 37%. This is on a 12core HP Z600 Workstation (Xeon X5650 @ 2.67Ghz), 16GB Ram, Windows 7 64bit.
Just hoping you might imagine what this is...
