Investing in a sample library can be an important decision. Not only are you committing a sizable chunk of change, you’re also buying into a certain aesthetic, from the all-important overall sound of the library to the way it has been scripted, ease of use, suitability for integration with other libraries, and so on. You will of course want to hear what the library sounds like, so your first port of call will be the demo page of the author company. The tracks on this page will, naturally enough, showcase the sounds in their best light. They’ll be written by composers who know the samples inside-out and how to get the best out of them. They may even have had in input into the coding of the software, so it’s almost as though the library has been custom build to produce the demos you’re listening too, which will give you, the potential customer, a great impression of what can be achieved. But what if your aesthetic differs significantly from that of the programmers and producers? You’ll probably find that simply replacing your existing samples in the music you’ve already written will result in your tracks sounding pretty bad. This is because a sample library is an instrument, and as such it must be learnt. It’s worthwhile to seek out music using the library that’s been written by ‘lay’ composers, not only that produced by the high priests, anointed by the library producers. This will give you a better impression of how the library might sit with your own compositions. Admittedly, it’ll still be different than anything you’ll produce, and you’ll still have to adjust to the new library if you do decide to purchase, but at least this will give you a fresh perspective.
With that in mind, I’m posting a set of tracks that I’ve written using the last library that I bought – Spitfire’s Albion 2, Loegria. I hope that if you’re in the market for a full orchestral library these will help add to your impression of what this particular one is capable of.