HISE Logo Forum
    • Categories
    • Register
    • Login

    When I compile vst with a HardcodedMasterFx, vst3 does not appear in the DAW, when I remove it it appears

    Scheduled Pinned Locked Moved General Questions
    6 Posts 2 Posters 360 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.
    • K
      klaytonrangel
      last edited by

      When I compile vst with a HardcodedMasterFx, vst3 does not appear in the DAW, when I remove it it appears.

      A 1 Reply Last reply Reply Quote 0
      • A
        aaronventure @klaytonrangel
        last edited by

        @klaytonrangel do you have the network in the chain which has the Compiled flag enabled? If you do and export with that, the plugin will just not scan properly.

        K 1 Reply Last reply Reply Quote 0
        • K
          klaytonrangel @aaronventure
          last edited by

          @aaronventure
          Good afternoon, thank you for your attention.
          I don't know if I understand correctly but here we go.

          • I have the interface with the design.
          • I have a ScriptFx with a Faust.
          • I compiled ScriptFX in DSP compile
          • I added a HardcodedMasterFX and linked it with the compiled DSP.
          • Deletes ScriptFx from the project.

          When I export VST3 it disappears from REAPER, if I remove Hardcoded and update VST3 it appears again in REAPER without any effect working.

          What am I doing wrong or not doing?

          Sorry if my English is incorrect, I'm using Google Translate as I'm not fluent, and I didn't find any help in PT-BR

          A 1 Reply Last reply Reply Quote 0
          • A
            aaronventure @klaytonrangel
            last edited by

            @klaytonrangel In order to compile the effect, you had to right click the node and set "Allow compilation" to enabled.

            If you export a plugin with that network in the chain, it will fail to scan in Reaper. But it looks like you're not using it in the chain.

            Try compiling and empty network into a hardcoded fx, see if that works. If that works, then the problem is somewhere in your network. Now you have start removing things from your network one by one until it works. Depending on the size of your network, this can take a bit.

            If the plugin would run then you could run it with a debugger but since it's not scanning at all, you gotta do it step by step to find the culprit. I suggest putting some music on, maybe grabbing a drink 😄

            K 1 Reply Last reply Reply Quote 0
            • K
              klaytonrangel @aaronventure
              last edited by

              @aaronventure
              I enabled compilation on the ScripFx node and compiled the DSP, but I will redo the chain, it must be some oversight, but I appreciate your help, thank you very much.

              1 Reply Last reply Reply Quote 0
              • K
                klaytonrangel
                last edited by

                UPDATED - SOLVED

                Good evening, it was really a lack of attention, to do a multibend in the designer I created a custom js in the interface, I referenced ScriptFX and forgot to remove this line that was now supposed to reference HardcodedMasterFX. Thanks for the help..

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

                27

                Online

                1.7k

                Users

                11.8k

                Topics

                102.8k

                Posts