A better question is that how can Hise have the same Build and Version number, yet have completely different results? I figured we would build the latest and greatest this week to make sure all bugs were gone and the new version actually lost the feature that the May build had correct.

@christoph-hart It's called intuition and don't try to understand it :)

@jadg said in A question about getCurrentLevel()...:

@christoph-hart
Thank you very much for your explanation.

I´ll pass this switch in my proyect settings.

All peak meters are working now !!!!
Thanks again

alt text

@remarkablex I see - I guess I got confused because this doesn't seem to be required in VST instruments.

After adding another routing matrix and doing so, everything works out like it should. Thanks for the explanation.

@ulrik said in Create script variable declaration for Sampler:

@d-healey Ok, I'll fix it with more samplers, thank you!

or even better, with split one incoming note and trigger 3 instead :) the Synth.playNote() you tought me :)

@christoph-hart cool! The thing is same happens with AU or VST plugins. Not user friendly for final users

@d-healey I compiled yesterday following your video(with suitable changes for VS 2017 and the slightly different layout in projucer) with no problems...

@macromachines Yes

Yeah, getting the keyboard focus right is incredibly annoying (especially when also dealing with text input things like code editors, etc). I wouldn't count on it being fixed in the foreseeable future...

You know that 8 channels are stereo so you get 16 channels for multimics. What do you need more for? I never needed more than 8 stereo channels except for weird "hyper-surround" kind of experiments.

@christoph-hart Hi again, now it builds, thank you! :)

@christoph-hart Yippie! Thank you, I will give it a spin

I've just experienced this as well.

@christoph-hart Any progress with this? :)

ok thanks

Its Working now! YES!, i need to click several time to continue in the debugger...

Ah damn, I should have branched it until things are smooth.

Oops, I've missed that. If the configuration file couldn't be found, it crashed the dialogue. I have fixed that, however I still need to tidy up a few things there so expect a few other glitches...

Hmm, unfortunately the crash report is still stripped so either this didn't work or Logic didn't clean the cache (BTW Logic is the worst when it comes to developing because it constantly uses older versions of the plugin or stops loading the plugin for no reason if you don't increment the version number with each build).

The debug version is much bigger (and MUCH slower) because it is not optimised and contains all symbols.