Topics created 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.

@Soundavid this works incredibly well, thanks for sharing

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

@iamlamprey I saw that post. Nice! That trick works in certain DAWs but it still doesn't work in Logic, Studio One or Reason. I got it to work on a windows version of FL studio. It wont work on the mac version...

Thanks though... Still Progress!

@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 I've solved the first issue and added 8, 12, and 16 bar options. I'll make a pull request later.

For the second issue it seems there isn't a TempoListener in the AudioLooper class. I tried adding getMainController()->addTempoListener(this); but I get an instant crash when adding a loop player. Any suggestions?

Here's a scripted workaround:

const alp = Synth.getChildSynth("audioLoopPlayer0"); const th = Engine.createTransportHandler(); th.setOnTempoChange(false, function(x) { var syncMode = alp.getAttribute(alp.SyncMode); alp.setAttribute(alp.SyncMode, syncMode); });

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

@ulrik I didn't pay attention to 2. but the one I use is simply called the midi player in the midi part of the containers. the one where there is the drag n drop, choice of sequence, play stop rec.

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

Awesome! Thanks for the help fellas.

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