HISE Logo Forum
    • Categories
    • Register
    • Login

    How to ensure MIDI Overlay Panels Load on Exported Plugin?

    Scheduled Pinned Locked Moved Scripting
    7 Posts 4 Posters 244 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.
    • M
      Mwins
      last edited by

      I am running into a peculiar issue with the MIDI Overlay Panels. I have 2 floating tiles that reference 1 MIDI player. One is set as the MIDI viewer and the other is set as the Drag/Drop. When the plugin loads, it may or may not show my MIDI panels. The MIDI player will play but without the panels, you can't see or drag and drop the midi. Weird thing is, the issue doesn't always happen. Its intermittent. This is on an exported instance.

      Anyone else run into this?

      Christoph HartC CatABCC 2 Replies Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart @Mwins
        last edited by

        @Mwins Can you make an isolated snippet that reproduces the issue? I wouldn't know what could cause this, so I have to debug it.

        1 Reply Last reply Reply Quote 0
        • M
          Mwins
          last edited by

          Sure, I was able to solve it by allowing the script to fully load before loading the Panels. I was coming back on here to edit the post and saw your message. I will try to recreate it and post a snippet.

          1 Reply Last reply Reply Quote 0
          • M
            Mwins
            last edited by

            Turns out, that did not fix it. Here is a snippet HiseSnippet 1504.3oc4X80bSaDDWJNJfcoTfgG5Lc5LZxzNCLjpwNIjjg9.J1JFLDmnIxPAFOk4hzY6iHcm5oSgXX3c9rzoOzOB7QoeD3a.cOI+GIiav3gRSa8Cdzt2tm9c6t2ucss4LWbTDiqnVrU+Prh5Ezb5SE8p0CQnJMrTTuhVKbjPuYCqF5g9n9XtR09gnnHrmhpZg6HsSs3hJIed6sqh7QTW7XUJJOjQbw6RBHhwZsMuOw2uNxC2hDjw50Ma3xn0X9rX.SEzJqDhbOB0EuGRZ1BZJpKsiGQv3NBj.GontXUlWemdrmSSs+gjHxg9XoPEEGXiRUWm46IQr7YkZ8H9d1CO6QJJpZ1iiDERiDWUqIwiLR+3HxkRVPerGYiGpKbZvqxbBO0LvawT3cYMGWNITLdEI19BsFTAl2AAofrvJ0VE02nUiAFPEFAniv04fvHGt1FkKuhN700+wNwTWAgQ0Yz8XB79zqc8RurTwRupj9jK0oyTWS9Z3LeeLepKKy57SywqQiCNDyWQ+XjeLdjgvwOe7coYK95ldpyXHi1fRD6GhGHONCTYJY.kAgM3oGzvBIPxjx.cfcgXtfHgipE9XnZOMEUTyBGcjfEBEt0XAgLpbGTKJFTeklTp6yPBBsaKB.aBffuRKqpJJmL55wa5Z1e7ckFlC.P5a6JIkk6eLlC2RsQTruxgcGdSp3RfCeuzKh.GLV6qe8qeWdsqJUaYYknN4jptu1KKoqu7n3QCukuk9xILB1ILBUVdEoAMnd3SfkpjHAATe1y+IF+nH3NLFz2A4GgK8JYvbNCFq9WFLrNqFLJ+gBFu+Uaffg4E6iD4YcjTsCV.tpj65s7NLMhH5mkJ9ifJp7Tohl5EgYDtWVylHb6Mc7tvTvKbg5ua7NfX+K01oSGrqXLXWTq9ilWV74CJe6vxTGAGiBfxaGTPHvVlfmRZCjp7onWa3L2q0ligKadNjWjwr2XVMFhW77Z+cyjW01ArXZt20.je.NDiDP5OiOm27fCtCmEGNoWu81IEKs3PudHTjcg8oXHtKxdFqwYQQcfiSxdEkcI6XdWYrZrlCv.GPTdc6EG.4dJPJ.NqopJI0ivxbMwsIRvImj05j2R4Vnj7ML.RhbkIjWcB40lPd8Iju4DxaLg7likSCnMQgxJC4.PSzA7byVGPXCR3AyXYUR2Qadpl7TLYLcTLOAWYF2ZJCqrz+dlk5bCG5MAdoS2Jg0E0xRnmCT0h4b4jD3eIFm+xm4fkRJiyVCuKiEtCUF37xUyC69gfoNg37KnVH+4tvrctmBii7XUG5aJO2KLT.rdPoTZGsiz1bCCZqMt+V0p9L26ZX7r6Y6zpa8Ga.epaXaXXc75zWX8fShpCZ53YXzXe+G2v13Dxiue0SHFFOh1o4Z2H1vtpwcspZ2r61Q2qypk2Ysd23Y0d9K1yng2SdvgUMTju+zQ4aoU6Vsgqc7n1QH.gssXtwAP3KpcKLLdP6QXu8Vk2R+GzqFG0WWRWhE5fXkM17vv.3AWlrD9Di.43BpRJNGRWJRDyg2xRvc8pHdFRBcy8X.eqra0XkWxzBSmlZYpCRC7bDPo4yborDHKU7aO4a9U0+vyT4rUzdkIi1aGFJwS6cYtH+jHdaXpmvyHQwTE+r4mugiJLac3+.7IEGhQGhrnbG5wPCUPS5Oj1B2AE6KFpMOuRSFkE1iQIt4aeAsi51Eyyh8odf1VHxQ6bUyCv9XTTFFpuybWBEi346J+QEKpL6whSKe80ZovUWVno+eigZK7+9gZOsP2EGLRqdJOvY677EzRFBSWNy7+TP8.Vr7W8NbdTMfB1AFT2Emcz0EjiCmJWVJKAjCl5kH7N3yfEqLbNW4hUFtnh6vsBNaCdNsIUA7vwUTWvGlf1OaIcD7yAjPBZo8YAkAHWN6oto+uPRrd9DM.JoI81Jp0TJqWQI4+JJKTgtYjm55leqdOGWcdcbs40w0mWGu4753FyqiaNuNt0G1Q4LRaGKXAojov7p16jV.pNZdY0BJ+ItO.BjB

            1 Reply Last reply Reply Quote 0
            • CatABCC
              CatABC @Mwins
              last edited by

              @Mwins This is not an intermittent occurrence. If you remove a plugin once and do not completely shut down the DAW, this problem will occur when you load the plugin again.

              This problem does not seem to have been resolved yet
              https://forum.hise.audio/topic/10212/drag-and-drop-midi-functionality-does-not-work-after-reloading-plugins/11?_=1729782136374

              //I am a new student at HISE._
              //Windows11 & MacOS Ventura 13.6.7_

              M 1 Reply Last reply Reply Quote 0
              • M
                Mwins @CatABC
                last edited by Mwins

                @CatABC Yes that's precisely what happens. Maybe we'll get a patch for this or some kind of solution. It happens if you delete the compiled plugin and pull up another instance. It basically causes you to have to restart the entire DAW to get the midi panels to display. Pulling up another instance wont bring it back. I'm not sure if it has to do with referencing the same MIDI player from two separate panels or if its the Midi panel display in general.

                1 Reply Last reply Reply Quote 0
                • Matt_SFM
                  Matt_SF
                  last edited by

                  I'm reviving this topic because I'm facing the same issue.
                  (Tested in multiple DAWs, on Mac and PC - develop latest commit)

                  After loading the plugin in a blank project: the tile is correctly displayed.
                  When loading a saved project in the DAW - without quitting and reloading the DAW : the tile disappears
                  When quitting and reloading the DAW, and reloading the saved project : the tile is correctly displayed.


                  I'm using a MidiOverlayPanel to allow the user to drag MIDI into the DAW.

                  The floating tile follows the mouse when a user hovers over the MIDI files (painted in a panel). When doing so, the panel loads the corresponding MIDI file in the MIDI file player during the mouse CB, so when the user clicks the tile, he can drag it into the DAW.

                  8375bbf5-6fd8-4338-a44f-010a71ab4486-image.png

                  I'm explaining all this because I made a function to track what the tile is doing.
                  The tile is still there, placed where it should be, and the MIDI files are correctly loaded into the MIDI player (so no problem here). If I hover where the tile should be, I can see that the panel is no longer hovered - so there's something invisible there - but it's impossible to click and drag the tile. So the tile is still there but I can't interact with it.

                  @Christoph-Hart it seems to be not related to what I'm doing with the MidiOverlayPanel floating tile, so the snippet above can be used to reproduce the issue.

                  Develop branch
                  Win10 & VS17 / Ventura & Xcode 14. 3

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

                  18

                  Online

                  1.7k

                  Users

                  11.8k

                  Topics

                  102.4k

                  Posts