======================================= HOW TO SETUP KTDRUMTRIGGER IN YOUR HOST ======================================= (last updated: 20070225) KTDrumTrigger is a plugin with 1 audio input, 1 audio output and 1 MIDI output. In order to be able to use it, your host must be able to handle this type of plugin. Some hosts (currently?) don't support plugins that send back MIDI, and some do. This document is meant to describe ways of setting up the plugin in hosts that DO support it (compatible hosts). Hosts that currently don't support it (yet?) are listed in the non-compatible hosts section. IMPORTANT --------- If your host is not listed in either section, you will have to find out for yourself or ask your host vendor the following questions: "Does support VST plugins with 1 audio input, 1 audio output and 1 MIDI output? And if so: how do I set it up so that I receive the MIDI sent out by the plugin on a track or an instrument?" COMPATIBLE ========== Cubase VST 5.1 R1 ----------------- 1. Add a mono audio track to your project. 2. Open the VST channel settings of the audio track, add KTDrumTrigger to the insert effects rack (best first in the chain, but not necessarily) and enable it. 3. Put some drums on the audio track. 4. Add a MIDI drum track to your project. 5. Open the VST instruments panel, add a Universal Sound Module and enable it. 6. Select the MIDI drum track, set the instrument to the Universal Sound Module (channel to 10). 7. Make sure the MIDI drum track is selected (important). 8. Press play. 9. You should hear the Universal Sound Module play back the MIDI drum triggers sent by KTDrumTrigger. Note 1: Instead of playing back audio already recorded on the audio track, you can also enable audio input monitoring for that track to use the incoming audio instead. In that case, you don't need to press play. Note 2: Cubase 5 does not seem to have a way to directly specify a MIDI input for a track, other than setting up an instrument in the studio module setup. To receive the MIDI output from KTDrumTrigger on the correct MIDI track, that track *must* be selected in the "Arrange" window. Cubase SX 3 Cubase SX 2.2 Cubase SX 1.06 -------------- 1. Add a mono audio track to your project. 2. Open the VST channel settings of the audio track, add KTDrumTrigger to the insert effects rack (best first in the chain, but not necessarily) and enable it. 3. Put some drums on the audio track. 4. Add a MIDI drum track to your project. 5. Open the VST instruments panel, add an LM-9 and enable it. 6. Select the MIDI drum track, set the input to KTDrumTrigger and the output to LM-9 (channel to 10). 7. Record enable the MIDI drum track (or enable its input monitoring). 8. Press play. 9. You should hear the LM-9 play back the MIDI drum triggers sent by KTDrumTrigger. Note: Instead of playing back audio already recorded on the audio track, you can also enable audio input monitoring for that track to use the incoming audio instead. In that case, you don't need to press play. Bidule (at least as of version 0.6501) -------------------------------------- 1. Create a new instance of KTDrumTrigger. 2. Connect the audio output of another block (an audio file looper for example) to the audio input of KTDrumTrigger. 3. Connect the MIDI output of KTDrumTrigger to the MIDI input of another block (a VSTi drum module such as the LM-9 for example). 4. Connect the audio output of the plugin to the audio input of another block (an audio output device or a mixer for example). 5. If you used a virtual instrument block as receiver of the MIDI triggers, connect the audio outputs of this block to some audio output device (or a mixer). 6. Activate signal processing. 7. KTDrumTrigger should now be sending the MIDI triggers to the block that you connected to the MIDI output. Sonar 2.2 Sonar 4.0.2 ----------- 1. Make sure you have a working version of DirectiXer 2.4 or higher installed on your system (*) and add KTDrumTrigger as a wrapped plugin in the DirectiXer management console. 2. Make sure that the DirectiXer Loopback device is selected in the MIDI devices list (Options -> MIDI Devices...) 3. Add a mono audio track to your project. 4. In the "Track Pane", add KTDrumTrigger to the insert effects of the audio track (best first in the chain, but not necessarily) and make sure it is enabled. 5. Open the KTDrumTrigger editor window and make sure "Send MIDI to host through loopback driver" (the button with the two notes near the top of the window) is enabled. 6. Put some drums on the audio track. 7. Insert an instance of the DXi synth EDIROL VSC into your project (one "MIDI source" track, and the "first synth output" audio track). 8. In the "Track Pane", setup the EDIROL VSC properties as follows: Ch = 10, Bnk = GM2 Drum Set, Pch = STANDARD1. 9. Select the EDIROL MIDI track (important). 10. Press play. 11. You should now hear the EDIROL play back the MIDI triggers generated by KTDrumTrigger. (*) The trial version of DirectiXer can be downloaded from Kirill Katsnelson's web site and will do fine (it produces a short beep every 20-60 seconds or so but this won't affect the MIDI output (only the audio output). More info: http://www.tonewise.com/DirectiXer Note: Instead of playing back audio already recorded on the audio track, you can also enable audio input monitoring for that track to use the incoming audio instead. In that case, you don't need to press play. Sonar 5.2 Sonar 6 --------- 1. Configure KTDT so that Sonar allows you to use it as a MIDI event source. To do this, follow these steps: - in Sonar, go to: Tools -> VST Configuration wizard, make sure "Re-scan existing plug-ins" is enabled, and press "Next" to let Sonar scan your VST directories - in the next window, select KTDrumTrigger and press "Properties" - in the next window, make sure the following items are checked: . "Enable as plug-in" . "Configure as synth" . "Enable delay compensation" - then press "OK", and then "Next" to finish the VST configuration 2. Now comes the "trick(y)" part: - go to Windows "Start" menu, select "Run..." and type "regedit" to start the registry editor (it's possible you need administrator rights to do this) - create a backup of the registry (File --> Export... --> select "All" for export range) - browse for this key: HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk VST Adapter\Inventory at least, this is how it worked on my system; another user reported that he had to change the following key instead: HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Sonar Producer\Cakewalk VST\Inventory - look for a key that ends in KTDrumTrigger.dll and select it (you should now see a list of key-value pairs at the right) - set the value for the "generateEvents" key to 1 (in case the key doesn't exist, create it (type = REG_WORD) and set it to 1) - exit regedit - restart Sonar 3. Add a mono audio track to your project. 4. In the "Track Pane", add KTDrumTrigger to the insert effects of the audio track (best first in the chain, but not necessarily) and make sure it is enabled. You will need to select it from the Soft Synths -> VST section. 5. Go to View -> Synth Rack, and make sure that when right-clicking on KTDT, "Enable MIDI output" is checked (you can only change this when the sequencer is not playing). 6. Put some drums on the audio track. 7. Insert an instance of the DXi synth EDIROL VSC into your project (one "MIDI source" track, and the "first synth output" audio track). 8. In the "Track Pane", setup the EDIROL VSC properties as follows: Ch = 10, Bnk = GM2 Drum Set, Pch = STANDARD1. 9. Now also set the MIDI input (I) for the MIDI track to "KTDrumTrigger 1" -> "MIDI Omni" (if you can't do that, something went wrong in the previous steps and you should probably re-do these from scratch...) 10. Press play. 11. You should now hear the EDIROL play back the MIDI triggers generated by KTDrumTrigger. Note1: There's one thing that might be worth mentioning: it seems that Sonar 6 (but maybe also Sonar 5.2, can't remember) is setup to rescan existing plugins by default. That means that whenever you made the required change in the registry (see steps above), the plugin will be rescanned and the change will disappear again... So: what I did is disable the "rescan existing plugins", quit Sonar, make the change, restart Sonar, and that seemed to work. Note2: It's possible that the registry editing step disappears in the future. The very supportive people at Cakewalk were looking into this at the time of writing. FruityLoops 3.5.6 FL Studio (at least as of version 4.12) --------------------------------------- 1. Add a Sampler channel and load a drum loop. 2. Set its effect track (insert) to FX 1. 3. In the effects panel, select FX track 1 and insert KTDrumTrigger (best in slot 1, but not necessarily). 4. Open the KTDrumTrigger editor window, click the little arrow at the top- left and select "Show MIDI out port". Then, at the top-right set the (out) port to 0 (or another number). 5. Add a VSTi drum instrument (like LM-9, BFD, DR008, ...). 6. Set its effect track (insert) to FX 2. 7. Open the drum instrument editor window, click the little arrow at the top-left and select "Show MIDI in port". Then, at the top-right set the (in) port to 0 (the same number you chose in step 4.) 8. Press play. 9. You should now hear the VSTi drum instrument play back the MIDI triggers generated by KTDrumTrigger. Note: Instead of using the output from a Sampler channel, you can of course create drum loops using several channels, and route the audio output all to the same effects track (insert). Tracktion 1.5.1.2 (so Tracktion 2 probably too) ----------------- 1. Add an audio track to your project. 2. Drag an instance of KTDrumTrigger into the filter chain for the track. 3. Drag a (drum) instrument after KTDrumTrigger in that same track. 4. Put some audio on your track. 5. Press play and tweak the KTDrumTrigger settings. Note: You will see a warning from Tracktion telling you that there are wave clips on your track that may be inaudible as it doesn't output to an audio device. This is because in our setup, not the audio of the wave clip is sent out, but the MIDI-controlled output from the instrument following KTDrumTrigger. Also note that you can make it work by creating a rack and adding the KTDrumTrigger and virtual instrument to that rack and do the signal/MIDI routing yourself. This allows you to connect up the audio output from KTDrumTrigger too, if you like (for example: put the audio output from KTDrumTrigger on the left channel, and the output from the instrument on the right channel, for verification purposes). Drag the rack to the filter section of your track. Ableton Live (as of version 5) ------------------------------ 1. Add an audio track and put some audio on it. 2. Drag a KTDrumTrigger device from the Plug-In Device Browser onto the audio track's Track View. 3. Add a MIDI track. 4. Drag a drum VSTi from the Plug-In Device Browser onto the MIDI track's Track View. 5. In the In/Out section of the MIDI track, you will see that the audio track that has the KTDrumTrigger device on it, appears as a choice for the "MIDI From" property. Select that audio track. 6. Now, to just hear your VSTi play back the MIDI events from KTDrumTrigger, just enable monitoring for the MIDI track. Don't forget to make sure that the MIDI note numbers in KTDrumTrigger correspond to valid note numbers for your VSTi. 7. You can of course also record the MIDI events coming out of KTDrumTrigger, by arming the MIDI track for recording and doing a recording while the audio of the audio track is playing back. SawStudio 3.9c + Midi WorkShop 1.5a ----------------------------------- 1. Make sure you have a working version of DirectiXer 2.4 or higher installed on your system (*) and add KTDrumTrigger as a wrapped plugin in the DirectiXer management console. 2. Open SawStudio and put some audio on an audio track. 3. In the FX Pre Patches for that audio track, add the wrapped DX KTDrumTrigger plugin. 4. Open the KTDrumTrigger editor and make sure "Send MIDI to host through loopback driver" (the button with the two notes near the top of the window) is enabled. 5. Open MIDI WorkShop, go to Options, and select DirectXer Loopback for Port In 01. 6. For Port Out 01, select either: (a) a physical MIDI output (if you want to use a hardware instrument) (b) MWS Virtual Port Out 01 (if you want to use a VST instrument) 7. For one of the MIDI tracks, select Port 01 and channel 10. 8. Make sure MIDI Thru is enabled for that MIDI track. 9. If you chose to use a VST instrument, make sure you have set the SoftSynth MIDI In Port for the instrument to MWS Virtual Port 01. 10. Press play and tweak the KTDrumTrigger settings. 11. You can record the generated MIDI notes by enabling Rec on your MIDI track and pressing Rec instead of Play. (*) Same remark as for the Sonar 2.2 setup above. Note: You can also add the JMS Latency Compensator (available through the SawStudio website) for latency compensation if needed. Just plug it in on the same track as KTDrumTrigger and dial in the number of samples to sync the MIDI playback with the digital audio playback. EnergyXT -------- Supported. Did not test this myself (source = Marc Bangerter), so I can't give you advise on how to do it. NOT COMPATIBLE (please let me know if you find things have changed) ============== Logic ----- Logic currently (?) doesn't support plugins sending MIDI events back to the host. I hope they will make this available in the future somehow... Audio Units ----------- Sending back MIDI from plugin to host is not a part of the AU API, but apparently it can be accomplished in another way, with CoreMidi loopback, same as you can with Windows DXi and loopback drivers. It's not ideal, though, as there's no way of making sure everything is in sync. (source = Sophia Poirier and Angus Hewlett) VST-AU adapter -------------- Because of the above, the Fxpansion VST-AU adapter currently (?) doesn't support sending MIDI output out from the plugin. In any case, it's no use if hosts don't support this anyway... ProTools VST-RTAS adapter ---------------- Pro Tools does not support midi-from-plugin-to-host. So neither does the Fxpansion VST-RTAS adapter. Cakewalk VST-DX adapter ----------------------- This adapter currently (?) doesn't support plugins sending back MIDI events from the plugin to the host. Project 5 --------- Not supported. Did not test this myself (source = Marc Bangerter). Vegas 6 Sound Forge 7 ------------- Not supported. Did not test this myself (source = "Sims"). NOT TESTED YET (please let me know your findings if you tried yourself) ============== ACID ? Samplitude ? Orion ? --- Koen Tanghe - Smartelectronix http://koen.smartelectronix.com