Sunday, December 6, 2015

Tutorial: Making a Multi-output Drum Kit in UVI Falcon

UVI Falcon has taken the soft synth world by storm since its release, but there's not a whole lot of information out there yet on how to do certain things with this powerful instrument.


This tutorial walks you through the following aspects of building your own sample-based drum kit in Falcon:
  • Using layers in Falcon to send different drum sounds to separate audio output channels that you can mix and process individually in your DAW.
  • Setting up an exclusive group (or "choke group") to simulate real hi-hat behavior.
  • Using Falcon's "custom drop" feature to import multiple samples into a single keygroup.
  • Using the round robin trigger mode to add variety to individual percussion sounds.
  • And finally, we'll see how to apply some of this knowledge to modifying kits in UVI's excellent Beat Box Anthology collection of classic drum machine samples.
To help you get up to speed quickly I've put together a free mini sample pack for this tutorial, which you can download from the Ultimate Outsider Software page. We'll start off by building the kit's layers and importing samples, and then complete the kit by setting up the multi-channel audio routing in a DAW. As an added bonus, I'll show you how to create or modify your own kits using samples from UVI's Beat Box Anthology. I'm using Ableton Live 9 in my examples, but most of what's covered here applies regardless of what DAW you're using. (Part 5 of the written tutorial also includes configuration steps for Steinberg Cubase.)

TUTORIAL VIDEO

I produced a YouTube companion video that covers everything in this written tutorial except for Cubase configuration.



If you prefer written tutorials, read on!

PART 1: ADDING THE KICK LAYER

  1. Open up a new DAW project and create an instance of Falcon. Make sure your left and right panels are both visible. You toggle the panels on or off using the Show/Hide Panel buttons at the top of the Falcon window. Also make sure all the sections of the Edit tab (Program, Layer, Keygroup, Oscillator, Mapping, etc.) are visible by enabling their respective icons. Falcon automatically creates a new, empty program (patch) when you start a new instance.

  2. Download the Falcon tutorial sample pack from the Ultimate Outsider Software page. Extract the samples to a local folder and then browse to them in the file browser tab of Falcon. I've added my copy of the folder to the Favorite Places section of the browser.
  3. Click the wrench icon near the top of the Falcon window to open Falcon Preferences. On the General tab, enable the One Shot option next to Sample drag'n'drop mode. This will ensure that our drum samples automatically play all the way through when triggered.
  4. You'll notice that each of the samples includes the intended MIDI note value in its name. Drag the Kick C1 sample to the C1 key on Falcon's virtual keyboard. This creates a new layer ("Layer 1"), a new keygroup ("Kick C1.wav"), and a new oscillator that contains your sample. You should be able to trigger the sample with your MIDI controller or by clicking its note on the virtual keyboard. If you select the List pane in the left tab of Falcon, you can see the new layer and keygroup.

    Tip: The lower you click on the virtual keyboard, the higher the velocity of the auditioned sound. This velocity sensitivity happens by default, and is the result of velocity modulation to the amp envelope, as shown in the above screenshot (bottom of the window). If you disable or delete the Amp. Env modulator, you will disable velocity sensitivity for this keygroup.

    Note: If you didn't set your drag'n'drop preferences to One Shot in step 3, you can apply one-shot mode to an individual sample oscillator by right-clicking inside the waveform and choosing Set as One Shot on the shortcut menu.
  5. In the List tab of Falcon's left pane, rename the current layer by double-clicking the layer name and typing: Kick

PART 2: ADDING THE SNARE LAYER

  1. Click the + sign in the Layer(s) row to add a new layer.
  2. Double click the new layer's name and rename it to Snare. Leave this layer selected (so that it's highlighted.) The Keygroup(s) pane should appear empty.
  3. Drag the Snare D1 sample from the file browser to the D1 key of the virtual keyboard.

PART 3: PUTTING HI HATS IN AN EXCLUSIVE GROUP

  1. In the List tab, click + in the Layer(s) row to add another layer, and rename the new layer to Hi Hats.
  2. Making sure that only the Hi Hats layer is selected, drag the Closed Hat F#1 and Open Hat A#1 samples to their respective places on the virtual keyboard. Your single Hi Hats layer should now have two keygroups, each containing a single sample oscillator.
  3. In order to make the hi hats behave more like real cymbals, we're going to put them in an "exclusive group," where one hi hat sample cuts the other one short when playing. With the Hi Hats layer selected, scroll the Keygroup(s) view all the way over to the right so you can see the ex. group column.

    Note: If you can't find ex. group, right-click any of the column headers in the Keygroup(s) pane and make sure to check ex. group in the list.
  4. For each of the keygroups under Hi Hats, set the ex. group field to 1. (You can change the values by dragging your left mouse up or down on the fields, or by double-clicking them and entering a new value.) This puts the hi hats into the same exclusive group. Now when you play the two hi hat samples very quickly, triggering one of them will cut the other one short.

PART 4: IMPORTING ROUND-ROBIN SHAKER SAMPLES

  1. Add a new layer in the List tab and name it Shaker.
  2. Make sure that only the Shaker layer is selected, and then SHIFT-select all of the Shaker A3 samples in the file browser. Notice how all of these samples end with something like "rr1?" Falcon recognizes this as an indication that these are intended for a round-robin keygroup.
  3. Hold down ALT on Windows (or OPTION on Mac) while dragging the shaker samples to the A3 key. This brings up the Sample Drag'n'Drop dialog. Select NoteName RoundRobin under Mapping method and make sure Destination points to your Shaker layer, and then click OK.
  4. You should now find that your Shaker layer has a single keygroup that contains all eight shaker samples. Each time you press A3 on your keyboard you will hear a slightly different shaker sample.
  5. At this point we have a basic drum kit that sends all audio to the plugin's "Main Out" bus. Save your work now by clicking the wrench icon and selecting Save Program and Samples. In addition to saving your program as a UVIP file, this command is supposed to create a folder in the same directory containing all samples used in that program.

    Note: On version 1.0.1 of Falcon, Save Program and Samples doesn't appear to actually save the samples (not on my Windows DAW PC anyway). I have found that the Save Program and Samples as command, however, does correctly export the samples. Something to keep an eye on.

PART 5: PREPARE YOUR DAW FOR MULTIPLE PLUGIN OUTPUTS

Before we start setting up our Falcon kit to use multiple outputs, we should make sure our DAW is ready to receive audio from the plugin's various outputs.

Ableton Live

The easiest way to do this in Ableton Live is to make use of the External Instrument device (only available in the Standard and Suite versions of Live).
  1. The MIDI track hosting our Falcon instance receives audio from Falcon's "Main Out" master stereo output. When you're working with multiple outputs, it's best not to assign any parts to Main Out, since that bus is also shared by Falcon's four Aux buses. What this means for our DAW setup is that we'll need four additional MIDI tracks to receive audio from the four layers in our drum kit. I've named my additional tracks Kick, Snare, Hi Hats, and Shaker.
  2. Drag an External Instrument device to the Kick track. Point its MIDI To to the Falcon track, channel 1. Under Audio From, select the Falcon 2 output.
  3. Repeat this for the Snare, Hi Hats, and Shaker tracks, only set their Audio From entries to Falcon 3, Falcon 4, and Falcon 5, respectively.
  4. Select the Falcon track and make sure that it's armed for MIDI input.

Steinberg Cubase

Since all the screenshots up to this point use Ableton Live, we'll take the Cubase setup from the top. I'm going to use the "Rack Instruments" approach (versus the "Track Instruments" approach), because you can use the rack method in all versions of Cubase from 5.0 on. These steps will definitely work in the Pro and Artist editions of Cubase, but probably apply to the limited editions as well.
  1. In a Cubase project, go to Devices > VST Instruments an add Rack Instrument instance of Falcon.
  2. When Cubase asks if you want to create a MIDI track assigned to Falcon, click Create.
  3. Back in the VST Instruments window, click the Activate Outputs icon on the Falcon instance.
  4. In the menu that appears, make sure to enable outputs Falcon 1-Falcon 5. The plugin's Main Out goes to Falcon 1, and the other four outputs are for the individual drum layers.
  5. If you expand the Falcon folder under VST Instruments in your arrangement view you should now see five separate VST channels, one for each output pair enabled on the plugin. You can set up inserts and sends on these channels just like regular audio tracks. In my example, I renamed the VST channels to represent which drum parts they would receive. I also renamed the MIDI track that's routed to the Falcon instance.
    The Cubase project, after renaming the VST channels and MIDI track and importing a MIDI loop.

PART 6: ASSIGN LAYERS TO SEPARATE OUTPUTS

  1. Back in Falcon, locate the output column in the Layer(s) tab of the left pane (you may have to scroll right to see it). This column is actually hidden by default, so if you cannot find it, right-click one of the column headers in the Layer(s) list and then click output on the shortcut menu. 
  2. For each layer in your kit, select a different individual output to match the Audio From selections you picked in the previous section. (Kick = Out 2, Snare = Out 3, Hi Hats = Out 4, Shaker = Out 5.)
  3. Now when you play the appropriate notes on your MIDI controller you should see audio coming in on separate tracks in your DAW. Use Save Program and Samples as to save the multi-output version of your kit if you like.
  4. The sample pack I put together for this tutorial includes a MIDI drum loop that you can import in your DAW to test the kit out. Drag the clip onto the MIDI track where your Falcon plugin instance is hosted. You can now apply your own effects and EQ to each drum part in your Falcon drum kit!
  5. At default track volume, the shaker layer is pretty loud in relation to the rest of the kit. If you'd like to adjust the volume of a specific layer, go back into Falcon and locate the volume column in the Layer(s) pane of the List view. You might have to scroll to see it. Also, the volume column is hidden by default, so right-click one of the other column headers and then click volume on the pop-up menu if it's not currently shown. Make sure that only the layer (or layers) you wish to adjust is selected and then adjust the volume field for that layer by dragging down or up.

PART 7: MODIFYING KITS IN BEAT BOX ANTHOLOGY

UVI's Beat Box Anthology is a great collection of kits and samples of dozens of classic drum machines. All of the kits in the collection are set up to send all sounds to the instrument's Main Out. Users of the free UVI Workstation are stuck with this limitation, but Falcon gives you the ability to tweak these kits to suit your needs. Beat Box Anthology is included in UVI's Vintage Vault bundle, and the following steps assume you have both Falcon and Beat Box Anthology installed.
  1. Let's start with a new instance of Falcon, and expand the Soundbanks category to locate the GM Kits under Beat Box Anthology. (The General MIDI kits will work with the MIDI loop included with my Falcon tutorial sample pack.)
  2. Double-click one of the kits to load it into the currently selected Falcon part. I've selected the DR Tracks kit, which is based on the Sequential Circuits Drumtraks unit from 1984.
  3. On the List tab of the left panel we can see that this kit contains two layers. One layer is for the hi hat choke group, while all other sounds in the kit reside on the other. We can assign the hi hats to their own output the same way we did in Part 6 earlier. First, make sure that only the HH layer is selected in the List view, and then scroll over to locate the output column in the Layer(s) section. If you don't see it, right-click one of the column headers and then click output in the shortcut menu to add it to the Layer(s) view.
  4. Change the output setting for this layer to Out 4 (to match the assignments we used in part 6).
  5. For the rest of the drum sounds, we'll need to edit the keygroups assigned to individual samples in the kit. First, make sure that only the Drums layer is selected, and then ensure that you can see the output column in the Keygroup(s) view. Like with the Layer(s) view, the output column is hidden by default.
  6. Now assign the outputs of the individual keygroups to your desired output channels. You might want to hide some columns in your Keygroup(s) view for this step so you can see the keygroup names and outputs without scrolling. You might also find it easier to work in this view by sorting it in root key order, and you can SHIFT-select and CTRL-select multiple keygroups to change their output settings at the same time. Here are output assignments that match what we did when building our own kit in the previous sections, in order of root key note value:

    B0 & C1 (kicks): Out 2
    D1 & E1 (snares): Out 3
    (The HH layer should already be on Out 4)
    A3 & A#3 (shaker): Out 5
     
  7. Next set up your DAW to accept multiple plugin outputs just like we did in section 5 above, and don't forget to arm the Falcon track to intercept your MIDI if you're planning to test your setup out with your keyboard controller.
  8. If you have my Falcon tutorial sample pack, drag the Falcon Drum Loop MIDI clip onto your Falcon plugin track and loop it.
  9. Important: Don't forget to save the modified versions of your kits! Click the wrench icon and use Save Program as or Save Program and Samples as to back up your work.
  10. Unlike most of the UVI libraries, Beat Box Anthology includes individual drum samples that you can access in the file browser to create or modify your own kits. If you have the auto preview button activated, you can audition the samples while you browse by selecting them with your mouse or the arrow keys.
  11. You can drag these samples from the file browser right into your kit.
Well, that's it for now. Check out the Ultimate Outsider YouTube channel or the blog at UltimateOutsider.com for more production tips. Enjoy!

4 comments:

Pilcho Graggins said...

Hey Josh,

This is not at all relevant to your post above, though I do dabble in LMMS and FLStudio :).

I just wanted to say that I created a simple icon for GWX Control Panel. I have uploaded the Version 1 of the icon, a .psd, and a Krita file (I made it in Krita) if you want to make edits.

Please feel free to use the icons if you are so inclined. I do not ask for compensation in credit, or money. Just trying to be helpful in what ways I can, as I respect and appreciate your efforts. The .ico file (Version 1), a .psd, and a Krita work file are available here : http://www.filedropper.com/gwxicons

Thanks again for helping all those who would rather not be using Windows 10 at present!

Ultimate Outsider said...

@Pilcho - That's really generous of you, thanks!

Michael Rife said...

I'm a computer tech and have been dealing with KB3035583 for some time now. Until today, my method has been much like yours but without being aware of and using your control panel. Today I was dealing with a customer and her 2 computers and found on both that I had to uninstall the update exactly 3 times until Microsoft finally gave up. Despite even having WU set to "Never" install updates, the update was again installed following the uninstall re-boot. We'll see if your control panel overcomes this new MS BS obstacle.

Ultimate Outsider said...

@Michael - My program won't prevent KB3035583 from installing if the user's Windows Update settings allow it, but the "Delete Windows 10 Programs" feature will neutralize the patch, removing all the program files and scheduled tasks associated with it. Please see the Troubleshooting guide for more info on this.