@scottmire It's not possible with JUCE6 but should be with JUCE8, I don't know what would be required on the HISE side though.

Coming right on time (well, when ready...) as I am to release a set of plugins based on the same engine so if fixes and updates can be done just once for the bundle I can already see the benefit of this!

@Orvillain said in Using custom preset system - as in the actual presets themselves, not a browser:

Why do you want to do this?

Because it kills voices and I want to silently update some metadata like tags and author for presets.

But.... your method seems to be working!!! I feel like I'm going to have to remove certain characters in case it messes up the preset code....

I also saw this one: https://github.com/Noizefield/audio-plugin-coder

@Lindon Thanks for the link!

That explains why I was getting the 'Unknown Function' error—I was trying to call it on the Synth object instead of a ScriptPanel.

I’ve set up a hidden panel to handle the callback now, and it’s working perfectly. Appreciate the clarification!"

@David-Healey said in Moonbase:

if you then reexport from HISE the juicer file will be recreated and your changes overwritten, that's probably the issue you were running into

yes i believe this was the issue.
but im also wondering if i somehow screwed up changing over from 6 to 8.

@veryveryhaps The Audio Loop Player responds to MIDI like any other sound generator.

If you only want to trigger it from the UI try playNoteFromUI. It's meant for triggering sound generators from UI elements. It simulates pressing a key on the virtual keyboard.

There's also the cunningly-slightly-differently-named noteOffFromUI to stop playback.

As for pausing playback and continuing from the same point, I'm not sure.

const var loopNote = 60; const var channel = 1; inline function onPlayButton(component, value) { if (value) // button ON Synth.playNoteFromUI(channel, loopNote, 127); else // button OFF Synth.noteOffFromUI(channel, loopNote); } Content.getComponent("Button1").setControlCallback(onPlayButton);

@Oli-Ullmann Yes, I do exactly like that

@Anhuarcin It could be possible that there are code paths generated for runtime dispatch, so that if the CPU detection shows AVX support, then it will branch to use that - I can imagine that IPP does stuff like that to squeeze out performance.

@JulesV My solution is to use a flag. If the plugin is being initialized, load a specific preset that has my settings. if the plugin isn't being initialized, it doesn't do anything special.

@sletz Another Faust + MCP project by Yann Orlarey: https://github.com/orlarey/faustforge

@Daanyoo I just tried to reproduce it on a empty project on WIN, it worked there and all of the sudden it worked in the regular project as well... I am so confused haha

But at least its fixed, thank you guys for your help!!

@David-Healey & @dannytaurus thank you guys. I'll update.

@David-Healey Ah that video flew under my radar!

Indeed I do have the same issue, same with the examples in the HISE docs. I've mainly gotten around this just sticking to the old school method of reg variables. I haven't seen many HISE scripts using Lambdas.

Something must be off with my HISE setup in XCode so I'll dig around a bit.

@HISEnberg

Indeed!
I've also got someone after this. But judging from the lack of movement on this, my guess is that it's troublesome to implement

@dannytaurus @Oli-Ullmann @ustk thank you all for the help, all your suggestions work great!

@ustk yeah ill just hide it.

I was gonna have it as part of the interface for the user to see cpu and ram usage, but its not really necessary.

@dannytaurus Oh cool! Bug or not I can at least make my project to work so thanks!

@Bart Wow, that interface is wild! 😮 😂

The synth I'm building is the start of a series, so I'm designing a layout that will work with all of them. Each one will have a couple of unique controls, so they all look slightly different but obviously from the same family.