@d-healey
I see, where I was wrong...
I needed to set them to false and not delete them...LOL

@DanH friendly bump

Alright, this is making me crazy, so I take a deep breath and try to simplify manually...

$TIME = dechex(1673481600000); /* Today in ms */ $EXPIRY = dechex(1676160000000); /* Expiry in ms ($TIME + 30 days) */ /* For the encodedTimeString */ $data['encodedTimeString'] = "0x" . applyToValue($TIME, $private_keys['private_key_part1'], $private_keys['private_key_part2']); /* For the XML containing the $EXPIRY (among the other things) */ $root->setAttribute("expiryTime", $EXPIRY); $root->setAttribute("expiring_mach", $MACHINE); $ENCRYPTED_XML = "#" . applyToValue($XML_STRING, $private_keys['private_key_part1'], $private_keys['private_key_part2']);

Result from unlocker.checkExpirationData(encodedTimeString) => Unlocked with19400 days remaining

I'm just lost...

@Christoph-Hart I've read someone got the juce unlocker hacked by brute force of the key which I thought to be near impossible. So they moved to a 2048bit key.
My thought is that if the only thing they could do is a brute force, that means the binary is secure enough.
Any thought about this key length?

@ulrik OK>.. Great.. Thank you (y)

@Dan-Korneff Thanks for the quick reply and was just coming back to report the same thing.

I ran a test build and was surprised when it actually worked. Looks like I needed to rebuild the script as you suggested.

@orange Hmmm.... Exactly.

@Matt_SF Yes all of the properties are the same.
Threshold knob is connected to the converter node (dBtoGain mode)

@d-healey actually I thin k I have a solution - just do the same thing in reverse using Synth.addNoteOff

for (n=0; n < ChordPlayer.playingEvents[pos].length; n++) { Synth.addNoteOff(1, ChordPlayer.chordPadArray[pos].data.chord[n], ChordPlayer.chordPadArray[pos].data.strumLength * n); ChordPlayer.playingEvents[pos][n] = -1; };

@ulrik Its not working in Reaper on High Sierra , I will send you a VST3 via pm.
Thanks mate.

@Lindon Indeed :)

@orange I think these warnings are mostly useful for debugging and spotting where a scriptnode graph is likely to crash, as it can happen sometimes with some nodes.

This connection should be fine altough it would be better to keep the ranges identical when possible. You could use a control.smoothed_parameter_unscaled in that case.

@Fortune You can see it in use here, although I am not entirely sure why its called sidechain, unless its preparation for a sidechain input or something.
https://forum.hise.audio/topic/6386/simple-multiplex-style-switched-routing/10

@Matt_SF wow perfect, thank you !

@ulrik
Oh yes I saw that as well. Looks like a really clean solution!👍

@observantsound no it will be useful for people asking the same question

@Matt_SF Sure.. Thank's buddy.

@Christoph-Hart My mistake.