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

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.

@Lindon

Thanks for the response, good to hear your road is less rocky and commercial useage is working out!

The globalmod and faust module bugs have similar issues reported on the forum. The feedback loop has been confirmed as a bug on Windows by David in the latest release.

Defenitely wouldnt rule out a configuration issue, would still like to know how to trace that without having to reinstall my entire system.

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?

@dannytaurus Thanks for suggesting and sounded pretty promissing tbh. However after manually changing the code for this, recompiling hise -> Export plugin, it still fails silently.

Very frustrating tbh.

So I have a global modulator that uses SNEX. This works fine in Hise itself and I have it wired up to a global mod container inside a DSP network (and also have it hooked to pitch of a waveform generator).

After export the LFO / Global modulator disconnects. It's just doing nothing.

I tried some stuff I found on the forum and on github, like seeing if the matrixTargetId was filled in and checked if NUM_HARDCODED_FX_MODS=1

Anybody have an idea what to research next, anybody ran into the same?

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.

@Christoph-Hart

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

@jeffd Yeah I would like to know that as well tbh. Was it hard to get it working?

@NISHI_MUSIC Yes you need licenses.

JUCE if you plan to sell commercially and make more then 20k
https://juce.com/get-juce/

HISE if you are not releasing open source. Commercial or not. If you are publishing source under GPL, you do not need a license.
https://hise.dev/#license

Ok so a couple of things;

• when you sell you need to cover sales tax. This is hard to set up on your own so the fastest way is to find a MoR (merchant of record) to handle the sales tax. Gumroad is pretty cool and is a MoR nowadays. It's also a good place to look for and find more then experimental plugins. So signing up there is a no regret for you. Unless you want to skip taxes and just do a couple of sales, in that case setting up a small website yourself is the way to go and just do some kind of PayPal transaction
• Licenses. Keep in mind that Juce requires a license when business exceeds 20k and Hise requires a license if you don't release open source
• copy protection / license activation. 2 good options are Hise activate or moonbase. The latter is also a MoR but it's still difficult to set up under the current Juice version. It will take some work integrating either.
• installers: I think this is a bit of a hassle with code signing. David is preparing a course on this I think.

Mind you this is just my research from the last couple of weeks. I didn't go to market yet. So I might be missing some stuff or getting it wrong.

Btw for your more experimental plugins, probably the best way is indeed gumroad, and maybe just skip copy protection. Consider publishing open source as well. Unless you want to start a big ad campaign, publish on Plugin Alliance and take a more commercial approach.

Good luck!

@PV3679 I solved it on my end by doing 2 steps.

1. Renaming the Faust modules parameters to something less generic (So FXslot1_Cutoff instead of simply 'cutoff'. It is my understanding that Faust modules dont like names that are re-used.
2. I compiled ONLY the Faust module (so got rid of other stuff and compiled).

After that the knobs of the Faust module were working