Plug'n Script as Audio Units but different hosts.

[ValliSoftware]

I created a Plug'n Script and it shows up and works well as a MIDI FX in Logic Pro X, but in Kushview Element it does show up but it doesn't work.

Is there different build settings that I need to make to get it to work in Kushview Element

[Blue Cat Audio]

I don't know this other host, but it is probable that it does not support AU MIDI FX (it is a rather new specification, and most hosts even do not support MIDI output for regular Audio Units...). If it supports VSTs, you may want to try that instead. Otherwise maybe if you change the type of Audio Unit to "Instrument" or "Audio FX" it may work.

[ValliSoftware]

I don't know this other host, but it is probable that it does not support AU MIDI FX (it is a rather new specification, and most hosts even do not support MIDI output for regular Audio Units...). If it supports VSTs, you may want to try that instead. Otherwise maybe if you change the type of Audio Unit to "Instrument" or "Audio FX" it may work.

Odd, it sees it and when I put in in the workspace, the green dots are audio and the orange dot is midi.
The top is input and the bottom is output.
So I have stereo audio input and output and a midi input and output.

If you notice, it even sees your Plug'n Script MFX

[Blue Cat Audio]

What does happen when you connect it?

[Dewdman42]

There is currently a bug in JUCE related to hosting AUmfx plugins. its possible to hack around it in the juce modules with a few lines of code, but the JUCE really needs to rectify this. Even the demo AudioPluginHost that they provide with JUCE fails to properly host AUmfx plugins...it hosts them, but the midi ports don't work.