Tips for structuring audio plugin development workflows

[Funnelsflex]

Hi everyone,

I’ve been learning more about audio plugin development and how to keep projects organized as they grow in complexity. One challenge I keep running into is making sure I have a clear workflow from idea → prototype → testing → release without losing track of details.

At Funnelsflex (................
), we often talk about how structured workflows help reduce mistakes and make collaboration smoother. I’m curious if anyone here has developed a set of practices, tools, or templates specifically for audio plugin development — especially with HISE — that help keep things consistent and efficient.

Some questions I’ve been thinking about:

Do you break development into set stages (e.g., UI design → DSP → scripting → testing)?

What tools or methods do you use to keep edits and revisions traceable?

Any tips for avoiding repetitive mistakes when iterating on presets or modules?

Would love to hear the community’s approaches — thanks in advance!

[Lindon]

@Funnelsflex said in Tips for structuring audio plugin development workflows:

Some questions I’ve been thinking about:

Do you break development into set stages (e.g., UI design → DSP → scripting → testing)?

We try - but some design (product not UI) ideas only come thru usage of the test versions...

What tools or methods do you use to keep edits and revisions traceable?

Git and GitHub

Any tips for avoiding repetitive mistakes when iterating on presets or modules?

include("yourHSIEScriptfileHere.js);

[Christoph Hart]

@Lindon I think you’re advising a robot here.

[Lindon]

@Christoph-Hart Great! I've always wanted to advise a machine.!!!

[ulrik]

@Lindon Haha!