HISE Logo Forum
    • Categories
    • Register
    • Login

    Compiled VST3 FX Plugin crashes when using Routing Matrix

    Scheduled Pinned Locked Moved Bug Reports
    13 Posts 5 Posters 540 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.
    • oskarshO
      oskarsh
      last edited by

      I figured it out, it's not the Routing Matrix its the channel amount. If you use more than 2 channels it instantly crashes when opening. I tested with standalone and vst3. Also forcing stereo output does not help.
      @Casey-Kolb Try building your plugins against the master it seems like this bug does not exist there. I was not able to pinpoint the exact commit where this started happening.

      @Christoph-Hart you should be aware of this bug and maybe know what could cause this.

      HISE Developer for hire :)

      Casey KolbC 1 Reply Last reply Reply Quote 1
      • Casey KolbC
        Casey Kolb @oskarsh
        last edited by

        @oskarsh I'm almost certain it's related to this commit if you look at my crash thread: https://github.com/lunacyaudio/HISE/commit/367cae32bc2dcba48fb0d6359295da2bedac29d2

        The crash happens right when setSize is called on the AudioBuffer.

        Casey Kolb
        Founder & CEO of Lunacy Audio
        Composer | Producer | Software Developer

        1 Reply Last reply Reply Quote 1
        • oskarshO
          oskarsh
          last edited by

          @Casey-Kolb this looks pretty plausible. How can you log the crash report? Do I need to compile my plugin with the Debug configuration or is it enough to enable setEnableDebugMode in my plugin? I want to debug these kinds of errors myself in the future.

          HISE Developer for hire :)

          Casey KolbC 1 Reply Last reply Reply Quote 0
          • Casey KolbC
            Casey Kolb @oskarsh
            last edited by

            @oskarsh You'll just need to compile the Debug version of your VST or standalone app. You can open the Autogenerated Projucer file in your project's Binaries folder and then export the plugin from Xcode. From there you can choose to "Build For Testing"

            Casey Kolb
            Founder & CEO of Lunacy Audio
            Composer | Producer | Software Developer

            1 Reply Last reply Reply Quote 1
            • Dan KorneffD
              Dan Korneff
              last edited by

              On Win11/Cubase12/VS2022 I'm seeing this at launch:

              JUCE Assertion failure in juce_AudioSampleBuffer.h:421
              

              Also, the exported plug-in doesn't show up in Reaper.

              Dan Korneff - Producer / Mixer / Audio Nerd

              1 Reply Last reply Reply Quote 0
              • O
                optimistic
                last edited by

                Same experience here.

                Instruments are building and working as expected but VST3 and AU are crashing Logic and Ableton.

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

                  So just to recap: multichannel plugins crash with the latest commit?

                  1 Reply Last reply Reply Quote 0
                  • oskarshO
                    oskarsh
                    last edited by

                    @Christoph-Hart yes correct FX plugins crash with multichannel amount != 2.

                    I have not tested instrument plugins.

                    HISE Developer for hire :)

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

                      I've committed a fix for it, was indeed a trivial issue. Let me know if it works now.

                      O 1 Reply Last reply Reply Quote 3
                      • O
                        optimistic @Christoph Hart
                        last edited by

                        @Christoph-Hart Just rebuilt the latest commit and confirm the issue is fixed here. Thanks for sorting this out so quickly!

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

                        57

                        Online

                        1.7k

                        Users

                        11.7k

                        Topics

                        102.1k

                        Posts