@d-healey I'm building the working one again just to check my sanity.

UPDATE: It works. Somehow, lol.

@d-healey
Ok, then I'll add it to the bug reports.
Thanks to you, David!

@orange
I haven't tried it yet. I'm more interested in the fact that the user doesn't have to download a 14GB file...

Last week, while working on a project for custom logo design services, I faced a challenge with the plugin's UI interface. It was crucial to detect whether it was open or closed. I implemented a solution using broadcasters and listeners to bypass certain code when the UI was closed. This not only streamlined the process but also indirectly optimized my workflow, allowing me to focus more on delivering creative designs to my clients.

@Lindon Thank you for your reply. I can go back and forth between them, or repeat the same — the results are identical — if I add the text, I get one result; if I remove it, I get a different. Weird, huh?

@Christoph-Hart Bump 🤗

@d-healey Ah.. thank you. It worked when I put a script processor after the swapper.

@d-healey

Thank you, really useful

@orange the jdsp version was fine actually

Mee too :)

alt text

@CyberGen fortuitously discovered that setting the ignoreNoteOn to 1 acts as a reset signal. Whenever triggered, the LFO goes back to the start of it's cycle without having to play a note. You might sometimes need to set it back to 0 immediately (depending on what's required of the LFO) but it's a good workaround. :clinking_beer_mugs:

@d-healey
David, you are always so helpful! Thank you so much! :-)

I've solved it setting the bias knobs of the Shape Fx to 0.0

@Christoph-Hart Thank you for your reply. I actually like that the plugin doesn't teleport somewhere…I've just seen that message 120x already. 🤪 @d-healey 🤣

@aaronventure you can easily do this as local change to find out what's happening:

Just search for the string in the HISE codebase and replace the line with

Logger::writeToLog ("!! killing thread by force !!" + getThreadName());

@d-healey
Great, that worked. Thanks as always David! :-)

@Christoph-Hart Feel free is skip over the rest of this reply since I don't think I'll ever come to terms with this 😜

However, that's exactly my fundamental disconnect with this - I don't get why all other elements have "a predefined amount of sub elements" while the knob doesn't?

The stock HISE knob has a predefined amount of sub elements, and two of those elements are the name and the value. So why can't we address all those stock elements with CSS?

I totally get the 'one more lane' reasoning and that's why I'm only talking about the stock decisions you've already made with the knob control.

Let us style what's already there in the stock control with CSS, anything else we have to go full LAF.

@Christoph-Hart Thank you very much.