A working drag and drop MIDI feature would be great! I see the progress in the develop branch which is great but it's still not dropping the midi file.

@d-healey I ended up finding a previous version I backed up that wasn't too far off from where I was. It's a pain in the ass to have to redo but I'm going to bite the bullet and do it. If it happens again, I'll send it over.

Thanks again :flexed_biceps:

@d-healey, Thanks D, I looked into that but couldn't quite get it to work but it lead me to some other string functions such as replace which ended up being exactly what I was looking for. For anybody looking for an answer to this thread, I ended up using

const var oldstr = "{PROJECT_FOLDER}";
const var newstr = "";

.replace(oldstr, newstr)

@Christoph-Hart said in Midi FX Export Arp Pattern - Drag n Drop:

The MIDI player has the drag to DAW functionality, but the Arp's notes are just generated internally, so there's nothing to export.

Can you give a brief explanation of how this is done? I'm not worried about the arp notes but the MIDI Player drag to DAW... How can one implement this?

@DanH Big thanks my friend... saved the day! That worked.

Hey Guys. Just wondering if anybody knows how to bind the MIDI sequences from a midi player into a combo box or create some sort of browser for the MIDI files/sequences that are loaded into the MIDI Player. Can't seem to find a clear way to do this from the API.

@Lindon Thanks Lindon. You are correct and I was able to find a post that helped me solve the problem... however, for anybody seeing this post, the VST SDK folders have to be rigged a bit to get it to work if you are getting this error.

See @dustbro post here: https://forum.hise.audio/topic/1444/vst-export-failed/82

that solved it for me!

@d-healey Sorry that was an old image from the Hise-master export but the error is the same with the Hise-scriptnode.

Yes! That worked. I appreciate the quick response too.

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

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

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.

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?

I am hoping to get some help as I have not seen this topic anywhere on the forum and I do not know where else to turn.

When I export my plugin with a MIDI player and 2 floating tiles referencing that one player: (One for viewing the MIDI (midiviewer) and one for Drag and drop), the displays don't always load. Sometimes it does and sometimes it wont. When it doesn't load, opening a new instance won't fix it. I usually have to restart the DAW to get it to load up. The play button will still play the file but I can't see the midi or drag and drop the midi because the floating tiles connected to it failed to load properly. Big issue for the user.

What could be happening here? I have a typed reference to the MIDI player near the bottom of the code. Should I always pre-load a midi file or something so that it is guaranteed to load up? I tried placing the reference to the MIDI player at the top.. it still happens.

Also, I am creating MIDI data in hise but the bar tick lengths are off in the exported plugin. In hise, I had to set the bar tick length to 96000 to get MIDI files that are correctly on time when imported to any DAW. However, when the plugin is exported, the times are off and my loop cuts off short, plus, all the timing in the loop before it cuts off is incorrect. What do I do to sync the times and code it properly within Hise? The midi files generate perfectly and export exactly as they should within hise no matter the tempo. When the plugin is exported, its all off.

I am hoping this is not uncharted MIDI player territory and someone knows about this already...

"I'm able to create multiple audio outs for a plugin, and the daws will see them so that I'm able to route the audio outs to different tracks/channels in the mixer."

@ulrik im just curious to know how you would go about doing this. Do you have a snippet or snapshot that you can share? I'm working on a multi-out drum project and can't seem to figure this out at the moment. I'm trying to get the audio on each of my audio players to route to a different channel in the DAW. Would be a big help.

@orange Yes. It is a delay and it has IR samples in a reverb. @Soundavid I'm Using the latest develop branch just before this last update released a few days ago. The static seems to be happening on the delayed signal.

Weird discovery: if I turn the feedback on the delay to 0 on both left and right channels, the static actually goes away... It has to stay on zero or its right back

@Matt_SF said in Delay Effect Produces Static In Compiled FX Plugin. Need Help!:

@Mwins hard to tell without taking a look at you project. The delay effect works fine, the noise is probably coming from something in your project.
Try to build a plugin with only the delay module and see if the noise is still here.

So I just compiled a fresh plugin with nothing other than a delay in it and I am still getting the same static. I'm using the same cpu I load hundreds of other plugins through with no issue so I know its not my setup. I'm thinking its either a setting or a bug. I haven't messed with the plugin settings at all.

HiseSnippet 953.3ocuV0raaaDDdWYQ2HmeZSPPQOJTfB3.jFHYmlVfbvL1xpUH1NBgNA8VvZxgVKzxcYHWlX1hBzi8Vek56P.549Hz2f1YHkHoiUsUEZpNHv4OteyOeyxwIFeHM0jv3cNNOFX7a33kqsS1ahPpYiFv3ejy.PIxY6lGKRSg.Fmu12RF4cZyJ98m6rqPIz9PsJF6kFoObfLRZq0N18oRkZnH.NVF0v6G5Nx2n2ynLYHPVyoGKV3OUbJbjfbqkCiu99ARqIwyJrPJ5ytlfbuIl2pK8+kxT4IJfD5y7vWToZ1dSjpfwySxTFi2dbcJuVYJeWmCkAxJ80o9mTXnacDMqA7VWFj5+u.R7FPpcIjtsimehL1Vagvy0cFosPRn.K0MgRouL9u4rmAcPaePjXJLLAEpBXyG0q286h+cuGGlo8sRitqQejwBOSu4813G2nyF+zFceeSggKzFcLIFkBRVnYp6lbYAtoNK5DH49ceiPkAUNho+4qoqub0T+xrtgiF8Hsz9rXXl7PiJfpUzyWrCvlU1vdQqYHDc0VzIt0rNgmRF.ILY.wHdp1bReVA3aNyyV5f2ZAA+hQCDVAMOLCNHDigDqjpD7AvaPBU4zQGjRlN0ZhKvaTrQSfmeyqDwmw3N7eEOqb5geGeH0lS0y0KbfEICBTvXSpj5W0n6ycSsPrm7Gflr9HwY0ha4FJUQoV7jGEgTWF+NNuHE5F.ghLksa5TjToj5oPvwlBNc77NvHDgWqbKSej4mfjdbnkz9wkZo4oCfPKKxD.DM3X.SZbOkOUxqx+abkE8Z75l4lWI7yScWt5verSZVXn7LZP5KXe.R3a4LDffSvseMx2O04HSRjPgk+fwPhOlrz4wt3ZCbgkIHSIrmeKFstdlAJcZt5f1OnwzLuYi88Ws09elF1qAM7JHYKIbusyXo0exhwaqEfWh09AFuytn3lN6GFB91Zv11Y32eo2Jzd41fUCkq7FhqWhk4WKSnnZVpIRNOyopZ8YtUFdt7zIMrbW2yM6Up2c6se2Ny02LfBCGXd6X7.Gl.ut587Kuy86jWPKaf6gxyZxjp4vMm7V6+nKUYO2jYk5SOTfDTZs2QYQd3mW3CXySqAUJsArEsytTtGISfvCzAEB+E9alw9jLelw9yM9+xYDI7SLuxu7hEZV3ZEZv7VW7wQcbNjj6VccjiSuGzi1fIekuOMg9k3z8hiYqUHlsWgXd3JDyWsBw7nUHludEh4atzXnuY7IYVST41KTw38KtYmy2WKvo2B5I6u0RlKHM

@Matt_SF thanks, that's a good thought, trying that now. Lets see.

In Hise, the delay effect works perfectly as an effect either on an instrument or as an effect. When I compile the plugin as an Effect plugin (there are no audio modules at all in the plugin), the Delay effect produces static and is ultimately unusable.

1. I do not know how to create a scriptnode delay such as the one Hise comes with

2. I have already built a quite intricate plugin using the standard delay and I am beyond my deadline for my client.

Has anybody run across a fix for using the Hise Delay in a compiled Effect plugin? I really need a save here :anxious_face_with_sweat: