@Orvillain apparently, the problem is in the Reaper itself, everything works fine for me on version 7.23.

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 Thank you so much
@ustk @Christoph-Hart 👍

@d-healey I did compile it from source (my first time compiing anything as well) and it was the develop branch. Maybe I'll compile it once more just in case I did something wrong.

Thanks for your help, David! I can't believe how fast you responded. I hope to have more meaty questions in the future.

@Christoph-Hart Is there a possibility to remove the shadow from the Favorite Icon next to the preset in the default Preset Browser?

@d-healey @Oli-Ullmann haha yes that's why I will leave it up. I think I learned about this before (watching David's video) and just sort of forgot about what the boolean was for. 😆

@Christoph-Hart
I just saw that you fixed it. Thanks very much! :-)
I'll let you know if I encounter any problems.

@Chazrox
Glad you like it. To be honest, there's not that much to do, since @Christoph-Hart has already done all the hard work for us.

Creating the WaveTable:
All you have to do is fill a buffer, which you then load into the WaveTable synth using the WaveTable controller.

Christoph has provided us with some examples in the documentation:
https://docs.hise.audio/scripting/scripting-api/wavetablecontroller/index.html

Appearance:
To make the whole thing look interesting, I drew a panel based on the slider values of a slider pack. The slider pack is transparent and the panel is behind the slider pack.

So you use the values of the individual sliders in the paintRoutine of the panel.

@paper_lung check the MonolithSplitAmount parameter inside the xml converted to monolith samplemaps. If the value from there is higher than you have in the archive parts, then the sampler will not find the monolith. There is indeed a bug in Hise that can add the previous values of the parts of the split monolith when exporting to the monolith. I recently report this bug. But is no actually for fix. Maybe this with low priority, if you have this bug - you can fix it by yourself.

@Christoph-Hart Screenshot 2025-10-01 at 5.14.38 AM.png

sweeet! 🙏

@It_Used Check out my Bootcamp course, I cover the floating tile meter in it. You can still apply your design to it using laf.

@Christoph-Hart Thank you!

@ustk ah yes that's an easy fix.

@pcs800 oh great!

@pcs800 said in Creating a pop out window with an eq or something on it:

post the info

up to you.

@Christoph-Hart Performance is acceptable here. Thanks!

@Christoph-Hart haha, absolute madness from Apple, no one could have expected such an unnecessary change
thank you for the quick fix, that was indeed the solution - now the export runs just fine! you saved me from downgrading my OS again^^

Lets see when I will encounter my next bug with this new macOS update...

@ustk Mmm... loading the only network I have with a dynamic blocksize node in another project works...

@Christoph-Hart Thank you, hugely appreciated!

@Christoph-Hart I gave this a shot but this wasn't the solution. It's my mistake.

@d-healey you are exactly right.

Basically for anyone who ends up here I recommend looking at and comparing the Info.plist that is part of the .component bundle. In my case I had changed the company code and this is why the plugin wasn't being recognized properly. Strange I couldn't find this in my Github commits but my issue had nothing to do with the version number.

Thanks both for your responses!