@Christoph-Hart
Unfortunately not. I just tried it with a new project and it's not being applied.

@d-healey
Okay, I'll try that too. Thanks. :-)

@Christoph-Hart
Great to hear that! 😊

@ustk
Ah, I hadn't thought of that. Much better solution! Thanks! 😀

@ustk
Great, I didn't think of that. Thank you very much! :-)

@d-healey That wasn't my experience at all. Search the internet for "GPT5 fails" and you'll see all the negative reactions.

In my case it was very slow, showed way too much 'thinking' text, refused to execute terminal commands and had a much higher hallucination rate than previous GPT versions or Claude.

Keep in mind, this wasn't with HISE. This was mainly in a Ruby on Rails app with ~30k LOC and a bunch of other much smaller projects. I haven't used AI for HISE at all yet, mainly because I don't think there's enough HISE code out there for it to give really useful answers.

For casual stuff it might be fine, but for coding - and in particular in the Cursor IDE, it was horrible.

@Christoph-Hart
Great! Thanks for the snippet! :-)

@Christoph-Hart
Okay, I got it. I had to name the Matrix Modulator according to the matrixTargetId of my slider. Then it works...

@Christoph-Hart
If I don't connect the “value” parameter of the Matrix Modulator via the ‘processorId’ and “parameterId” of the Property Editor, but instead control the value via the callback function of the slider, is the modulation still sample accurate and polyphonic, or do I have to establish the connection via the Property Editor?

@Christoph-Hart
All right. Thanks for the explanation! :-)

@Christoph-Hart
Thank you! :-)

@d-healey
I got it. Thank you! :-)

@d-healey
Yes, that's a great topic for a video! If I had known this earlier, it would have saved me a lot of time and programming effort.

@Oli-Ullmann said in Maximum number of sliders in SliderPack:

Why do you ask?

Just curious 😀