@Mors Update: I used a faust delay instead of hise template feedback delay, works like a charm!

@pratitghosh you can just use bypass nodes for each model. And these modes will be connected to a xfader node, so it will switch between models

Edit: 100 models are pretty huge, maybe multiple xfader nodes, each one will switch 8 models

@ccbl Thanks for the tip. So like @David-Healey says, it is impossible to convert files each other.

@Christoph-Hart yeah, here's what I could come up with!

The model occasionally thought you could add child panels directly to viewports. It didn't properly cast/convert the raw result of vpt.get("scrollBarThickness") for calculations. It hallucinated a scroll event listener/callback for viewports. I needed to prompt it specifically to use a 30Hz timer loop for position updates instead. It had the most trouble with local, reg, and const. Especially in long generations with multi level functions, it tried standard JS var/let scoping, leading to long runs of compilation errors. I mainly used Google's Gemini 3.1 Pro via Antigravity, but I also tested Claude Opus/Sonnet 4.6. The Anthropic models had a couple fewer issues, making sense if the MCP server is currently tailored to their behavior.

I had checked out the viewport's multicolumn mode. I built this as a ScriptPanel recycler to have high LAF control over individual buttons and icons for a custom preset browser. I wouldn't be able to get the same component styling flexibility with multicolumn mode.

I'll try out the LSP server! I've been following HISE's ai journey and can't wait to see what's next! Being a dev who uses AI to assist in most my work nowadays, it'll make HISE development much much faster and accessible lol. Love the forum, but I dream for the days where I'll ask Claude to explain why my function call is wrong and @David-Healey can enjoy his vacation instead! 😁

The MCP server in antigravity is amazing, but there's a couple things HISE struggles with against AI.

Absolute positioning is a bottleneck. Is there anyway to expose JUCE's FlexBox/Grid to hisescript? It would be life changing. If the model can just write relative values, it wouldn't have to guess pixel coordinates anymore. Can't wait for scriptnode to work with MCP. Having models build scriptnode networks from text/json, or piggybacking faust, will make that rodeo a lot simpler.

I can envision HISE's future as a sidecar rendering engine alongside your everyday IDE, which wil be where the actual code writing/editing and prompting happens. Having HISE run in a headless like manner to compile the plugin, fix errors, and run tests would have massive potential. The LSP and MCP server are great starts for this.

@Bart FYI I'm working on a TUI app at the moment that allows you to remote control HISE and perform all kinds of actions - the same command set is also exposed as an CLI interface for the LLM to use (and you can use the TUI app as a "log viewer" to trace back what the LLM did).

This will include a feature complete builder mode with full undo support where you can add / remove modules and change parameters from the command line:

https://github.com/christoph-hart/hise-cli/issues/5

@iamlamprey I've already tried this, the project freezes while loading.

@dezertaudio said in Custom JSON preset file support:

I'm using a custom preset browser though.

Are you using a custom preset format as well?

@David-Healey stash, fetch/pull, then restore stash should do, no?

@Solocky You might be interested in the C++ API https://docs.hise.dev/cpp_api/index.html

@Sifres For Faust I had the same issue recently. Is your Faust node in a frameProcessing container by any "non-chance"?
That was my case so I've made a PR to fix it (in fact I made it then it was removed because I was fiddling around because I was trying stupid thing with git because I'm an idiot because... Well, I just re-pushed it)
The export wasn't processing the signal as frame, only as blocks...

@David-Healey Ah yeah! I've seen the projucer being replaced at some point during my crappy manipulations! Checking this, thanks Dave!

@young60 how did you connect the LFO to the macro, and how did you link the dummy slider to the filmstrip knob?
Can you provide a snippet?

It turns out it was a frame processing issue in the wrapper.
Fixed by PR https://github.com/christophhart/HISE/pull/928

@David-Healey Oh awesome, thanks for letting me know!

Here is a video where you can see better the visual details:
Fully customized pseudo backlit interface via LAF