Problems with DirectX versions classified as DXi's

[TheSteven]

I would humbly suggest that the DirectX versions of the Blue Cat plug-ins be recompiled as DX instead of DXi.

I think that Blue Cat's plug-ins are great so please don't take this suggestion as critique on their quality.

It just that by classifying them as DXi causes some Hosts, for example Sonar and Project5, to identify Blue Cat plug-ins as 'Direct X Instruments' and to exclude listing them directly in FXs plug-in menus.

What is the difference between DXi and DX effects?
DXi effects are MIDI controllable DirectX plugins. It's the same as DX effects plus MIDI control.

I think that most people tend to think of DX/DXi in the same context as VST/VSTi. If its an instrument its VSTi/DXi, if its an effect (delay, compression, etc.) its a VST/DX.

Best Regards,

...Steven

[Blue Cat Audio]

Hi, thanks for your feedback. I know this can be an issue for some hosts (and sometimes a pain, such as with Sony applications), but unfortunately it is the only way to enable MIDI control for DirectX plugins. The difference with VST is that VSTi are specified as Synthesizers, whereas with the DirectX plugins the hosts do not make the difference (even if they could!).

That's the reason we have released the free DXi Manager that lets you choose for each plugin if you want to enable/disable MIDI support. Once MIDI is disabled, the plugin is just seen as a "standard" DX plugin.

This tutorial about DXi plugins in Vegas show you how to do it (just do not read the ugly registry things that may be necessary for Vegas due to a bug in their software).

[TheSteven]

Thanks for the quick reply and explanation.
I was afraid that this might be the case.

Best Regards
..Steven

[Blue Cat Audio]

You are welcome.

I think having the MIDI I/O on a plugin is really worth the trouble...

It's a pity these host applications did not do their job better to check wether a plugin is a synth or not!