Yes, I don't think that anyone that starts thinking about customizing it's UI in anyway is using the default knobs :)

The filter IDs are not subsequent because it would prevent me from adding new filters without breaking backwards compatibility. That's why the FilterModeList object is there. Basically you create a custom array containing all filters you need and add get the correct filter ID via this code:

const var modes = Engine.getFilterModeList(); const var myFunkyFilters = [modes.LowPass, modes.StateVariableNotch]; comboBox.addItem("LowPass"); comboBox.addItem("Notch Funky Yeah"); inline function onComboBoxControl(component, value) { local filterIndex = value - 1; filter.setAttribute(filter.Mode, myFunkyFilters[filterIndex]); }

Protip: If you type modes. and press Escape you get a dropdown with all filter modes available.

@christoph-hart Yey, going to build now!

@christoph-hart Wonderful, seems to be working fine now.

@christoph-hart Excellent!

@christoph-hart I will report all glitches I find :)

Fixed in the develop branch

@christoph-hart Thanks, downloading now!

Coming back to sliders again as I start to finalise my instrument. Disabling the show text option still leaves the border around the slider.

So I used the method where a hidden slider is placed over a panel, however It still provides the ability for the user to enter values via shift+click (even with show text disabled) which I would like to disable on my vertical sliders.

There still doesn't seem to be a way to restore the basic slider control to its default value when the show text option is enabled.

I could just use a custom slider/panel but then I lose the nice value popup feature. Another option I'm going to try is putting a custom panel over a slider control which I think will allow me to do what I want and still have the value popup the downside to this is I have 8 sliders I want to setup in this way which means 16 controls and some extra code and the whole thing feels untidy.

Update: I managed to get the slider controlling the knob but unfortunately it loses the value popup (I assume this muse be part of the mouse callback of the knob itself).

i figured out the issue after all the others was asio4all. finally upgraded

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.