@whoopsydoodle Currently the only way to use a scroll wheel in a custom control is to use a WebView. Use it for your EQ panel.

@goldee Yes you can do this with HISE

@Allen said in Please Increase parameter limit on Scriptnode custom nodes!:

I just found out one of my node with about 100 parameters won't update the internal value and ready to increase this limit to 256

Haven't tested all the params but just wanna comfirm so far it works in both script fx and compiled fx with max 256 params limit! :)

I found there's also a similar param number limit in the rnbo node so don't forget to change that one as well if you're using a rnbo node

@Morphoice if you want a more detailed error message try opening the generated AutogeneratedProject.jucer file from the DSP Networks Binaries Folder.

You can then compile this file as you would compile HISE in VSCode or XCode. This usually yields the correct error message.

@griffinboy i suspect that implementation will just be a stretching of the path across a different area, haha.

For multiple channels, you'll probably find it easier to do using the new Rectangle() object.

@Sawatakashi if standalone inputs were possible, I see how you could ship a standalone HISE app to an embedded Linux device and pack it all into a pedal or a rack device.

@d-healey Amazing! Thanks :) I posted this before realizing they didn't work in expansions. But maybe that can be fixed

@d-healey Alright that's fixed - that logic is a bit convoluted because as soon as something is not zero based (like the old RR group values were) it breaks my brain, but you can thank that deficiency of mine for not having to write Lua all day.

Free mankini with every commercial license???

@aaronventure It shouldn't be limited to 16, but there's still a bug with the number of sliders an ExternalSliderPack can handle.
This might be of interest to you: https://forum.hise.audio/topic/11411/externaldata-sliderpack-seems-to-be-limited-to-128/13?_=1743103883757

@aaronventure I requested a proper bug tracker a couple of times, something like Mantis. It would prevent bugs being lost in the ether of the forum, or being lonely on github.

@Christoph-Hart Nice, going to give this a try now.

@clevername27 said in [feature request] Stop specific broadcasters firing at on init:
It's also not always possible to tell if a broadcaster is being called at startup…which doesn't sound right, but there are edge-cases.

Can you make an example?

@d-healey

Proposes the feature. Documents the feature. Codes the feature.

Because that's how @d-healey rolls.