HISE Logo Forum
    • Categories
    • Register
    • Login

    Pan modulation is not working

    Scheduled Pinned Locked Moved Bug Reports
    55 Posts 7 Posters 3.5k 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.
    • ustkU
      ustk @LeeC
      last edited by

      @LeeC Try just to remove the connection and make it again. There are some buggy things sometimes with parameter connections... Might not be that, but it worth trying in your situation :)

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

      L 1 Reply Last reply Reply Quote 0
      • L
        LeeC @ustk
        last edited by LeeC

        @ustk I know what you mean about the buggy parameter connections - tried reconnecting but no luck.

        In fact, I’ve actually tried with no parameter connection at all, I set the mode on the oscillator to ‘square‘ and exported the FX plug-in. The result?...... It flipped back to ‘sine’ mode after loading the AU 🙃

        1 Reply Last reply Reply Quote 0
        • L
          LeeC @Brian
          last edited by LeeC

          @briandoliveira if you get a chance to build a plug-in Fx version your end and send me a link to it would be helpful.
          I must have something setup badly in my export compile settings somehow... This is all I can think of right now.

          ustkU BrianB 2 Replies Last reply Reply Quote 0
          • ustkU
            ustk @LeeC
            last edited by ustk

            @LeeC It sounds like you're using a version where all waveshapes are sines (even if the drawing shows all the shapes in the node). Christoph added the shapes not so long ago (2 weeks?). Since it works for you in Hise but not in the exported plugin, it might be related to the Hise path. I know you just showed us it's pointing at a good path, but... I can't see anything else. Especially since it's working for two of us :)

            I also noticed that you might not be using GitHub, if it's the case you might want to think about using it. You'll never have to worry about the path anymore ;)

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

            L 1 Reply Last reply Reply Quote 0
            • BrianB
              Brian @LeeC
              last edited by

              @LeeC here is the AU version, I have been having a busy day at the studio so no chance to test this version yet :

              PANNER TEST AU.zip

              favicon

              Google Docs (drive.google.com)

              1 Reply Last reply Reply Quote 0
              • L
                LeeC @ustk
                last edited by

                @ustk yes I’m thinking that it’s related to the HISE path also. I’ve noticed in the past that changing it to point to a new path doesn’t always take effect and I’m confident that this is what’s happening here.

                What I see isn’t what I’m getting so to speak.

                Ok, so using github with HISE sounds promising. Is this quick and easy to do?

                BrianB 1 Reply Last reply Reply Quote 0
                • BrianB
                  Brian @LeeC
                  last edited by

                  @LeeC indeed it is! @d-healey has been kind enough to make a very thorough video on how to set this up https://www.youtube.com/watch?v=Bs3zI5Dtvn0&list=PLynv7CujPCfbH2OPE-cC5F4ZK-sVGkBwx&index=20&t=0s

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    LeeC @Brian
                    last edited by

                    @briandoliveira I should have known that @d-healey would've had this covered. Thanks again!

                    1 Reply Last reply Reply Quote 1
                    • L
                      LeeC
                      last edited by

                      @ustk @briandoliveira

                      Just a quick message to thank you both again for your time.

                      Finally managed to get it all sorted by deleting the '.xcodeproj' file in project>binaries>builds>MacOSX and rebuilding using the 'AutogeneratedProject.jucer'. There seemed to be some sort of Hise Path conflict I think.

                      Hope you're both good!

                      BrianB 1 Reply Last reply Reply Quote 1
                      • BrianB
                        Brian @LeeC
                        last edited by

                        @LeeC its me to thank you and @ustk ! I learnt allot from this as well and it solved a major problem on my end with the instrument that I am developing :)

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

                        39

                        Online

                        1.7k

                        Users

                        11.7k

                        Topics

                        101.9k

                        Posts