I still feel the primary reason users (i.e., me-but I assume I\'m not alone in this) want a way to get their money back is the simple fact that they are ALWAYS buying a pig in a poke. There is no adequate way to predetermine if a library really has the tools that the individual needs. Demos are inaccurate at best-MP3s do not show the true character of the samples and and are virtually always constructed to show the best features, while downplaying the weaknesses (of course...)
I have many gigabytes of samples I will probably never use, and I know for a fact my collection is much smaller than that of many members of this forum. Every one of these libraries was purchased after careful listening to the provided demos, and every one of them proved to be something other than what I needed-I think.
After listening to the works created by others using the same libraries, I know that some of the failure is my own, I don\'t understand how these lobraries were meant to be used. That\'s my problem, and I don\'t want to put it on the developers.
BUT: It would be a great help to the user base if two things could occur-first, each demo be posted in two forms: the demo as it is in final form, and the demo without DSP or tweaks applied, just the real samples as originally recorded. Second, to ship the libraries with actual examples and documentation: this same demo deconstructed-a GSP with the raw samples used (from this lib,) the MIDI file that created the phrase and a list of FX applied, plus a quick exposition of how and why it was done this way.
Yep-training! It\'s not a great additional burden. The demo is already done, just make a copy of the MIDI file and note the tracks that aren\'t from this library, and make a copy of the GSP, again with the other libraries removed. now a couple of paragraphs explaining what was done and why those choices were made, and the user can recreate it him/her self. And when those Altiverb-drenched horns don\'t sound the same with the user\'s Furman Spring Reverb, he can go back to the raw demo and verify that this is where the difference lies, not in his performance.
This does several things-we get to hear both versions of the demo, so we hear what CAN be done, and what to expect out of the box, eliminating much of that \"Omigawd,this is terrible\' feeling we sometimes get when first playing a new file. Plus it gives significant insight into how to apply the samples in the way they were intended.
If this could be done, I think many user post-sale complaints would vanish like the ring-bearer slipping on the One True Ring.
For already-existing libraries, and for those that are so full there is no room on the CD, these files could be posted on the developer\'s website. They\'re not big, a page of tex, another MP3 and a GSP are only a couple megs at best.
Comments? Criticism? Go back to your sandbox and leave the orchestration to the REAL players?