Categories

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

    4 Topics
    93 Posts
    David HealeyD

    Someone just sent me a link to this free AI course from Anthropic https://anthropic.skilljar.com/

  • General questions and announcements about HISE

    8k Topics
    73k Posts
    GabG

    @dannytaurus weird then, I'm not sure why it happens. I'll leave my setup, I added MSVC V143 in the list compared to the default settings.

    VS2026Setup.png

  • Scripting related questions and answers

    2k Topics
    16k Posts
    O

    I'm currently using a transportHandler coupled with the .setOnGridChange to create a FX plugin that sequences different effect settings depending on the measure in the user's DAW. I've noticed odd behavior with the clock.

    If you loop measures 1 through 4, the clock would read these grid points correctly on the first pass. After the first loop, the clock no longer recognizes being positioned in the measure 1, and instead assumes the position of measure 5. Therefore the clock reads:

    [ 1 2 3 4 ] > [ 5 2 3 4 ] > [ 5 2 3 4 ] > etc

    While looping your DAW, the clock acknowledges the loop END point to trigger the Grid Change instead of the START point.

    Is there a way to get the clock to trigger on the loop START point? Or is there some other way to double check the playback position?

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

    196 Topics
    2k Posts
    C

    I opened a thread regarding the problem I mentioned above:

    https://forum.hise.audio/topic/14273/clock-synced-arpeggiator-daw-sync-makes-first-tick-off-grid

    It contains videos and snippets; I don't know if anyone has managed to fix this yet.

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

    357 Topics
    2k Posts
    HISEnbergH

    @alobassmann Why not just recompile it? It only takes a few minutes at most, and is a much more stable way of sharing files (that way you only need to share the ThirdParty folder contents).

    That being said the easiest way would be to zip the full HISE project and send it over. (assuming you have similar OS). Alternatively you could just send the DspNetworks and AdditionalSourceCode folder, though you are most likely going to have issues.

  • A subforum for discussing Faust development within HISE

    114 Topics
    940 Posts
    S

    @PV3679 I solved it on my end by doing 2 steps.

    Renaming the Faust modules parameters to something less generic (So FXslot1_Cutoff instead of simply 'cutoff'. It is my understanding that Faust modules dont like names that are re-used. I compiled ONLY the Faust module (so got rid of other stuff and compiled).

    After that the knobs of the Faust module were working πŸ€·πŸ»β™‚

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

    @David-Healey thanks for replying. I will check out the sites that you mentioned.

  • 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.

    148 Topics
    1k Posts
    dannytaurusD

    @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?

  • If you encounter any bug, post it here.
    2k Topics
    12k Posts
    Christoph HartC

    @David-Healey I don't think it's a regression, if it happens to CUBE then it has always happened - I'm fairly confident they are not using the latest HISE version for their current version.

  • 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.

    22 Topics
    135 Posts
  • 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
    No new posts.
  • The nerdy place for discussing the C++ framework
    183 Topics
    1k Posts
    HISEnbergH

    Mainly a question for @Christoph-Hart .

    I'm working on integrating a thirdparty DSP library (PointToPoint by Hack Audio) with the ThirdParty C++ nodes. The library is pretty simple - it's header only for the circuit definitions, but the core DSP is a precompiled static library (libCircuitModel.a on macOS, libCircuitModel.lib on Windows).

    I've gotten the nodes compiled and working, but my main issue is the linking workflow with the HISE compiler. Since it wipes the binaries folder, the AutogeneratedProject.jucer get's regnerated and my linker settings (a few modifications to the library search path and flag pointing to the libCircuitModel.a) get removed. So I either have to manually add them back or, edit the .jucer. What I am doing now using this edited batchCompileOSX.sh (attached below) and building out of XCode.

    I am just wondering if you have suggestions for a more persistent extra linker flag for the library paths across the different DLL recompiles? I'm thinking something like a config file the HISE can read before generating the .jucer? My system works but it's just a bit clunky right now. I want to open this up for other users so it would be nice to make it compatible with the HISE compiler.

    #!/bin/bash PATH="/usr/local/bin:$PATH" chmod +x "/Users/ernest/HISE/JUCE/Projucer/Projucer.app/Contents/MacOS/Projucer" cd "`dirname "$0"`" "/Users/ernest/HISE/JUCE/Projucer/Projucer.app/Contents/MacOS/Projucer" --resave AutogeneratedProject.jucer // Patch link to the PointToPoint Library XCPROJ="Builds/MacOSX/Hise-PointToPoint.xcodeproj/project.pbxproj" PTP_LIB="../../ThirdParty/src/PointToPoint/lib/Release/libCircuitModel.a" PTP_HDR="../../ThirdParty/src/PointToPoint" if [ -f "$XCPROJ" ]; then if ! grep -q "PointToPoint" "$XCPROJ"; then # Add header search paths sed -i '' "s|HEADER_SEARCH_PATHS = (|HEADER_SEARCH_PATHS = (\"$PTP_HDR\",|g" "$XCPROJ" # Add library search paths sed -i '' "s|LIBRARY_SEARCH_PATHS = (|LIBRARY_SEARCH_PATHS = (\"../../ThirdParty/src/PointToPoint/lib/Release\",|g" "$XCPROJ" # Add CircuitModel.a library sed -i '' "s|OTHER_LDFLAGS = (|OTHER_LDFLAGS = (\"-lCircuitModel\",|g" "$XCPROJ" fi fi # ============================================================ set -o pipefail echo Compiling Hise-PointToPoint ... xcodebuild -project "Builds/MacOSX/Hise-PointToPoint.xcodeproj" -configuration "Release" -jobs "8" | "/Users/ernest/HISE/tools/Projucer/xcbeautify"

15

Online

2.2k

Users

13.4k

Topics

117.1k

Posts