Is the HISE REST server ready for use?

[Christoph Hart]

It's not intended to be used directly as REST API but the hise-cli app will talk to it and Claude should use the hise-cli app as this is more token efficient than dumping the entire HTTP response into the context window.

It's not 100% finished, but the basics should work. What's buggy?

[dannytaurus]

@Christoph-Hart said in Is the HISE REST server ready for use?:

It's not intended to be used directly as REST API but the hise-cli app will talk to it and Claude should use the hise-cli app as this is more token efficient than dumping the entire HTTP response into the context window.

Makes sense. Using it through the CLI now

Using REST directly was having things like the /repl endpoint not recompiling the scripts, and some values getting out of sync during saves.

But the CLI between seems much better now. Thanks!

[ustk]

I was doing the same through the REST API, but without having bugs though...
I switched to the CLI as well

[David Healey]

@ustk @dannytaurus What do you use it for?

[ustk]

@David-Healey

• For annoying and long tasks on the UI for instance. I've just made a re-ordering panel that is nice and smooth.
• For helping me to improve DSP too, and to catch issues I haven't anticipated.
• Sketch new designs quickly
• ...

[dannytaurus]

@David-Healey Honestly, pretty much everything in HISE now.

Not UI design, Claude is still pretty bad at that. But all the other stuff inside HISE.

I've been using Claude with HISE for weeks now, but only giving it the project repo and the HISE source. Not giving it access to a running HISE instance.

But in the last few days I tried the REST server, and now today, after Christoph's comment, using the hise-cli has made it much more reliable and easier for Claude to make changes.

Yesterday I asked it to implement a Growl control for the filter. A simple resonance control wasn't cutting it for this synth, so I asked it to add a narrow bandpass filter that tracked the existing LPF, with some variable tanh distortion. It changed the UI control from Res to Growl, added a ScriptNode effect with a dry/wet chain, filter and saturation nodes, so that the Growl knob would mix in the BP filter in parallel as the knob turned. It tidied up all the old res code too.

Today I had it convert a few old AHDSR modules into FlexAHDSR so I have more control, and rewire one UI envelope component to control the amp, pitch and filter envelopes, all with different ranges. Easy peasy for Claude, and even easier through the CLI.

I've even had it make a bunch of presets for me, based on the style of the synth, the controls UI and a few existing presets I made myself. Claude's presets weren't amazing but they were all valid - meaning no 'silent' or 'just noise' ones that you can get with pure randomisation. And they're all a great starting point for me to tweak and turn into valuable presets.

[dannytaurus]

@ustk I don't even know if those things I described were an issue with the REST server or with Claude not using it properly.

Either way, using the CLI has made it MUCH easier.

[dannytaurus]

@David-Healey Actually, Claud did make a couple of cool design suggestions yesterday. I didn't end up using them because the feature itself wasn't good, but the UI ideas were OK.

I just wouldn't have it design a UI from scratch, not right now.

[ustk]

@dannytaurus Yeah for all those DSP stuff and for creating presets as well.

The panel transition was existing way before I used Claude but I was lacking the reordering menu, they were just simple buttons.

[dannytaurus]

@ustk Nice!