Midi Browser and drag'n'drop midi to DAW...Drum Plugins without these features are completely doomed!

Drag to DAW is possible now using the MidiDropper. You can build a browser yourself with Viewports.

@lalalandsynth Sorry for been late to answer...I just now entered in the forum!
In order to have a mono functionality use only one LevelMeter...
Delete ''LevelMeterR'' and rename "LevelMeterL" to "LevelMeter"
Very correctly as @Lindon said ...sum the Left and Right values and divide them by 2...

Use this snippet

HiseSnippet 1611.3oc4Y0saaaCEVJNZHwcYqcnCXWRTzKb1ZSrS+YannKNw+T3sjZiXu1kcSJiDsMWjHEjnSSVP.1qQuauF6t7nrGg9FrcHojEsqiqgQawxp.BfIO+vuyGO7viTZEwcIww7HK6k6bZHwx9ScZeJSzuReLkY0npk80c1gbLweWhfD0gDKr19zPbbLwyx1N2SjZYu7hVpmWu41XeLykjMkk0y3TWxNz.pHa1Vk+IpuecrGoCMvP66WtgKmUg6yG.HJmSQqPr6Q3djmhkpsfik8mTyiJ3QsEXAI1xdws4dm1tO+kLs9OiFSOzmHGTxpM3H8z049dRDKm0pRepuWqzHO1xx1oUFOjSyC2zYWpGc37l7gT.JyBS9vdgoAuRlvq3rCOaC3snFd2vosaDMTjIQhsq4zfAaScwvVfIrz5Zsvm63TgCZvDqEfOhTOBFLzhBOrXw6fdPwhq9nUxuRdXiHVfNFGgx1+QOFkZeOhnBOHjyfAEtUlJ25xsdGt6QyfGjp8FdoElcolBxdC8aSCB8IxzyRfcpTZoU051k3BlXHNwz0WuJwEeJZOXiyzQUqUYq8OXus5TC7Sw0996knckAQQvpidF1e.Idk7RccGDoBCklESTTlgGgpf88ODxkMcs.zqFqGkQVyMh.qqR0lG9aRHJQkXsXhPMYp4E5Nf4JnbVgUWI+YR2qBsgn.kQ4fyKXDlJNSiYk3BkV8all3hqtJZczFOBgjdU+25q2hfOBYtjZQxEMDDktv6hA5N.eRA0D2QCHYDoUGgncQExL3GFxbqpEiPmk9CjIqNzjGkJ9b8OH9wjoY5W+XiMxwMV9H2qzgHjFPODLAx0NlDECbsd969t7AoIhz3JIK.1CRV8357H49RcrKTMovP5QucXtizlHL1JdGCSIPGhS0gSYFoZ4JXBnj+NWeTBRaE3Hchag6AkSRSZQb1S4BRSH6M+Y4WN+44QiKpa2IJSdvOh66CNbRh0K0TLr.aPvgjn6.Yp.1GpHTNcz50NWd8ZyqSb00gLTjyZvnhlgD1kUE2Jo3ETOOWBpfeITUy+rjp4s8odjHKpm7d3LR2Rg5rqI2+BqYvClWbKqoNtWd8lyhWbbfxqiaJ77yMphEX4kSIwEDqgjHAURi1UIGC25qupZYmpj3iD7PUfmT0Ff2rE5mX1cvoYCtc4tT+fXAXai.nCAKajyYs1q4OVqRmCp2bmp016biz1PVOKHGnsT+3gd4hes7Kodh9Yt85k6Sn85m0qxKdQ4.ydb1+BntlISDKHgso+dJ67mu5U+0lwC51kdhj7PdaaEP877Is3wTYRoQ7bgGoKdfu9.k4RDCIVcHmH1lehNgKf6kvjpxCxjogD4RydFfAvKMcx71SgLkt5RHTHoZLBciIPnlnO+aIyy.xMMf7eTsbX5gqFfxq3XbYFz0XDzvH.UonkcR6JcZaj6WVyw5U8x1xj8t9F8hAcDx8F3iEi1lnDJIBj9vreLYOWLv2mZRbuW5cbVg6MbZQEt8mLdWXB3EN4+9FuIchuhitqsLvtnS8e4Cba2KM7siFllofxn4cW9qFYYUk3iGg+d9nGT1u7Dd4oFxdPDs393nwY+biFx4lsatlPXt3LmhHCIzUlT5uvQQ4Wk.rJk3pCfutrV4+Af6d7ABJqG7VGQpaceJbuDePjKAfJiAcSCyYufrEL83hxwR.0lv7TC9G3IQXI4X6DgkREZRI2TSIWy443iIpWFRwFeoZbWdT.5IDFIRxUkdW70RBm4uVRSWA.gNQXVbHOlTxzyiIaiQqMIFvFUc8TinkL7f2KIvPukJmN4FlSBoEi3LX7HdZWpwMu+8l0XXXSuMAhFulwtPvJ4NSlp0.3E7TmNJYZX1zaXN830FWb1pMdk9iD8gqujbyFbeKWntbJF02eVCtnyGdAhgUtUMFmN6nGi1ky3g84LpqYN0dD3zeudjQxalX.skPfglgGNyMKuGwmfiIlMDuC7B43nc08cOObQoYmKl190W4ngKRd1G8+i9Iy8QY+jy9ITn73GI2p9gXMBvtQ7Cb0epC4QukTy.wMS8eUXYmckiQkR+JGNNEWqn7U.oG35JyNtKvOS1lMlCat2bXy8mCadvbXyCmCa914vluap1Hu6bqABdfN+GlnUM0Wax1V2pf5nf0+h9zF.s

And as @Natanr said very correctly if you will not use an invisible image like "levelMeterLock" on top of the LevelMeter you will have problems with Mouse Click / Drags.

@Natanr Try this...I send you a small test project with a filmstrip (107 frames) connected to a Simple Gain Module LevelMeterTest.zip

Then you can replace the filmstrip image with your's and adjust the code and number of frames according to your filmstrip image

@gorangrooves Great Job man!...I wish the best with your instruments and your Libraries.

@marcLab Hi.
You can add a lot more than 16 channels without problem.
I work with 64 channels in my project and there is not any problem.
Just follow the link that Dave posted above and recompile Hise.

@MikeB We Wait for the guru to make his magic...crossed fingers.

@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

Congrats man! Great work!

@d-healey Exactly...it is exactly as you said...this is the only way to have a louder result using saturation(of course very carefuly...we dont want much saturation)...the higher peaks of the sound will be altered on a tranparent way (not as compression acts) so we will have finaly in the middle area (and this is the real acoustic area that is perceived by human ears) clearly more volume.

For example you listen to the same track that is mixed by 2 different but lets say good producers

The one of them used no compression and no saturation and made a good mix
The other made the same good mix but used a combination of saturation and compression but not only globally on the Master channel (imagine that every different track needs different approatch)

Finally we have 2 finished tracks both play at 0db but the second is about 6 dbs louder (i am talking now as a producer that i have seen that hundrends of times)...
Final conlusion...if you will not saturate or compress or the better of the 2 worlds both you will never be loud enough as the other senario...

If you dont care about the volume it's perfectly ok
If you care it is one way.

@Lunacy-Audio Hi bro!
It is almost impossible to have the final volume as you describe (like Omnisphere for example) (if you will not use some techniques...as compression and/or saturation or both before importing to Hise or any other sampler) and as @d-healey said all the plugins have the same output volume (0db is for everyone)......but.....
same number (lets say 0 db is not same volume...i can send you now the same file where the only difference is that i used a gentle saturation on one of them and you will hear exactly the same sound they will be both 0db but one of them (SLIGHTLY SATURATED) plays clearly louder (about 4db louder)

NON SATURATED.wav
SLIGHTLY SATURATED.wav

So for Omnisphere and any other plugin that plays loud for sure these techniques were used before importing the final samples in the sampler... Trust me there is no other way to achieve this...ok you can use the Limiter of your plugin to achieve the volume but it is a post prossesing action and it does not have the same transparent final result as a clever saturation senario

Listen to these 2 files i send you and you will understand what i say...and i have to mention that this initial file was already treated the way i describe so if i used for an example a raw uncompressed and unsaturated file the difference would be even greater.

@gorangrooves Great Job man!...I wish the best with your instruments and your Libraries.

@Jay Nice Job man!...I wish you the best.

@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.

@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-daws

If 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

@Christoph-Hart This way seems to be better than mine...is it easy to have a small example as starting point so we can work it out?

@dustbro Hi...You mean that the user can use his own midi files?(That they are not embeded in the plugin?)...Lets say from another location where he can add or remove midi files?

If it's the case one way to achieve this is to create an expansion(lets say you name it "UserMidi" or anything else and the user can add or remove files from the respected folder.(This folder will be in ...User Library/Application Support/Company Name/Plugin Name/Expansions/Expansion Name/MIDIFiles).

Using a Viewport the user can see the midi files and load any of them in the midi player.
Add a play/stop button to control playback and maybe a floating tile(midi overlay panel) for drag to DAW

If the user adds or delete files from this folder the list will be updated on next load of the plugin.

If this is what you are going for and i did not misunderstood i can make a small snippet for you.

@dustbro They will not work from the Property editor...
Did you read the post that i mentioned above?
You will find a lot of answers there...and load my snippet and test it in your system...you will see that most of the functionality is there and working ok and finaly you will come to the most serious problem that i mention in that post above (the crashing senario) but strangely noone (of the users here not even @Christoph-Hart) was interested about...and in some point anyone who is using a midi overlay panel (for drag to daw or any other functionality) will face it.

The part of the code that controls play and stop is that below...

//The callback to control playback of the loaded midi file
inline function onPlayControl(component, value)
{    
    var position = Engine.getPlayHead().ppqPosition;
    var last = Engine.getPlayHead().ppqPositionOfLastBarStart;
    var currentposition = (position - last)/4;  
    
    if (Play.getValue())        
       {
         Player.play(0);
         Player.setPlaybackPosition(currentposition);
       }
	else
	   Player.stop(0);
};

Content.getComponent("Play").setControlCallback(onPlayControl);

@dustbro Play, Stop, getTimeSignature and Drag to DAW works but there are some problems...see this post and if you have the time test the snippet in your system...this way we will be sure if it is a Midi Overlay bug or not
https://forum.hise.audio/topic/4656/midi-overlay-panels-in-compiled-plugin-crashing-daws

About Drag To DAW it works ok but there are 2 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)

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?

@marcLab Hi.
You can add a lot more than 16 channels without problem.
I work with 64 channels in my project and there is not any problem.
Just follow the link that Dave posted above and recompile Hise.

@DimitrisSP Bump bump.
Did anyone has test it? If it is finaly a bug it will affect anyone who uses midi files in his plugin and wants to have the functionality of Drag to DAW or any other Midi Overlay functionality.

@Christoph-Hart please take a look at the problem...if it's finaly a bug it tends to be a very serious problem for this kind of plugins.