yeah if you could put some example code for the output meter using a vu meter filmstrip that would be great ive been pulling out my hair the last two days trying to get it to work lol. as far as the compressor i wish i knew the exact coding process to birng dsp code into hise there are tons of great things at musicdsp.org

I recently changed this so that you can call this in the onControl callback which is required when you want to create modulators dynamically, so no it shouldn't cause any problems.

I think you can't do it in the MIDI callbacks though (and it would be pretty stupid to do so), but I'll have to update the API docs.

No rush, I'm only using it as a sub-modulator and restoring the parent modulator restores the note number modulator correctly

I also had this idea in mind (that's precisely what the company URL field in the User Settings dialogue is for). I think the best way for this is adding an About page floating tile, which also shows the registered e-mail address of the user along with some other useful information.

Yeah that makes sense, duly noted!

*facepalm ;)

CCs that are assigned will not be passed to the engine in order to avoid side effects, but the onControl callback should be executed (so you need to call repaint() from there).

That's a good idea, and it will offer a working example too. I shall do it that way.

I see, I thought it wasn't there because it's not showing up in my API list

0_1503830264859_Capture.PNG

Thanks Christoph, mystery solved :)

Yes, this is possible, but highly complex and subject of many proprietary algorithms. The problem is to resynthesise the samples without loosing the sonic quality.

OK, I admit the for loop thing was one bit too much, so I reverted this :)

You can still use the standard for(i = 0... syntax...

Good idea. I sometimes make use of undefined so maybe void would be suitable in those situations.

Thank you

Thank you!

I can't reproduce this crash with the latest versions, and it's impossible to fish in the dark with issues like this (I assume it's still the deadlock, but please hook up the debugger to confirm this).

I've made some tiny changes that decreases the duration that the locks are held, maybe this fixes something.

Ah yes I think I have hardcoded bipolarity to the SliderPack as soon as you're crossing zero (as I thought that in 99% of all cases this will be symmetric around zero). I'll think of something.

Well the panels you can find in the HISE editor are not supposed to be embedded into a scripting interface. However I could add the frequency plot as script widget which would allow you to build a interface for the EQ around it.

Well, they are using the order for the channel routing so a leading zero might things clear up. Apart from that the mapping seems fine.

Also I would recommend using 7 stereo files instead of 14 mono files. It decreases the loading times and improves the streaming performance because HLAC stores stereo samples with alternating blocks of 4096 samples so it has not to jump around the files (and I can imagine that streaming could become the bottleneck here considering the amount of channels).