HISE Logo Forum
    • Categories
    • Register
    • Login

    There's something I don't understand about compiling a plugin

    Scheduled Pinned Locked Moved General Questions
    20 Posts 3 Posters 118 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.
    • OrvillainO
      Orvillain @d.healey
      last edited by

      @d-healey It crashes pluginval - I'm building a VST3.

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

        @Orvillain debug build?

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

        OrvillainO 2 Replies Last reply Reply Quote 0
        • OrvillainO
          Orvillain @d.healey
          last edited by

          @d-healey Okay, I went back to your suggestion of making a new project and just putting in the wavetable synth and including the wavetable files. That plugin does instantiate.

          So either clearing the sample maps and samples wasn't enough to make my actual plugin no longer attempt to reference sample maps... or something is going on with my custom DSP networks (hardcoded)

          1 Reply Last reply Reply Quote 0
          • OrvillainO
            Orvillain @d.healey
            last edited by

            @d-healey No, wasn't running the debug build of pluginval. I can do.

            OrvillainO 1 Reply Last reply Reply Quote 0
            • OrvillainO
              Orvillain @Orvillain
              last edited by

              @Orvillain Okay.... went to my original project.... but a new xml file.... added a waveform generator and my poly ring mod network. Compiled plugin. It loads. I'll do this and go through each of my networks to isolate the one that doesn't run. If they all do... then I'm back to suspecting the samplers as the issue.

              OrvillainO 1 Reply Last reply Reply Quote 0
              • OrvillainO
                Orvillain @Orvillain
                last edited by

                @Orvillain Okay. It isn't my networks. They will all run inside a plugin - one instance of them anyway.

                OrvillainO 1 Reply Last reply Reply Quote 0
                • OrvillainO
                  Orvillain @Orvillain
                  last edited by

                  @Orvillain Godddd I am so dumb.

                  cfbec723-d45d-476e-acdd-8555171c263d-image.png

                  I even bloomin' new about this, and just totally forgot! Commenting this out, and now the plugin compiles.

                  Basically, I found in the past that calls to the Builder could crash plugins. So I wrap all my Builder logic in a namespace, and I am SUPPOSED to remind myself to comment these lines out when building the plugin.

                  I'm pretty sure this is what was causing the crash on instantiation.

                  OrvillainO d.healeyD 2 Replies Last reply Reply Quote 0
                  • OrvillainO
                    Orvillain @Orvillain
                    last edited by

                    @Orvillain Also something to bear in mind, the docs say this:

                    Be aware that the wavetables will not be embedded into the binary, so if you don't want to use the monolith format, you have to untick the Embed AudioFiles option in your project settings. Also the Monolith file takes precedence over the source .hwt files, so as soon as you've created a .hwc file in the sample folder, the list of available wavetables will not reflect the audio file folder content.

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

                      @Orvillain said in There's something I don't understand about compiling a plugin:

                      Basically, I found in the past that calls to the Builder could crash plugins. So I wrap all my Builder logic in a namespace, and I am SUPPOSED to remind myself to comment these lines out when building the plugin.

                      According to the docs it should be disabled automatically anyway, even if you forget

                      This is connected to the former point: never ever use calls to the Builder in a compiled plugin (in fact, they are deactivated in the compiled plugin so don't expect them to work).

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

                      OrvillainO 1 Reply Last reply Reply Quote 0
                      • OrvillainO
                        Orvillain @d.healey
                        last edited by

                        @d-healey Probably a bug of some kind then. All I can say is, commenting out TreeBuilder.buildModuleLayout() cured my crash. Chased my own tail for a bit over that is all!

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

                        26

                        Online

                        1.8k

                        Users

                        12.1k

                        Topics

                        104.9k

                        Posts