Forum
    • Categories
    • Register
    • Login
    1. Home
    2. Sifres
    3. Best
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 12
    • Groups 0

    Posts

    Recent Best Controversial
    • The buggy road to my first plugin

      164ffaa0-3b5c-4d0c-910c-cf76d0a49ee3-image.png

      I know its a provocative title but made you look 😉

      Ok so let me start by saying Ive been on Hise for the last one and a half month developing and having a great time. The interface / logistics take some time to get used to, but getting the hang off where what and when. Its a really nice lowcode solution and I thorougly enjoy development. The MCP server is really nice to work with as well and really adds to Claude's knowledge which speeds up everything.

      BUT

      I've seen and worked around a LOT of bugs in the development of my first plugin and am kind of doubting if a commercial license and release is worth it. Let me sum them up. This is building on Windows.

      - Faust: There is a bug in the Faust handling and it would stop working after export to VST.
      WORKAROUND: Made a very simple Script FX containing only the Faust node, and made sure names werent duplicate.
      - Feedback / delay loop from template. Clicking in the menu to compile to DLL would crash Hise. After a lot of excluding, the feedback loop (from template!) is the culprit.
      WORKAROUND: I cant compile the entire network to DLL, but this isnt needed. This DOES force me to compile SNEX nodes seperately and excludes the waveshaper (because apparently this needs a compiled state). Also it's bad for performance.
      - GlobalMod LFO. I used a custom Script LFO one. Again on exporting, this would stop working.
      WORKAROUND; After a lot of puzzling the answer was to precompile the node in a minimal scriptnode, instead of a Hardcoded modulator, and wire up again. This however made the raw signal unusable for the LFO led on my frontend.
      - Any kind of analyser crashes HISE. For some reason when I click on the analyser tab when I want to add an analyser node, it crashes. I know it preloads existing nodes as well, so might have been me FAFOing but its not pretty
      WORKAROUND: The LFO signal couldnt be picked up by an analyser, but the Globalmod receiver did have a displaybuffer. Used that instead. Was harder to set up, because this was in the path of the Cutoff, and not the Pitch (which was wired into the Waveform generator).

      So basically I feel like there is some technical debt bugwise. I would like to contribute and file these as proper bugs on github. Hell I'll even wire up Claude to make some code proposals if it helps. What would be a good way to do this? Where do crash logs go?

      Is there any chance on a hardening development round, now that we have had some cool stuff on the AI side?

      posted in Newbie League
      S
      Sifres
    • RE: Agentic coding workflows

      @Christoph-Hart

      d0a930b1-cb19-4313-bf30-5a445a8e6781-image.png

      Really nice work man! Gonna play around with it. Its already mouthing me off on button placement 🤖

      posted in AI discussion
      S
      Sifres
    • RE: Moonbase

      Anybody who has tried to set this up? Want to give it a go next week, and wanted to check if there are any pitfalls you guys ran into?

      By give it a go I mean Hise + Juce8 and Moonbase as a license module.

      posted in General Questions
      S
      Sifres