Best posts made by Mwins

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.