And to add to Stevesong's wisdom, hardware requirements can often be problematic, coupled with workflow. There's a dedicated thread here about the infamous 3GB switch that frees up more memory in a windows scenario. That's the OS providing a limitation that would be a challenge for ANY developer. Couple that with Herb's detailed explanation of multiple samples used to create that 'sound', and the combination of the two present interesting challenges not only for developers but users too. Hardware's coming along, and hopefully, the new Win OS will allow users to exercise more freedom and 'space' when building up big orchestral templates.
Something i constantly forget, until it bites me, is just what we're asking data to do. And the volume of data that passes over the CPU and through RAM is considerable.
You've given the example of Kontakt, and how successfully it works for you. My one experience with Kontakt was completely the opposite. I thought it a bloated, extremely CPU/RAM heavy player that presented more problems than solutions.
And i found the 'tidying up' after playing in a line with Kontakt was a real pain in the backside. The interface, no matter which colour they dress it up with, is unpleasant to stare at day after day, and for me at least, looks like it was designed by a surly undertaker. (IMHO)
Steve's right. Everyone to their own, but that doesn't mean the product's bad, or has serious limitations. It simply means in an individual workflow, one design may fit more comfortably than another. The VSL player has proved extremely popular, just as there have been passionate discussions about the more general future of locking samples into a format. I for one find it rather incongrous that so much is made of Kontakt as a viable tool, yet it's just as restrictive as a locked format, especially for me, as i have no wish to use it and repeat a less than happy experience. Frankly i don't understand why other developers continue to release libraries in only this format, as, using your own frustrations as an example, there are some of us who don't want it. (And of course the same can be said for Windows player versus itunes formats, both restrictive and locked)
Whatever you do Janila, i wish you luck and success, with relatively trouble free audio 'motoring.' It's no fun to spend a deal of time trying to figure all this stuff out, and we all seek the same Holy Audio Grail, that of writing for a large percentage of time, and spending minimal time with the digital toolkit open trying to tweak something. I for one like going back after writing lines in, and tweaking not only samples used but applying filters to develop the sound in a direction i choose. But then i'm using a tiny self built library that i know well from years of use. Maybe the same will happen when i finally get back home and buy a substantial library to complement what i already use. I certainly know it will take practise, and some deal of dedicated study time to get the best out of any new sample library, and explore all the opportunities it may present, and that includes learning to drive the thing!
And i'm not a VSL owner yet, as i'm still in the middle of my study in Russia. So i get to stand back and be substantially objective about this stuff. (Whether that's good or not, i have no idea!)