@David-Healey said in Agentic coding workflows:

Does it not save it for you to view in the web version?

Oh, I don't know. I've only used the terminal version. Makes sense that there would be a web backup off chats though. I don't really get how it works, coding with AI on the web. I guess you just link it to a GitHub repo and then view the diffs in the web app? Feels a bit detached to me. But I am slowly spending less and less time in the actual files, and more time reading diffs.

How do the Codex models compare to Sonnet (that's the main one I'm using)? And does it have usage limits like Claude (resets every 5 hours/week)?

I found GPT-5.4 to be on par with using Opus 4.6 in Cursor. Mind you, I often switch to Sonnet in Cursor because I don't feel like there's a huge difference for what I do. And Opus costs 5X Sonnet, so that's good.

Does not compute... you mean you don't start by outlining your namespaces before writing your script

Not at all. I still haven't got my head around when and why to use namespaces. Maybe I haven't made a plugin complicated enough to really benefit from them. But that's what's cool about AI. I can code up ad-hoc from scratch then have the model tidy it up for me. Of course, that would be much more reliable if we had unit tests for everything

@David-Healey It will probably be useful for refactoring and moving things into namespaces. I'm on a short HISE-atus (see what I did there) at the moment but I'm gagging to get back into it now we have the MCP stuff set up.

The future is leaning back in my chair with a cup of tea casually throwing out commands like "now add an effects section on the right with a Juno-style chorus and an authentic BBD-style delay, and wire them both up to XY pads with, I don't know, you choose the parameters."

@Lindon It'll be a continually evolving world for quite a while I think.

You might know all this already but...

There are 2 main choices to make - the coding environment and the AI model that you use within that coding environment.

My preferred coding environment was always an IDE like VSCode, so Cursor, which is a VSCode port, was my obvious first step into this. But lately I've been trying the terminal-based Claude Code, where you don't get tabs with open files or a directory tree, etc. You just get chats and code diffs in one continual terminal window.

If you prefer and IDE try Cursor or Zed (David mentioned it, looks good). The advantage of Cursor is that it comes with the Claude model "built-in", so you don't have to set up API keys etc to get going. Another Cursor bonus is that it seems to absorb some of the AI model cost from your usage. Not sure how that will pan out in time. They can't keep doing that.

Another benefit of using an IDE over a terminal-based approach is that the IDEs keep a chat history of all your work. Meaning in Cursor, I can go back to any historical chat and just keep working on that same task without having to relearn all the context. As far as I know, terminal-based approaches like Claude Code can't do that. When you finish the task and close the terminal tab/window, all the history is gone. You're just left with the resulting code. Personally, I go back and carry on work in previous chats all the time, so I need an environment that allows this.

For the AI models, it sounds like Christoph is pretty set on Claude Opus 4.6 (an Anthropic model) but I've had decent results with the faster and cheaper (meaning not as thorough) Claude Sonnet 4.6 (also Anthropic). I also just had a couple of good Ruby coding sessions with GPT-5.4 (an OpenAI model) so that's another option.

The models are advancing all the time and some models are better for some tasks than others. But unless you want 3 or more AI subscriptions, you're probably better off paying for one that has a decent range mod models. For me, so far, this is paying $20/mo for Cursor so I can access the "built-in" Opus and Sonnet. And even sometimes Haiku (super fast and simple) for non-coding things like writing emails or support docs.

I also pay $20/mo to OpenAI for ChatGPT but now I'm trying out the Codex coding environment that all works within the same $20/mo subscription.

I don't feel like I've simplified anything at all here but it might be useful info for someone cruising by this post

@David-Healey said in This script processor has a network that consumes the parameters:

The only place you should use var is within functions and paint routines. In on init you should use const as much as possible, followed by reg. In MIDI callbacks and inline functions you should use local.

We should just use var everywhere and let the parser/compiler sort it out.

@Christoph-Hart How are you finding Opencode? I'm trying out a few but haven't landed on one I like best yet.

Cursor: love the chat history and better context management, but steering messages are janky
Claude Code: like the simplicity of single terminal window but not really the resulting view
Codex: love the split chat/diff layout and it has chat/task history too, best so far for me

Haven't tried Opencode yet. Looks a lot like Claude Code in layout and style.

@Jeetender Check the docs. Looks like you're missing an 's' at the end - setForwardControlsToParameters

https://docs.hise.dev/scripting/scripting-api/dspnetwork/index.html#setforwardcontrolstoparameters

@David-Healey Oof! It got swallowed up in this commit

Shouldn't we always blame humans? Because everything should be looked over before committing.

@NISHI_MUSIC Sorry, I didn't read your question properly. I thought you were asking what "-inf" represents. But I think you're actually asking if those numbers are in LUFS?

No, the numbers above the meter on the of the Audio Analyser panel are not LUFS. They're simple peak meters.

Top number is the maximum peak value for the buffer.
Bottom number is the "current" peak value, which uses a shorter buffer.

There's no loudness weighting or integration window. They're simple peak calculations for the specific buffer length.

Both values display -inf when the value is below -99.5dB.

@NISHI_MUSIC It means "minus infinity".

Since LUFS are measured with 0dB at the top, and all the values are negative values, the 'bottom' value is negative infinity.

You see it when there's no signal present to measure.

@Christoph-Hart Love the 'coming soon'. Very subtle!

@David-Healey Perfect timing!

@David-Healey Is it finished/functional?

@Orvillain Weird. I'll try it out here again and see if I get the same result.

Is yours a standard mono, 'power of 2' file?

@DanSound I was going to point you to a topic I made a while back about making an FM synth in ScriptNode but I see we already had the 'soft transients' discussion back then!

https://forum.hise.audio/topic/14257/making-a-basic-2-op-fm-synth-in-scriptnode/8?_=1772552990701

@Orvillain To be clear, I was dropping a prepared wavetable WAV into the Wavetable Synth.

I'm not sure about the Wavetable Creator.

Are you dropping a wavetable WAV or just a plain WAV and hoping to make it into an interesting wavetable?

I have no idea how the Wavetable Creator works, or what it's for!

@Orvillain After dropping the wav file into a Wavetable Synth, use the saveAsHwt() function to turn it into a precomputed HWT.

See this post, and surrounding posts, for details: https://forum.hise.audio/post/114563

@Lindon said in Builder InterfaceTypes:

According to Claude:

"SynthGroup" = Synthesiser Group
"SynthChain" = Container

Remember that names can change magically for no reason between source code, docs and HISEscript

@Christoph-Hart haha, I had several 'overload' messages from the Anthropic API yesterday and thought "what do I do now?".

It was then I released how much things have changed in the last few months!

@NISHI_MUSIC I use Gumroad https://gumroad.com

It's not perfect but for what they offer and the hassle they save me, I find the ~12-15% fee easy to live with.

Whatever platform you use, you'll find it easier to sell if you have an existing audience.

Cool looking plugins! Do they use web views by any chance?

@Lindon Fixing regression issues seems like it should be high(est?) priority.