HISE Logo Forum
    • Categories
    • Register
    • Login

    This script processor has a network that consumes the parameters

    Scheduled Pinned Locked Moved General Questions
    scriptnodecallbacknetwork
    9 Posts 5 Posters 718 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.
    • d.healeyD
      d.healey
      last edited by

      Trying to add a combo box with a control callback to my scriptFX (that also has a network). What does this message mean and how do I get rid of it? :D

      This script processor has a network that consumes the parameters

      Libre Wave - Freedom respecting instruments and effects
      My Patreon - HISE tutorials
      YouTube Channel - Public HISE tutorials

      modularsamplesM 1 Reply Last reply Reply Quote 0
      • modularsamplesM
        modularsamples @d.healey
        last edited by

        @d-healey I ran into the same message, but under different circumstances, my combobox is selecting UI elements..

        I guess you've figured it out by now, but what cleared it up for me was exporting the preset as snippet and then importing it, after that the message was gone.

        d.healeyD 1 Reply Last reply Reply Quote 0
        • d.healeyD
          d.healey @modularsamples
          last edited by

          @modularsamples Yeah I ran into this again yesterday and can't remember how I solved it :p

          Libre Wave - Freedom respecting instruments and effects
          My Patreon - HISE tutorials
          YouTube Channel - Public HISE tutorials

          Christoph HartC Adam_GA 2 Replies Last reply Reply Quote 0
          • Christoph HartC
            Christoph Hart @d.healey
            last edited by

            @d-healey A scriptFX will forward the parameter callbacks to the DspNetworks parameters by default so that combobox callback will not be executed and this message is supposed to save you some brain cells. You can use DspNetwork. setForwardControlsToParameters(false) to deactivate this and implement the callbacks for your scripted UI elements.

            Adam_GA 1 Reply Last reply Reply Quote 2
            • Adam_GA
              Adam_G @Christoph Hart
              last edited by Adam_G

              @Christoph-Hart i tired using this in the onInit but got an error

              "Interface:! Unknown function 'setForwardControlsToParameters' {SW50ZXJmYWNlfG9uSW5pdCgpfDEzM3w3fDQy}
              : onInit() - Line 7, column 42 {SW50ZXJmYWNlfG9uSW5pdCgpfDEzM3w3fDQy}"

              Does this command go some where specific?

              @modularsamples unfortunately exporting as a snippet and reimporting did not work for me

              1 Reply Last reply Reply Quote 0
              • Adam_GA
                Adam_G @d.healey
                last edited by

                @d-healey any recollection how you figured this one out?

                Christoph HartC 1 Reply Last reply Reply Quote 0
                • Christoph HartC
                  Christoph Hart @Adam_G
                  last edited by

                  @argon Use the solution I posted above. And don't type in DspNetwork.xxx but use your object name instead:

                  const var dsp = Engine.createDspNetwork("whatever");
                  dsp.setForwardControlsToParameter(true);
                  
                  Adam_GA HISEnbergH 2 Replies Last reply Reply Quote 0
                  • Adam_GA
                    Adam_G @Christoph Hart
                    last edited by Adam_G

                    @Christoph-Hart thanks so much, that set me on the right path. it works now :)

                    1 Reply Last reply Reply Quote 0
                    • HISEnbergH
                      HISEnberg @Christoph Hart
                      last edited by HISEnberg

                      @Christoph-Hart I think I am missing something but this won't work for me.

                      The "whatever" here is just the name of the scriptFx correct (whatever we named the xml file)?

                      ** Edit: Something strange with how the project was set up. There is something buggy about this feature that I can't quite put my finger on. Does the scriptnode have to be compiled to dll first? I solved the issue but I can't say exactly how. This has happened to me numerous times in the past.

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

                      58

                      Online

                      1.7k

                      Users

                      11.7k

                      Topics

                      101.8k

                      Posts