2 things ..

1. there was some bug with plug-midiout in steinberg hosts, read back at the forum and you will find posts about it.

2. if i get you right ... there will be no new ports in steinberg hosts after loading an instrument (or fx with midi) ... the curent vst-i can only send midi to another vst-i vila active track ... well basically like a hardwarecontroller at port 7 ... i dont want to insult your inteligence but eventually make sure you havent blocked midi created by nuendo itself for recognizing it on the midi preferences dialog or something ..

Hi, I've spent a lot of time futzing with this but I still can't seem to get it to work at all...

I checked in the preferences and it doesn't seem as if anything is being blocked other than sysex msgs. I tried building the plugin that is to output midi as a standard fx vst and loading it on the vsti that i wanted to send the midi note data to, but nothing happens.

Any one?

Quote: amelia wrote on Sun, 09 July 2006 21:55 ---------------------------------------------------- > Hi, > I've spent a lot of time futzing with this but I still can't seem to get it to work at all...

i am sorry i cant give a clearer answer ... from what i remember those "steinberg vs plugmidiout" problems were solved, as well as that other problem, "live 4 vs plugmidiout" which was said to be a threading issue.

any steinberg app since VST 4.1 supports sending midi from plug-ins and pluggo does support that since OS X version.

so the procedure you do seems right. but if you havent done this yet try sending from a regular VST plug-in (NI synths fx version, TC filtrator, or some of the free DFX or NDC effects send midi) and see if that works. otoh since you have tons of VST-instrument slots these days you could also make your pluggo and instrument and see if that works. ;)

Well one thing needs to cleared up from what I know, I have never heard of a plugmidiout external pluggozized created a new midiout port when the plugin is added. Thats just.... absurd sounding...

Absurd huh? Interestingly enough, its how EVERY other midi capable vsti/vstfx seems to work (including reaktor, which I got midi out working with in about 20 seconds. I'm now several weeks into this issue with pluggo with no results). You create an instance of the effect and it creates both input and output midi ports.

How exactly do you route midi from the pluggo if its not outputting to a specific port? My typical setup for reaktor (a program which i really don't use often) would be to create two midi tracks: the first with the HW controller on the input and reaktor on the output, the second has reaktor on the input and a vsti on the output. If there is no new port created where is the midi data from the pluggo streaming from? How can you control its destination? Any given midi track in cubase accepts only one clearly defined input (unless it is set to any, but even then its only using the inputs in the list)

Its amazing to me that no one has given a clear, concise solution to this. I imagine midiout is a fairly substantial feature and its not like cubase is some obscure piece of software.