I can't say that KP2 is the worse piece of software ever released, but it's getting right up there.
My on-going problem from day one is that I can't get it to load unless I cold boot first! If I run just about anything else prior (including KP2 itself!), KP2 won't load, freezing on the splash screen. If it somehow gets past the splash screen, then the instruments usually won't load. But if I cold boot and run KP2 immediately, then it will usually load ok. No other piece of software on this rig has ever behaved like this. NI "support" apparently doesn't want to hear about it.
I have 2.0Gb of ram on a 3.2Ghz XP pc at SP2 with 3Gb of dedicated disk cache. Nothing is running in the background; 99%+ of the cpu is available. When KP2 freezes, I typically have over 1.6Gb of ram still available. A successful load of the smallish ensemble I'm currently (trying) to work on only takes up around 200Mb.
Now, just today, all the instrument skins suddenly disappeared, and at the same time it blew away the output routings and aux send levels! I guess some hidden counter somewhere decided I've loaded it one time too many and now it's time to turn everything battleship gray!!
I'm hoping this erratic hosting software doesn't negatively impact Gary's market penetration and overall product line, but I'm assuming most of Gary's clients don't use the stand-alone version of KP2 anyway, except maybe to audition things and play around with the various parameters.
Reluctantly, I'm thinking of junking the whole deal and sticking with GPO "classic". Unfortunately, I won't be able to explore Garritan's newer offerings until something more stable comes along (or I upgrade my notation software to something that obviates the need for KP2 altogether, though I'd hoped to delay that expenditure well into the future).
Conceptually, KP2 is great piece of software -- a fine addition to the Garritan line up and it's just what I needed at this time. But unfortunately, it's just too buggy for everyday use right now.