@scottmire Vibe coding SNEX is very possible. Some recommendations;

1. Create a Claude skill. There are some common pitfalls that you will run into because Snex is a C++ like language. So get familiar with the skill creator and start by giving it the empty template of a snex node + documentation (and forum!) link + keep in mind that the misnaming between node title in de code and the node title in the network is a common tripwire with a not so logical error naming. Also tell it to keep previous versions of the DSP and make a new artifact any time (so you can rollback). Update the skill anytime you work out more pitfalls in SNEX handling DSP.

2. Ideate first. Keep the modules as small as you can keep them and keep in mind that SNEX nodes dont accept 16+ parameters. Also you can use less sophisticated but still smart models. I use Opus mainly. Tell it to research DSP and become familiar with DSP research papers. Use AI as a sparring partner in this phase. The more specific the sparring the better (ie. dont try to prompt 'Create a buchla for me' but rather 'Do some deep research on what makes the buchla sound unique, dive into the circuitry as well as the synthesis'.) Tell it to make a sophisticated prompt, referencing any DSP it needs, for the smarter model. You dont want to use this sparring conversation to escalate to DSP work!!! Because that will exponentionally increase token size with all kind of context from the research phase.

3. Use complex and high reasoning newer models like Fable or Astra for the DSP building phase. Especcialy Claude is quite adept in DSP work and will actually run python scripts in its background to check it's own DSP math. You dont have to grasp all math, but basic DSP knowledge is recommended. Also use all kind of scopes that Hise offers, to look for weird phasing. The newer models are actually really great in DSP work. Just costly.

4. Debug again using the smaller models Sonet and as an escalation use Opus. But Sonet will be fine for looking up syntax errors or doing a quick forum check to see if someone came across the same error.

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.

@Jeetender yeah the stock one works just fine.

@Orvillain I ran into a similar issue with snex nodes and Hise defaulting to 10.11 and the compiler wanting to do 10.13+. Both are at the DSP networks compiler end.

I've got a feeling it's more Xcode related and dropping support for the 10.x range slowly.

Claude told me this but won't be able to test it till.tomorrow. Let me know if it helps.

---

Got it. So the flow would be:
Export/compile the DspNetwork DLL from HISE on Mac
The AutogeneratedProject.jucer gets regenerated with 10.11
Xcode refuses to build it
The fix is to patch the .pbxproj after Projucer has re-saved it but before Xcode compiles. The easiest place to hook this in is your batchCompileOSX.sh script in DspNetworks/Binaries/ — add the sed line right after the Projucer re-save step.
Open that file and it'll look something like:
Bash

cd "$(dirname "$0")"
"$HISE_PATH/tools/Projucer/Projucer" --resave AutogeneratedProject.jucer
xcodebuild ...

Add the patch between the resave and the xcodebuild call:
Bash

sed -i '' 's/MACOSX_DEPLOYMENT_TARGET = 10.11;/MACOSX_DEPLOYMENT_TARGET = 10.13;/g' \
  "Builds/MacOSX/$(ls Builds/MacOSX/ | grep .xcodeproj)/project.pbxproj"

That way it survives re-exports automatically without touching HISE source. Want me to look at your actual batchCompileOSX.sh if you paste it here?

Might be because there have been major build changes. Maybe try an older version?

https://forum.hise.audio/topic/14647/latest-develop-won-t-build-in-vs2022/12

@dannytaurus I would like to add that you can also connect Claude with MCP to the Hise.exe, it can do a lot already and finds its way on its own through documentation, makes edits in the code, compiles for you, recompiles if it runs into errors etc.

Used it a lot with Opus 4.6 but as many people reported the model got dumbed down a bit and runs through usage like an addict runs through colombian snow. They did double rates in off hours last month. So I basically went from hitting the limit 30 minutes before rate refresh, to 30 minutes after rate refresh I think the openclaw community really fckd it up for us sadly.

Claude did a LOT of heavy lifting for my UI phase when developing. SNEX support was missing but I thought I think I saw some commits yesterday that integrate that part as well.

So yeah. Claude is the bomb and MCP makes it even better (especcialy for a novice coder like myself).

(Edit: Just noticed this is a topic from before the MCP )

@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

@pratitghosh when you say DAW with a mixer, a
I'm thrown back into time to Sonic Syndicate Orion Pro. First DAW that I used

@pcs800 said in Error when compiling vst3:

include_hi_scripting_01.obj : fatal error LNK1000: Internal error during BuildLibrary.EmitMember [H:\Common\HISE Projec
ts\Whineykid\Binaries\Builds\VisualStudio2022\WhinyKid Wah Pedal_SharedCode.vcxproj]
Press any key to continue . . .

ChatGPT pro seems to be convinced that its a storage issue. Are you running this from a network drive perhaps?

@David-Healey

If you want to use Juce8 what I do is I build Hise on Juce6, export the plugin, change Juce modules with a simple batch file and recompile with the batch file that Hise created. Then change back.

Def not ideal, but it's a working workflow when you need Juce8.

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