What's the difference between "event in" and "midi in"

Cantabile
1

I can’t seem to find this in the manual (ok, too lazy to do an exhaustive search)… sometimes when I load a plugin, I get “event in” instead of “midi in”… and I can’t seem to figure out why, or how to change it. What’s the difference and what is it all about?

2

Hi Kirk,

They are the same thing. The name used by Cantabile is the one reported by the plugin so it varies depending on the developer. It is not changeable AFAIK.

Cheers,

Dave

1 Like
3

I notice the difference mainly between VST2 and VST3 synths, so possibly something to do with the specifications?

1 Like
4

Yes, Steinberg’s VST2 standard uses “MIDI In” as the default name for the non-audio input, whereas their VST3 standard uses “Event In” as the default name (because the VST3 standard generalized it to include other kinds of “events”). Individual VST developers can change the default names, so in general you’ll see VST2s and VST3s with arbitrary names for their input channels. The names shouldn’t have any particular impact for users.

3 Likes
5

Hi @brad. Just a nit-like bug perhaps…

Replying to my own post from a long time back is a bit odd, but I think I finally have a clue about what’s going on here. There seems to be a bug related to the “replace plugin” functionality. When switching out plug-ins this way, if the replacement plug-in doesn’t match the old plug-in with regard to the midi in configuration, it may come up with a disabled midi input and no way to enable it. E.g. the old plug-in says “midi in”, and when the new plug-in is loaded it still says “midi in”, but its midi input is disabled and cannot be enabled. However, when I copied and pasted the new plug-in to a completely new instance, the new instance switched from “midi in” to “event in” and everything worked correctly. So, something about the object state from the old plug-in persists when doing “replace plug-in”, and sometimes this is not compatible with the new plug-in.

Not a big deal, now that I think I have a work around, but thought I would mention it in case others have run into it.

6

Yes, this is a bug, but it’s only in the routing view - the table view doesn’t seem to be affected. I’ll get it fixed, in the meantime the work around is to replace the plugin, save the song (or rack) and then reload it (easiest via File → Revert Song/Rack).