HISE Logo Forum
    • Categories
    • Register
    • Login

    Scriptnode build fail with custom cpp enabled

    Scheduled Pinned Locked Moved General Questions
    3 Posts 2 Posters 202 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alepan
      last edited by alepan

      Hi all, I'm trying to recompile HISE scriptnode after following the instructions to enable custom cpp, that is:

      1. in HISE, setting the path to a folder where custom cpp modules will be stored
      2. in Projucer, in hi_modules: HI_ENABLE_CUSTOM_NODE_LOCATION -> Enabled
      3. in my project, exported the scriptnode module as custom cpp class (maybe I should have chosen project cpp class o base64? I'm no expert...)
      4. recompiled HISE, obtaining this error:
      template <class T> void setInternalModulationParameter(T* modObject, const DspHelpers::ParameterCallback& f)
      	{
      		modObject->setCallback(f);
      	}
      

      /Users/ale/Documents/SOFTWARE PER INSTALLAZIONE HISE/HISE-develop_LATEST_WORKING/hi_scripting/scripting/scriptnode/api/StaticNodeWrappers.h:425:14: No member named 'setCallback' in 'scriptnode::bypass::yes<scriptnode::wrap::modscriptnode::core::peak, true>'

      Any suggestions on how to solve this issue?
      Thanks a lot!

      P.S.
      This is the Projucer page :
      ![alt text](Schermata 2020-04-28 alle 13.43.37.png image url)

      ustkU 1 Reply Last reply Reply Quote 0
      • ustkU
        ustk @alepan
        last edited by

        @alepan Some nodes fail to be exported, like the core.jit for instance, and probably other...
        Try first with just a gain node inside a chain to test if it works.
        If you succeed with this setup, but not with other nodes, you got your answer.
        And since everything is being rewritten, you gotta wait for the release of the new version to make it work

        Currently, I don't export custom nodes anymore until the next release.
        If you need the same chain several times in your graph, you can copy/paste

        Can't help pressing F5 in the forum...

        A 1 Reply Last reply Reply Quote 1
        • A
          alepan @ustk
          last edited by

          @ustk Ok, that's probably the reason, as I exported a container with a lot of thingies insiede... Well, I'll wait for the new version then!
          Thanks!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          28

          Online

          1.8k

          Users

          12.1k

          Topics

          105.4k

          Posts