1. Home
  2. Categories

Categories

  • Let's discuss the latest AI tech and how it influences your life as a HISE developer.

    14 Topics
    189 Posts
    Christoph HartC

    Is it possible to tell the AI not to do some of those tasks?

    sure. I mean you have to tell it to use these tools in the first place, so if you keep it a secret from your robot, it will never call hise-cli. Once the dust settles I'll try setting up system prompts / agents.md file templates that teach the AI the optimal usage of this tool.

    The ROI on it letting it compile the project for you is pretty narrow, so that particular set of commands might not be the most thrilling thing to teach the agent - however the hise-cli offers a script runner that can perform build steps for you.

    /hise launch # open HISE /builder reset # clear the module tree /project # Enter project mode export dll # compile the DSP network dll load MyProject.xml # load your XML preset backup export project # VST3 as default export project with format=Standalone # export App /exit # leave project mode /hise shutdown # good bye

    is basically the full cross-platform build script that automates the export for you. you then just need to call hise-cli --run "build.hsc" (or even register hise-cli as shell script runner, then the script file itself becomes executable).

  • General questions and announcements about HISE

    8k Topics
    74k Posts
    Y

    @Oli-Ullmann Thank you so much

  • Scripting related questions and answers

    2k Topics
    16k Posts
    ChazroxC

    @Lindon Still a good read either way. Good stuff to know. 🤛

  • To share HiseSnippets, Interface Elements, GUI, UI/UX, Panel LAF etc..

    197 Topics
    2k Posts
    jadgJ

    Here is a video where you can see better the visual details:
    Fully customized pseudo backlit interface via LAF

  • All about ScriptNode DSP nodes, patches, SNEX and recipes.

    366 Topics
    2k Posts
    HISEnbergH

    @Jeetender It looks like you didn't grab the source code for the Tube2 implementation. There's usually 3 things you need:

    This Airwindows.h file, which is the main wrapper for all of the FX.
    DspNetworks/ThirdParty/src/airwindows/AirWindows.h

    The individual wrapper file (Tube2.h)
    DspNetworks/ThirdParty/Tube2.h

    And the source code for the individual FX (Tube2 subfolder)
    DspNetworks/ThirdParty/src/airwindows/Tube2

    *Note 1: I had issues compiling all of the FX simultaneously so I initially broke this library into 2, so Tube2 wasn't included in the original version. I just added it, checkout the dev branch specifically.

    *Note 2: The individual source code for all of Airwindows FX are basically the same. There's typically 3 files:
    Tube2.cpp
    Tube2.h
    Tube2Proc.cpp

    Currently I accidentally pushed a version with a .inc extension. I'll try to fix those but you can manually remove those for now.

  • A subforum for discussing Faust development within HISE

    115 Topics
    949 Posts
    M

    @Christoph-Hart said in Instant crash when loading any faust dsp to the module:

    @Lindon damn, alright then. macOS or windows?
    macOS arm 64 bit

  • If you need a certain feature, post it here.
    627 Topics
    5k Posts
    ustkU

    As in title?

  • Develop better software through collaboration and shared knowledge. Not just about coding —> covering the entire journey, from development to launching and promoting plugins or software.

    167 Topics
    1k Posts
    O

    @David-Healey I’m changing the array right away. Thanks a lot and Yeah :D I finally got all the mechanical recordings done in the studio. Since I had already finished the grueling dynamic velocity layers a while ago capturing the mechanical sounds this time around was an absolute breeze in comparison.

    By the way, I watched your Ardour video and built my own workflow for sample editing based on it. It is incredibly helpful, thank you so much for putting that out there.

  • If you encounter any bug, post it here.
    2k Topics
    13k Posts
    ustkU

    @Christoph-Hart awesome! I was in the same situation so 👍

  • Post your example snippets that you want to add to the official HISE snippet database here. We'll revise it, upload it to the repo and delete the post when finished.

    23 Topics
    140 Posts
    CasmatC

    @Christoph-Hart yeah, here's what I could come up with!

    The model occasionally thought you could add child panels directly to viewports. It didn't properly cast/convert the raw result of vpt.get("scrollBarThickness") for calculations. It hallucinated a scroll event listener/callback for viewports. I needed to prompt it specifically to use a 30Hz timer loop for position updates instead. It had the most trouble with local, reg, and const. Especially in long generations with multi level functions, it tried standard JS var/let scoping, leading to long runs of compilation errors. I mainly used Google's Gemini 3.1 Pro via Antigravity, but I also tested Claude Opus/Sonnet 4.6. The Anthropic models had a couple fewer issues, making sense if the MCP server is currently tailored to their behavior.

    I had checked out the viewport's multicolumn mode. I built this as a ScriptPanel recycler to have high LAF control over individual buttons and icons for a custom preset browser. I wouldn't be able to get the same component styling flexibility with multicolumn mode.

    I'll try out the LSP server! I've been following HISE's ai journey and can't wait to see what's next! Being a dev who uses AI to assist in most my work nowadays, it'll make HISE development much much faster and accessible lol. Love the forum, but I dream for the days where I'll ask Claude to explain why my function call is wrong and @David-Healey can enjoy his vacation instead! 😁

    The MCP server in antigravity is amazing, but there's a couple things HISE struggles with against AI.

    Absolute positioning is a bottleneck. Is there anyway to expose JUCE's FlexBox/Grid to hisescript? It would be life changing. If the model can just write relative values, it wouldn't have to guess pixel coordinates anymore. Can't wait for scriptnode to work with MCP. Having models build scriptnode networks from text/json, or piggybacking faust, will make that rodeo a lot simpler.

    I can envision HISE's future as a sidecar rendering engine alongside your everyday IDE, which wil be where the actual code writing/editing and prompting happens. Having HISE run in a headless like manner to compile the plugin, fix errors, and run tests would have massive potential. The LSP and MCP server are great starts for this.

  • Everything related to the documentation (corrections, additions etc.) can be posted here
    71 Topics
    481 Posts
    Christoph HartC

    @username1234 this is a thing that I vibecoded last week - it‘s super fresh but yes once that is tested a bit it will definitely be recommended as the preferred way of getting hise setup for development. Just be a bit more patient my friend.

  • Collection of Blog Entries

    81 Topics
    770 Posts
    David HealeyD

    Another one you might be interested in is Floe: https://floe.audio/

  • The nerdy place for discussing the C++ framework
    184 Topics
    1k Posts
    HISEnbergH

    @Allen Ah thanks for clarifying. I believe this should work the same for RNBO node as any other C++ node. You need to add these flags to your projects Extra Definitions:

    NUM_HARDCODED_FX_MODS=4 //or however many slots you need NUM_HARDCODED_POLY_FX_MODS=4

    It is possibly you may need to first add that to HISE's extra pre processor definitions in projucer first and recompile HISE, then also add those to your project (so it works in the compiled plugin).

    The documentation about this is a bit hard to find. There's also a forum post about it here.

    Here is a spreadsheet of the different HISE flags you can use (it needs to merge this into the documentation somewhere).

    Just for some extra context this is straight from the docs:

    // number of modulation slots for Script FX HISE_NUM_SCRIPTNODE_FX_MODS=0 // number of modulation slots for Polyphonic Script FX HISE_NUM_POLYPHONIC_SCRIPTNODE_FX_MODS=0 // number of modulation slots for Scriptnode Synthesisers HISE_NUM_SCRIPTNODE_SYNTH_MODS=2 // If you plan to compile the DSP network to a C++ node // (which is possible with this node since HISE 5.0), you will // also need to set the corresponding preprocessor variables // for the hardcoded modules: // number of modulation slots for Hardcoded FX modules NUM_HARDCODED_FX_MODS=0 // number of modulation slots for Hardcoded Polyphonic FX NUM_HARDCODED_POLY_FX_MODS=0 // number of modulation slots for Hardcoded Synthesiser NUM_HARDCODED_SYNTH_MODS=2

21

Online

2.3k

Users

13.6k

Topics

118.6k

Posts