@dannytaurus I used moonbase for my licensing and store setup. As a new developer I looked into Hise licensing and MoR around the same time. Moonbase tackles both, is easier to setup then alternatives and requires no synchronisation.

From there I simply tried to implement (Moonbase requires Juce8) and nearly got it. However I ran into a bug. Moonbase response was instantaneous and very helpful. In the end David stepped up and the issue was resolved within a day or two with the Moonbase developer being responsive as well.

Even though I didnt have much alternatives I really like the philosophy of having an integrated system. I met Tobias in Amsterdam and like his view on things and what he tries to accomplish. For instance the mailing integrations have seperate groups from the get go, allowing for trial reminders. Also the system has good API integrations and is very well documented. So right now, for a press release, I wanted to make a bunch of NFR codes. Took about 3 prompts for Claude to figure out the API call with the docs and created a big list. Would have taken hours tbh.

Only thing missing is an MCP

If you want to take a look at the total integration take a look at;
Https://dropout-audio.com/
Hit me up if you want an NFR license so you can see the entire flow.

Appreciate the hard work and this should be usefull for the sample bank guys, because of the interface direct expansion shopping. You do have some competition in what is already a pretty limited space (HISE development) with Moonbase (which, at the moment requires some source hacking), Chrisophs own licensing server and Inlay. Then you also have a bunch of devs who are already on their own licensing system. Just wanted to put it out there so you dont get bummed by limited interest.

Your work does look pretty thorough though. Are you also a MoR on the storefront side?

Is the preview able to be accessed yet?

What would be nice is if the slider could also function/double as a led based VU meter.

I know its a provocative title but made you look

Ok so let me start by saying Ive been on Hise for the last one and a half month developing and having a great time. The interface / logistics take some time to get used to, but getting the hang off where what and when. Its a really nice lowcode solution and I thorougly enjoy development. The MCP server is really nice to work with as well and really adds to Claude's knowledge which speeds up everything.

BUT

I've seen and worked around a LOT of bugs in the development of my first plugin and am kind of doubting if a commercial license and release is worth it. Let me sum them up. This is building on Windows.

- Faust: There is a bug in the Faust handling and it would stop working after export to VST.
WORKAROUND: Made a very simple Script FX containing only the Faust node, and made sure names werent duplicate.
- Feedback / delay loop from template. Clicking in the menu to compile to DLL would crash Hise. After a lot of excluding, the feedback loop (from template!) is the culprit.
WORKAROUND: I cant compile the entire network to DLL, but this isnt needed. This DOES force me to compile SNEX nodes seperately and excludes the waveshaper (because apparently this needs a compiled state). Also it's bad for performance.
- GlobalMod LFO. I used a custom Script LFO one. Again on exporting, this would stop working.
WORKAROUND; After a lot of puzzling the answer was to precompile the node in a minimal scriptnode, instead of a Hardcoded modulator, and wire up again. This however made the raw signal unusable for the LFO led on my frontend.
- Any kind of analyser crashes HISE. For some reason when I click on the analyser tab when I want to add an analyser node, it crashes. I know it preloads existing nodes as well, so might have been me FAFOing but its not pretty
WORKAROUND: The LFO signal couldnt be picked up by an analyser, but the Globalmod receiver did have a displaybuffer. Used that instead. Was harder to set up, because this was in the path of the Cutoff, and not the Pitch (which was wired into the Waveform generator).

So basically I feel like there is some technical debt bugwise. I would like to contribute and file these as proper bugs on github. Hell I'll even wire up Claude to make some code proposals if it helps. What would be a good way to do this? Where do crash logs go?

Is there any chance on a hardening development round, now that we have had some cool stuff on the AI side?

@Christoph-Hart

Really nice work man! Gonna play around with it. Its already mouthing me off on button placement

Came across this on the KVR developer forum. Seems interesting and better then other filmstrip generators (Canva and some other tools). Acool feature is you can load a API key for Claude and others, to generate knobs, that you can then work with to generate the filmstrip / sliders etc.

https://github.com/Vybecode-LTD/stripkit

In no way affiliated, but thought it usefull for this crowd

Could it be that your 1.0.6 has no more working arpeggiator? Couldnt get it to work.

KVR crowd seemed a bit annoyed that you dissed the TAL version though, good that you changed it.

@HISEnberg So Moonbase JUCE module requires JUCE8 indeed. Hise isnt stable when being compiled, or when compiling plugins, on JUCE8. So yeah its not working atm. Christoph noted that this is because he did some funky stuff for the MCP integration.

BUT you can work around that by compiling hise on JUCE6, then exporting a plugin. It will fail but it will create a .jucer file and you can pick that up with JUCE8. At least thats my workflow. You could probably script the whole thing. It requires some other steps as well as modifying some Hise source.

TBH if you dont need it right now (as stated, for me it was a neccesary step) I would simply wait for Christoph to integrate it.

@Christoph-Hart great! I feel like it could really benefit the eco system surrounding Hise.

@Morphoice Sick dude. Well done! Loving the sound and glad you kept that interface clean. I'll trade you a code for my synth if you are interested

Anybody who has tried to set this up? Want to give it a go next week, and wanted to check if there are any pitfalls you guys ran into?

By give it a go I mean Hise + Juce8 and Moonbase as a license module.

I did it with Claude in two days. Most of the time was actuallly spend on a bug in the Juce module though, that david helped to fix. In the end I have 3 files in the Hise Source that needed changing.

Its not a gracious proces though.

I need to export first so it creates the batch file and set all files up from hise but it will choke on the Juce module missing. Then switch to Juce 8 (trivial, I have a script to switch easily), add the module / flag in Juce and start the batch file again.

There is some other stuff to set up like an encoded file so the connection can be set up secure and some settings on the Hise side need to be hooked up if you want the screen to dim and audio to block, but you do this once per product in Moonbase.

Honestly it works for me, but looking forward to supported integration. Moonbase is a great platform.

Is the preview able to be accessed yet?

What would be nice is if the slider could also function/double as a led based VU meter.

Appreciate the hard work and this should be usefull for the sample bank guys, because of the interface direct expansion shopping. You do have some competition in what is already a pretty limited space (HISE development) with Moonbase (which, at the moment requires some source hacking), Chrisophs own licensing server and Inlay. Then you also have a bunch of devs who are already on their own licensing system. Just wanted to put it out there so you dont get bummed by limited interest.

Your work does look pretty thorough though. Are you also a MoR on the storefront side?

@Chazrox I would opt for something similar to the knob -> Use an image as the slider head

Came across this on the KVR developer forum. Seems interesting and better then other filmstrip generators (Canva and some other tools). Acool feature is you can load a API key for Claude and others, to generate knobs, that you can then work with to generate the filmstrip / sliders etc.

https://github.com/Vybecode-LTD/stripkit

In no way affiliated, but thought it usefull for this crowd

@griffinboy not all heroes wear capes. These are very usefull, thanks!

Could it be that your 1.0.6 has no more working arpeggiator? Couldnt get it to work.

KVR crowd seemed a bit annoyed that you dissed the TAL version though, good that you changed it.

@HISEnberg So Moonbase JUCE module requires JUCE8 indeed. Hise isnt stable when being compiled, or when compiling plugins, on JUCE8. So yeah its not working atm. Christoph noted that this is because he did some funky stuff for the MCP integration.

BUT you can work around that by compiling hise on JUCE6, then exporting a plugin. It will fail but it will create a .jucer file and you can pick that up with JUCE8. At least thats my workflow. You could probably script the whole thing. It requires some other steps as well as modifying some Hise source.

TBH if you dont need it right now (as stated, for me it was a neccesary step) I would simply wait for Christoph to integrate it.

@Christoph-Hart great! I feel like it could really benefit the eco system surrounding Hise.

@dannytaurus I used moonbase for my licensing and store setup. As a new developer I looked into Hise licensing and MoR around the same time. Moonbase tackles both, is easier to setup then alternatives and requires no synchronisation.

From there I simply tried to implement (Moonbase requires Juce8) and nearly got it. However I ran into a bug. Moonbase response was instantaneous and very helpful. In the end David stepped up and the issue was resolved within a day or two with the Moonbase developer being responsive as well.

Even though I didnt have much alternatives I really like the philosophy of having an integrated system. I met Tobias in Amsterdam and like his view on things and what he tries to accomplish. For instance the mailing integrations have seperate groups from the get go, allowing for trial reminders. Also the system has good API integrations and is very well documented. So right now, for a press release, I wanted to make a bunch of NFR codes. Took about 3 prompts for Claude to figure out the API call with the docs and created a big list. Would have taken hours tbh.

Only thing missing is an MCP

If you want to take a look at the total integration take a look at;
Https://dropout-audio.com/
Hit me up if you want an NFR license so you can see the entire flow.

Its been there a while I guess. It didnt work for me in my en of februay / march build.