KTDrumTrigger setup in your favorite host

[KoenTanghe]

[This thread is meant for questions/answers related to setting up KTDrumTrigger in different hosts.]

First of all, from the "read me", just in case:
"You will need to find out how to route the MIDI output of the plugin to the MIDI track or instrument you want it to be sent to. This is different in every host:
- in track-based hosts (like Cubase), inserting the plugin on a mono audio track will usually add the plugin to the list of available MIDI inputs for your MIDI tracks
- in modular hosts (like Bidule), you will see 1 input (audio) and 2 outputs (1 audio and 1 MIDI): just plug in two audio cables and a MIDI cable and you're all set"

I (still) don't own a Mac myself sadly enough, so I won't be able to help out people on Mac (Marc from DestroyFX always does the Mac builds for me)

Within the next days, I will make a few more detailed descriptions for the hosts I have used it in on my machine (Windows2000 with Cubase 5.x, Cubase 1.x, Bidule, FruityLoops demo) and I would appreciate it if other people would post ways of setting it up in their host. I will collect the descriptions, add it to the KTDrumTrigger web page and also add it to the "read me" for the next release.

I do hope hosts like Logic can send MIDI output from a plugin to a MIDI track or virtual instrument somehow...

And if host developers would read this: it would be great if I could get an NFR version of your host for testing if that's possible.

Until soon,

Koen

[KoenTanghe]

News flash:

About KTDrumTrigger and Audio Units:
I heard it should be possible to do that in AU too (AU API update that came with QuickTime 6.4 and/or Mac OS X 10.3), but this is still rather new. It will probably become possible in the near future if some major hosts start supporting it. But not right now apparently.

About KTDrumTrigger and the VST-AU adapter:
Because of the above, the Fxpansion VST-AU adapter currently does not support sending MIDI output out from the plugin. In any case, it's no use if hosts don't support this anyway.

About KTDrumTrigger and Logic:
Logic currently does not support plugins sending MIDI back to the host. I hope they will make this available in the future somehow...

In the next episode: how-to's for hosts that do support audio-processing plugins sending MIDI back to them... Stay tuned...

[Bram]

fruityloops:

1. set midi-out port of KTDrumTrigger




2. load a VSTi and set midi-in port

[Bram]

bidule:

[KoenTanghe]

Thanks Bram!

In the meantime, I also added a small document to the KTDrumTrigger webpages describing step-by-step how to setup the plugin in some hosts + I started to make a list of non-(or not yet?)-compatible hosts too.

You can find that here (just look in the "Some hints to get started" section).

I'll also add it to the "read me" file with some screenshots (that was a good idea).

Koen

[Lazlo Minimart]

in track-based hosts (like Cubase), inserting the plugin on a mono audio track will usually add the plugin to the list of available MIDI inputs for your MIDI tracks

I use Nuendo but would expect it to work the same as Cubase. I do not see the plugin appearing in my list of available MIDI inputs. All I see are my soundcard's two MIDI inputs. It makes sense that it should work this way, but I don't see it happening.

[KoenTanghe]

I use Nuendo but would expect it to work the same as Cubase. I do not see the plugin appearing in my list of available MIDI inputs. All I see are my soundcard's two MIDI inputs. It makes sense that it should work this way, but I don't see it happening.

Sorry Lazlo, I don't have Nuendo myself (and there's still no demo version available), so I can not try things out in Nuendo
However, I did not mean that KTDrumTrigger should show up as a new device in your system, but rather as a new input device in the input list for your MIDI tracks. At least that's what happens in Cubase SX 1 (there's a screenshot over here).
Also note that you need to put the plugin on an audio track first (as an insert effect). Only then you will see it appear in the MIDI input list for your MIDI tracks.

Could anyone else here who has Nuendo try it out in that host?

[Lazlo Minimart]

I use Nuendo but would expect it to work the same as Cubase. I do not see the plugin appearing in my list of available MIDI inputs. All I see are my soundcard's two MIDI inputs. It makes sense that it should work this way, but I don't see it happening.

Sorry Lazlo, I don't have Nuendo myself (and there's still no demo version available), so I can not try things out in Nuendo
However, I did not mean that KTDrumTrigger should show up as a new device in your system, but rather as a new input device in the input list for your MIDI tracks. At least that's what happens in Cubase SX 1 (there's a screenshot over here).
Also note that you need to put the plugin on an audio track first (as an insert effect). Only then you will see it appear in the MIDI input list for your MIDI tracks.

Could anyone else here who has Nuendo try it out in that host?

Actually, the way you explained it was exactly as I tried it. In your screenshot where it says "in: KTDrumTrigger," I only have "Dakota 1" and "Dakota 2" (my soundcards two MIDI inputs) as options. There is not a KTDrumTrigger option. It makes sense that it should be there, but it is not.

[KoenTanghe]

Aah OK, sorry I misunderstood you. In that case, I have no idea, really... Maybe Nuendo doesn't support plugins with a (mono audio in/out + MIDI out)-configuartion? I know some host programs don't allow plugins to send back MIDI to the host, but I would not expect Nuendo to be one of them though...

Koen

[KoenTanghe]

I asked on the VST plugin developer list about Nuendo and plugins sending back MIDI to the host, and someone says that "It works since Nuendo 2". So my next question would be: which version exactly are you working with?
Koen

[Lazlo Minimart]

1.6. I own 2.0, but haven't upgraded from 98 to XP, whihc 2.0 requires (too busy with active projects). So guess I'm hosed until I upgrade my OS. Oh well. Thanks!