@pcs800 Looks like it is integrated into the HISE source code (included with the JUCE modules), but you would need to add you own API for this to communicate in HISE script, or edit the HISE source code to contain a version of the script you provided:

https://github.com/christophhart/HISE/blob/01b810a9d31f032b30537b4767082732cd96f46e/JUCE/modules/juce_audio_processors/utilities/juce_PluginHostType.h#L38

https://github.com/christophhart/HISE/blob/01b810a9d31f032b30537b4767082732cd96f46e/JUCE/modules/juce_audio_processors/utilities/juce_PluginHostType.cpp#L4

@d-healey i will try that, thank you!

@elemen8t I just did this myself trying to mimic the RC-20's Intensity knob. What I ended up doing was putting each of my scriptNodeFX's inside of another wet/dry node, then when you have that done, script one slider/knob on your UI to adjust all 'GlobalMix' knobs together. So if you have a scriptnodeFX with a wet/dry setup already, put the whole thing inside of another one and let that be your 'GlobalMix' parameter. I hope I explained that well enough.

Heres a working example.
Screenshot 2025-10-04 at 11.24.40 PM.png

Screenshot 2025-10-04 at 11.24.46 PM.png

Best way? idk but it works.

Screenshot 2025-10-04 at 11.32.17 PM.png

@trillbilly @Yarost

yes i tried different things and it still crackles

i ended up using the pitch shifter in faust

it sounds a little different but it works fine without any crackles

@d-healey ah, yes thanks

laf.registerFunction("drawFilterGridLines", function(g, obj) { });

gotcha thank you all

@HISEnberg we have MIDI scripts but you are able to bypass them (glide and pitch envelope)

Good to know that there is no issue on your end.

A single wavegen work fine.

I will remove more and more from my project to see what causes this.

Strange is that is only on one OS in one DAW.

@HISEnberg Okay I see my error now. I was loading the audio files from the Audio Files folder (using the File System API) and not the Pool which explains why it works in HISE but not in the compiled plugin.

So for anyone else who comes here the answer looks something like this:

const var audioFileList = Engine.loadAudioFilesIntoPool(); // get the audio files from the pool const var AudioReference = Synth.getAudioSampleProcessor("AudioReference"); const var cmb_MatchLoader = Content.getComponent("cmb_MatchLoader"); cmb_MatchLoader.set("items", ""); for (file in audioFileList) { var displayName = file.replace("{PROJECT_FOLDER}", "").replace(".wav", ""); cmb_MatchLoader.addItem(displayName); } inline function oncmb_MatchLoaderControl(component, value) { if (value > 0) { AudioReference.setFile(audioFileList[value - 1]); } } cmb_MatchLoader.setControlCallback(oncmb_MatchLoaderControl);

@pcs800 Pretty similar issue. You are calling the repaint incorrectly here:

inline function onKnob1Control(component, value) { currentTempoIndex = value; Panel1.repaint(); } Knob1.setControlCallback(onKnob1Control);

So now you need to change Panel1 to displayPanel1 here and call the repaint on the control callback. This also means you will no longer need the timer on this panel since it will be your knob that is updating the panel, so you can remove this:

displayPanel1.setTimerCallback(function() { this.repaint(); }); displayPanel1.startTimer(50);

However there is one other thing important to understand. If you want to assign a knob callback with script, than you cannot use the property editor to assign the control anymore (the property editor is going to overwrite anything you are doing in the script).

So if you want the knob to control the delay time still you are going to need to do that in the inline function:

inline function onKnob1Control(component, value) { currentTempoIndex = value; displayPanel1.repaint(); // Fixed // Assign to the Delay knob } Knob1.setControlCallback(onKnob1Control);

I think @d-healey ''s video here covers this but maybe there is another one I don't know about:

https://www.youtube.com/watch?v=1rs0w4MDNA0

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

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