Exactly.But some have more hit or miss than others.
And some libraries just plain suck.Suprised to see some of the libraries mentioned in this thread. Goes to show that you'll never make everyone happy if you're a developer as some people just never read the manual ha
Yeah, most libraries don't require a manual to know whether or not it's been over-hyped, or doesn't deliver. Most libraries are instantly playable and you know how it behaves and sounds. In rare cases is it due to a lack of manual reading.Exactly.
And some libraries just plain suck.
my top 2 votes for most revealing manuals:
Every manual should start with several pages of bio and pictures of the producers looking like cool kids.East West Hollywood Orchestra Diamond and Play Manuals
This!Some, for sure. Most of my favourite libraries are not instantly playable.
I think people have misunderstood what I've said. The default patches and instruments should definitely be "playable." But that doesn't mean they fit perfectly with what we want. So tweaking is definitely a must. But at a certain point it can be a draw back if it's required for it to sound "good." Shouldn't the standard patches showcase the sound and playability of the instrument? Yes, tweaks here and there should be used to adapt to your needs, but I don't think you should have to significantly tweak it to make it usable.This!
Maybe I'm some kind of masochist, but I don't really care for instant playability as a criteria for why I like a library or not. I come from the 90s where you had to manipulate everything for stuff to sound good.
What I want from a library is a human feel/sound.
Aren't all libraries plug and play? Sigh, I keep hoping
The answer is "all of them".What I've realized lately as I am building a new VEPro template is that I only need about 25% of what I have, and even that, will cover me for a few years. So the other 75% of what I've paid for is completely wasted $. How many staccato Flutes does one need