Drag and Drop MIDI (Develop Branch)
-
@MikeB @Christoph-Hart Confirmed in my end also...i tried with Hise Standalone, Hise plugin and through compiled Vst and Au plugin with no luck
I am also on Mojave 10.14.6
-
@DimitrisSP Let's see what Christoph finds out.
-
@MikeB We Wait for the guru to make his magic...crossed fingers.
-
Yeah... erm, ... magic:
- fixed MIDI file drag and drop not working · christophhart/HISE@cded98d
The open source framework for sample based instruments - - fixed MIDI file drag and drop not working · christophhart/HISE@cded98d
GitHub (github.com)
-
@Christoph-Hart
Do you think about zoom 100% with keyboard shortcut comand/strg 0?
Thank you
-
@Christoph-Hart Yes....Yes....Yesssss.....Master....You are a living Legend :flexed_biceps:
It works on the Hise plugin, and to the exported Au and Vst plugins...
Confirmed in Logic Pro x, Cubase, Reaper and Studio One.
But there are 2 small problems....
1) If you load a midi and drag n drop to any daw it works like a charm...but if you load another midi after that(or try to drag n drop the same midi for second time) it does not work...I noticed that if you close the interface from the edit button of the daw and load again the instrument you can drag n drop again any loaded midi file...and that story goes on...Or if you try it from Hise plugin in any daw the same thing happens...you can drag n drop any loaded midi file but in order to drag again a second midi file you have to close and open again the (interface preview, or Hit compile and it works...and so on)It looks to me (Without been sure) like it is not deleting the temp midi file and it stucks there but when the inerface opens again or you hit compile it is refreshed and probably the temp file is deleted.
2) The midi file that is created and dropped to daw is named as temp...
Is there a way to have the name of the actual midi file that was loaded? -
@DimitrisSP Yes this is exactly the problem I am having, it's a major inconvenience if you have multiple midi files in the plugin. However, If you reload the plugin, the drag/drop resets and everything works again. Is there a way to reset the plugin or initialize the engine via scripting @Christoph-Hart ?
Right now we are basically limited to one single drag and drop action per plugin instance. It only allows for the drag to take place once... Is there any workaround?
-
@Mwins Exactly...I looked further in that situation because my instrument depends a lot on that functionality (Acoustic Drums with about 2000 midi files/performances) and the worst is that i found that i have crashes...
See this topic...https://forum.hise.audio/topic/4656/midi-overlay-panels-in-compiled-plugin-crashing-dawsIf it is easy for you please check if you have also the same crashes...or maybe it is a problem in my system?
In this way we should confirm if it is a Hise bug or not.
If it is a Hise bug it has to be fixed...otherwise it is a dead end for anyone who uses a midi overlay panel for drag n drop or any other functionality in his plugin -
@DimitrisSP Yep, I get the same crash in Logic Pro X. It is intermittent and usually happens a time or two after the plugin has been freshly installed or recognized by Logic. This crash has been happening for a while when you use more than one midi overlay for the same midi player (I'm not certain and I have not tested this theory but it seems so)
-
@Mwins Here in my system it happens even if i use only one midi overlay...i think something is going on with the source code of midi overlay.
