@ulrik I need to access it with a slider.
c5fd98de-afcc-4763-a243-7043d46ff34b-image.png

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

..oh and the customer wants to have a left and right panel that remains across all "instruments/expansions" is that possible with full Instrument Expansion?

Yes - I opened some PRs recently with a bunch of expansion additions for the preset browser that might be useful to you, including a built in installer/uninstaller. None of them have been merged yet so things might change.

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

can you point me at any documentation about how to get this done?

Make your base project (this is your player). Add some method to it for installing expansions and loading expansions. I have a video about building an installer, and loading them could be as simple as adding a preset browser. In project preferences set expansion type to Full, add an encryption key - this key will be used by all expansions you create. Export this project as a plugin/standalone app, this gets sent to the end user.

To create an expansion make a new HISE project. Leave the expansion type set to disabled, add the same encryption key as your base project. Once you're happy with the project export it as a Full Instrument expansion, this will create an info.hxi file. Then export your samples as a hr1 archive and in the exporter window you can select the info.hxi file.

You ship the hr1 (hr2, hr3, etc.) file to the end user and they install it in the base project.

https://docs.hise.audio/working-with-hise/project-management/expansions/index.html#features

@ericknido You should compile HISE from the newest develop version, the standalone release version is outdated and bugged. Also check my previous posts about the Filter bug fixes, you have to use github to do it right

@jadg It's normal if you didn't enable MIDI learn for those components...

@David-Healey I've worked around the issue by deleting the Strength knob, assigning the macro, then re-adding the deleted knob

@resonant thanks! The system is running in GCP right now.

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

@resonant absolutely:

function(sampleRate, blockSize)
blockSize = buffer size

@HISEnberg Yeah, I built it without checking this box and effect was silent, now I checked it and compiling. The "Signal Input" plays a very short loop and follows the audio, it's a very nice way to build effects.

Edit:
It worked! One knob has harder tickles, other one is warmer with some high cut. I'm impressed by the effect.

@pratitghosh said in NAM Model switching logic:

Do you have any information on those?

then I could follow with a new "NeuralNetwork.loadTensorFlowModel( var modelJSON)" function call. It obviously doesn't work this way.....but it would be amazing if it could....just sayin...lol.

I don't know how you could use the timer with a network

TheAudioProgrammer and @tobbentm did a live stream yesterday

https://www.youtube.com/watch?v=wQGq4KT55qk

@Quemis Enable isPluginParameter in the property editor for the controls

d7f14fe3-1294-4fb1-82dd-6a3016fb6e94-image.png

@Mors Is it possible to have a faust sync reverse delay?

Here is a reverse delay but not in sync: https://forum.hise.audio/topic/11445/free-reverse-delay-built-in-rnbo/11?_=1774466149983

@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