MidiFX Plugin from Hise
-
@ulrik setting the AU_MidiProcessor flag might be useful for Au export. Let me know if this changes anything then I‘ll hook it up into the exporter.
-
@Christoph-Hart I'll experiment with it, thanks!
-
@d-healey @Christoph-Hart aha, you were talking about compiling Hise as a plugin right?
That's why I couldn't find the settings in the Hise Standalone project
Those settings are in the Hise Plugin project not for the the Hise standalone.I'm talking about compiling a MidiFX plugin from Hise standalone.
-
@ulrik I was talking about compiling your project as a plugin, not compiling HISE. Those settings are accessible in your project's .jucer file.
-
@d-healey ok, I didn’t know that, great thank you
-
This post is deleted! -
@Christoph-Hart said in MidiFX Plugin from Hise:
@ulrik setting the AU_MidiProcessor flag might be useful for Au export. Let me know if this changes anything then I‘ll hook it up into the exporter.
This is from the Ableton Live website
I did not know about this limitation before -
@ulrik Did you know of this little quirky setup needed for Ableton Live MIDI output, because I did not. My VST2 from HISE on windows work fine both in Ableton Live and Reaper.
https://help.ableton.com/hc/en-us/articles/209070189-Accessing-the-MIDI-output-of-a-VST-plug-in
-
@jonhallur Beautiful find! Thank you for showing, works great with Midi FX plugin vst2
-
@ulrik More updates.
If you like to use modulators and MIDI I have found the least changes you can do to the HISE code to make that happen.
diff --git a/hi_core/hi_core/MainController.cpp b/hi_core/hi_core/MainController.cpp index 2863465c6..5a40b119e 100644 --- a/hi_core/hi_core/MainController.cpp +++ b/hi_core/hi_core/MainController.cpp @@ -975,7 +975,7 @@ void MainController::processBlockCommon(AudioSampleBuffer &buffer, MidiBuffer &m } } -#elif HISE_MIDIFX_PLUGIN +#elif defined(HISE_MIDIFX_PLUGIN) || defined(ALLOW_MIDI_OUTPUT) synthChain->processHiseEventBuffer(masterEventBuffer, numSamplesThisBlock); @@ -1149,7 +1149,9 @@ void MainController::processBlockCommon(AudioSampleBuffer &buffer, MidiBuffer &m #endif #if !HISE_MIDIFX_PLUGIN + #if !ALLOW_MIDI_OUT midiMessages.clear(); + #endif #endif }
Then I added the following extra definitions
JucePlugin_ProducesMidiOutput=1 JucePlugin_IsMidiEffect=1 ENABLE_ALL_PEAK_METERS=1 ALLOW_MIDI_OUT=1
Export the plugin as a FX (not as MIDIFX) and Bob is your uncle.
-
@jonhallur If I change the code to this and export the plugin as FX plugin, will it really load as a Midi FX plugin?
-
@ulrik With out knowing it completely, I don't think under the VST2 or even VST3 (I´ve done some professional JUCE work before using VST3) there is no concept of a MIDI FX plugin.
At least in JUCE, you just tell the host that you want to receive and/or send MIDI. You can do the same with sound, stating how many channels you want to input/output etc.
I have no idea what a given host does with that information. The host will ask a plugin upon instantiation weather it will produce audio and/or MIDI. A JUCE plugin can answer yes to both. Perhaps some hosts will decide to put some plugins into some categories, but it works on Windows both in Reaper and Ableton Live
-
@jonhallur Ok I see, I might give it a try and see if also Logic will accept it as a MidiFX plugin, thanks! :)
-
@ulrik Please let me know, I don't have a Mac and I'm very curious about Logic.
-
@jonhallur I don't know if I did. it the right way but...
I changed the code (as you described), compiled Hise Standalone with the extra definitions, exported as FX plugin from Hise but it didn't show up in Logic under the Midi FX slot
-
@jonhallur am I supposed to set the extra definitions in Hise preferences as well?
And do I set the Hise projucer "HISE_MIDIFX_PLUGIN" enabled? -
@ulrik No, I did not mess with the ProJucer project file at all it's just settings in HISE.
I also did not compile the HISE Standalone editor again, if that is what you mean.
-
@jonhallur great, I'll test again
-
@ulrik I found some crazy behavior using Hise MidiFX plugin inside Logic
When standing on the MidiFX activated track it works fine, as soon as I stand on another track it fails, the arp is running but it's not producing any midi out to the instrument even though the arp is running as it should
Compared to the Logics own arpeggiator
Any thoughts about what's happening here is much appreciated
-
@ulrik We got CC output to work as midi fx plugin if we export as AUv3 , but we are encountering problems with ui size and and some other minor ui issues. So I would love to be able to do a normal AU midifx plugin , did you make any progress with that ?