@tobbentm This looks like excellent work and sounds very promising. Please keep us updated when you integrate JUCE 6 compatibility. Would really love to see a HISE-example integrating Moonbase as well for us here to test out when it's ready :)

I would like to know about this as well. To my knowledge I have not seen a commercial MIDI plugin that can route directly to and from MIDI ports/drivers, but I do remember that the two MIDI plugins here called "midiIn" and "midiOut" attempt to do this:

https://github.com/sleiner/pizmidi/tree/main/pizjuce

Some of the plugins are buggy, so I do not know if they work or not.

I think some of the challenge on Windows is that host apps can gain exclusive control over a port, and I know DAWs like Cubase/Nuendo are aggressive in this regard, but there are utilities to multiply port connections (such as MIDI-OX, Virtual Cable or Bidule), and therefore making it possible for multiple hosts to access the same MIDI input/output.

I would love it if you found a way to do this in a plugin. On an app I believe you should just be able to have access to the output ports from any of the MIDI devices as long as it is not in use by another app (I think it is first-come-first-serve in that regard).

@d-healey Oh yeah sorry… but since it’s not that important for instruments anyway

I made a little update so it works with the wordpress comments form too.

temp-mail-shield.zip

Think I've solved it.

@Christoph-Hart This is set to 11 in develop. I've changed in to 10.7 and now it's running on Catalina.

b91dabbb-64b6-4fad-82bc-66eef8ae5d14-image.png

350 students now!

And thank you Christoph for your totally non-biased review 😀

@d-healey Might be related to this commit

https://github.com/christophhart/HISE/commit/f9fe4f8bc4cbf7041140449fc6eb7849a593a55d

@Chazrox fr

@Christoph-Hart Correct, but it should match the number of groups the user has set, which is the previous behaviour - I can do this but I figured you'd changed it for a reason.

Here I see allowMidiAutomation, but no mention of MIDI in the rest of the example.

yeah, the example is all about plugin parameters, MIDI is a different concept. But it's listed here:

https://docs.hise.audio/scripting/scripting-api/userpresethandler/index.html#setcustomautomation

It basically replicates the enableMidiLearn property of the UI component but for the automation slot.

Slight update. I've merged the configs from the faust and non-faust exporters into a single exporter - like it is for the other platforms.

For example, you can now use CONFIG=ReleaseWithFaust

@d-healey

I keep accidentally trying to use metaprogramming concepts from c++20 and have to remember Hise is not c++20 😩

It will save groups of nodes, so it can be useful if you've deleted a complex chain and want it back without repeatedly clicking undo.

@aaronventure ah yes, that was in the interface designer. I think it was folding a node that made the mustard go away.

If I use CURL in HISE via a background task (runProcess) to download the file then it only records one download. So it is definitely an issue with Server.downloadFile()

With CURL I'm using -L which is to follow redirects, I think this might have something to do with it since WooCommerce is taking the given URL and forwarding it to the real time-limited URL.

When using g.addNoise() the area parameter is still expecting an array.