参考文章:Using EastWest's WordBuilder with Symphonic Choirs in REAPER To support my work as a producer of orchestral scores & cues, I've been drooling over the prospect of having a digital choir I could make sing whatever I want for well over a year. When I recently found EastWest's Symphonic Choirs with WordBuilder discounted in price by a couple hundred dollars I went ahead and took the plunge. The box arrived intact and unopened, the thirty-three gigabytes of data installed without a hitch, and then I opened my Reaper DAW.
And I got stuck. Really stuck.
WordBuilder comes out of the box with easy integration in programs like Cubase and Pro Tools. However, seeing as how I'm still on the low budget end of things I've been using Reaper by Cockos. The DAW works great and I have yet to find a virtual instrument (barring a few freebies of questionable programming) which won't get along with it. After nearly a week of reading some internet forums, most of which included cries for help from other users of Reaper who were struggling to get WordBuilder to work, I became discouraged. Many folks couldn't get the choir to sing words when loading it as a VSTi. Others could hear the words when recording but were stuck with "ooohs" or "aaahs" when rendering. After reading the multitude of sob stories on the internet, I had all but resigned myself to the fact that I'd likely have to plunk down half a grand for a new DAW.
But yesterday I decided to carefully pore over the manual for WordBuilder. Reaper is not mentioned at all in it. However, what one does notice is the fact that running WordBuilder and Symphonic Choirs in their stand alone modes is a simple matter of directing WordBuilder's MIDI output to Symphonic Choirs input. The trick here is that WordBuilder actually sends six separate MIDI channels to make the voices sing words. I thought to myself, could it really be that easy if using the choir in Reaper?