@Christoph-Hart

Gotcha. Maybe I'm thinking about this all the wrong way, and the best approach for me is to use the classic method of handling all my RR logic inside a midi processor script.

I haven't got to implementing any of this yet. I'm still just thinking about it. But as I see it, and from experience, a hihat needs the following:

Ability to trigger multiple articulations, with round robin functionality. Ability to fade out or "choke" earlier voices when a new voice of a different articulation is triggered (Open to closed) Ability to crossfade from one articulation to another, based on incoming midi CC (usually CC4) Some way to trigger the 'tail' of a 'more open' articulation when going quickly from closed to open. Instantly choke all voices when a pedal articulation is triggered.

I was hoping the complex group functionality would do a good chunk of this. But I suppose it is the wrong tool?

@d-healey said in Moonbase:

@tobbentm Is it compatible with GPL plugins?

Since our JUCE module is closed-source, no.
You'd have to dual-license it, with a separate version that has DRM in it.
Alternatively, you could integrate on your own, or use other libraries to integrate with.
Syl is currently working on a pure C++ (no JUCE dep) open-source thing here, but it's very early days: https://github.com/SLM-Audio/moonbasepp
We're getting more and more requests for a simple C++ library, so we may try to build an alternate open-source solution ourselves next year.

@d-healey I'd never heard of them til I seen your post. It sounds promising.

@bendurso Integrating with HISE is definitely a priority. What types of features would you be interested in?

@Lindon I hear you brother. I think some of these things could be issues to smaller/startup developers. I'm not looking to create a marketplace in terms of just onboarding developers and selling their products for 2 main reasons. 1. Talk about a saturated market. 2. I just sold a business like this last year to further pursue other things.

@tobbentm Moonbase looks great. Yes, I've 10+ years working for and with resellers so I've got a good idea of the ins and outs of that market + a collection of contacts. I have a few thoughts on keeping things in order across the board. I would definitely love to chat. I'll send you a DM and go from there.

@lacroix Can you show me a screenshot of your plugin code?

@ulrik awesome

@DanH said in Preset Browser - List item background:

@ustk ok back on this again 😆

What would be a crafty way of adding multiple 'tags'?

So the preset name could be something like BA_LD_PRESETNAME to indicate that it's a bass as well as a lead sound.

Maybe some kind of divider is needed...

Really I watch this sort of discussion a lot here, that can be characterised as "how to bend the preset browser to my will". My experience is that its nearly trivial ( a few days at most) to write your own custom preset browser...

@griffinboy can you give me an example with screenshot? my english its so bad and i think that the google translate its giving me wrong traduction

@Chazrox

Ahh, I see! Thanks duder!

@DanH @Christoph-Hart Wish he told us 120 parameters ago... 🤣

@Christoph-Hart is the Notch filter display (in Scriptode) a fiddly fix?

@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:

Link Preview Image pizmidi/pizjuce at main · sleiner/pizmidi

A collection of helpful tools when working with MIDI - pizmidi/pizjuce at main · sleiner/pizmidi

favicon

GitHub (github.com)

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! 🙏