I hear what everybody’s saying here, but there’s a real issue here. Half Light Studios, I’d recommend that you go do some research on combining articulations, like the Youtube videos that Alex Pfeffer (fantastic composer, btw) did on how he builds trumpet parts from multiple articulations. Here’s one: http://www.youtube.com/watch?v=Yu73C3GBOuw
EWQLSO isn’t intended to be played as one patch on the keyboard, all the way through an instrument’s part. It’s thought that you’ll have each note in a phrase played by the appropriate articulation for that note alone. So, what a lot of composers do is to play in a phrase while recording multiple parts, such as staccato, sustain DXF and Marcato patches simultaneously, and then edit out the parts after the recording pass. If you’re playing through a whole section with Marcato or Legato or Staccato patches alone and wondering why it doesn’t sound like an orchestra…well, that’s why.
I personally use a lot of the libraries mentioned here, like Cinesamples, Project Sam, Spitfire, VSL, or my personal favorite String Library that isn’t mentioned in this thread yet, LASS. The thing is that none of these newer libraries has some magic ingredient that will make your pieces sound like an orchestra. What will make any sample-driven composition better is always going to be better programming. Whatever you use, you have to learn how to use that product, how to program for it, which patches to use in combination with which other ones, when to layer, when to alternate…it comes with the territory, and it’s a lot of work. It’s just the way it is!
Are there some bogus patches? Sure. Was the whole thing made before anyone did Legato Transitions? Of course. But saying it’s broken, or that it’s some outdated throwback, is just probably not true. There are a lot of really great composers out there doing fantastic work, and still using EWQLSO in part. Mike Patti, THE cinesamples dude, has always used a ton of EWQLSO’s strings (well, until he recorded his own!!!), which I always thought were the weakest part. But what it made me realize about myself, and what I hope you might take away from this, is that when I couldn’t get EWQLSO’s strings to sound good, I couldn’t blame the tools, because they COULD be used better. I had to blame myself, and work to learn how to program it better. Heck, I’ll still be working on learning how to use EWQLSO long, long after its obsolescence.
I probably sound an awful lot like a condescending prick. I’m sorry! I just want to save you the heartache of you saving up more money and throwing it at some ‘cure-all’ library, and then still not getting what you want from it. Just think of it this way: EWQLSO is a training ground for virtually every other articulation-based library out there. If you can rock EWQLSO, you’ll sound fantastic on anything else.
Or, at least that’s just my two cents on it!