administrators group

Christoph Hart

@Lindon you cannot add executable hise script in standard expansions - these are limited to static resources only.

you have two options:

implement all logic that is required by all expansions in the base project, then just hook into it. the additional data can store JSON - this would be the config setting for which expansion needs which logic.
If that isn't enough flexibility you can always use the Full Instrument Expansion route - this is basically what Rhapsody is doing. You get a completely dynamic module tree / script interface, basically Kontakt Player tailored for Lindon and every expansion is a complete HISE project.

Christoph Hart

@David-Healey ah yes I‘ve hacked around in the juce code to allow artificial mouse clicks to give the robot the ability to use the plugin interface but I haven‘t ported this to JUCE8 yet.

Christoph Hart

@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

Christoph Hart

@Casmat nice. if you want you can post the hallucination bugs and I'll add them to the MCP servers in the DONT section - that's an iterative process but since I'm working mainly with the Claude models it might be overfitting to their behaviour.

I'm also inclined to change the scripting language to support more "JS-type" constructs granted that it doesn't affect backwards compatibility and is within the scope of HiseScript - that's the gold standard of removing friction points, a DONT section in the unified style guide is a band-aid.

But the first line of defense against hallucinations should be the LSP server - this is another binary that is integrated with your coding agent and is executed after every file edit. This doesn't recompile HISE (and you have to disable the "recompile on file load" function in HISE for this to work), but it "shadow parses" the edited file and returns a multi-error diagnostic log with all syntax errors or hallucinated methods. It doesn't do real runtime inspection, but it catches missing API methods as well as a few custom diagnostics.

RE: your initial feature request. Have you checked using the Viewport's multicolumn mode for preset browsers? this should be vastly more efficient and is suitable for displaying hundreds of preset items without performance issues. ScriptPanels are too heavyweight to be used for a single row in high numbers.

Christoph Hart

@boim98208 the circles are only hidden if you enable the complex group editor as they don‘t make sense anymore when it‘s enabled. If you don‘t use the complex groups then it should still be there.

Christoph Hart

@Orvillain yup viewport should consume the mousewheel events of a child component.

Christoph Hart

@Orvillain yes they were relicts of long before the set call and I just forgot they exist until the AI tried to use it and messed up the magic numbers. There‘s no need for it - they just route to the set call but without a self-contained explanation.

The content.setColour call sets the background color of the interface and can easily be replaced with a panel if a plan colour background is what you want.
Are you using these methods?

Christoph Hart

Nobody is expecting that AI will produce interesting plugins on its own - the same as it will never produce interesting music with any artistic value ever.

It‘s the middle layer that handles the transformation from a human having an idea and vision to a plugin that is completely being revolutionized at the moment - this is where HISE sits and ignoring this paradigm shift would be suicidal for a framework like HISE which is why I‘m pulling 14 hour days since about 3-4 weeks to figure out the best way going forward. The way Opus 4.6 interacts with the current toolset I‘m developing is uncanny though and goes far beyomd simple LAF stuff - it eg. oneshotted the transformation of a fairly complex user preset model to the custom automation handler then Ralphed it‘s way to find out that setting processorIds will make the control callback not fire - with proper guidance and planning, which ties back to daves distinction between vibecoding and AI assisted development.

Christoph Hart

But how and why did we get to the point of writing code using AI

Simple: the latest iterations of the SOTA models make AI coding on par with a reasonably well skilled developer.

Christoph Hart

@David-Healey that should be covered by that wildcard function, any file that matches against that wildcard would be excluded from the deinstallation procedure (and before installing it checks if it exists, then does nothing). A big XML file would be a bit tricky though - you can never change that template file because it would never be updated - with script files you can branch out your config stuff into a seperate smaller file.

administrators

Posts

Member List