Greg is right, just drag a cable from a parameter to the power button and it will control it's bypass state.

You can also define the range where it's on (default is 0.5-1.0), but in this example it's 0.5-0.8 so it will turn the oscillator off again if the parameter is full right:

HiseSnippet 1281.3ocyW07aaTDEeF6rgX2D9Lb2pmRkBQ1soTjPBaRbbkEwoVwIg1SUS1ch8Hu6LK6NNotEjPBNvMNCW3LWp3JGPJ+APN0CbMbr2B+ETl2Nq8tq2MstFAg8zNu48l426qeyLs8DlTeegGBWXugtTDdQiNC4xda1iv3nl0Q32znEwWR8JoEswPWhuO0Bgw4uKH.WXNTv2EU2fXS3lzHQHzABlIcalCSFIscsOiYa2fXQ2i4DS60q0zTv2TXKFnvSdixHWhYeRW5NDPsbFH77aYwjBuNRhj5qzYCg0vN8Dmv05e.ymcnMEFTA0QsPZwnM6wrsZOxW8QH7bsi777ZOeYiVLK1X4QQf2NXhRQVDOFfykDRyk.RUhCoxwfTCgsEr.fJogGJF5lSiNEHDVCrIxjHCRAgSvDIyNM4RJ2mIGFOEckB22wnMSZ1Ka7lKC7pRT+ai2vj+RFaczQTSYDXmynw8m0LckLgRlEh3zwthFcL8XtR09C.YwvgkZb+JI.jVLB+yFaw6x3z0L8nJnU22cGp7DgW+Uttku60uQoOdohGMfaBQ7RtdTWhGcOQaaxvU7INt1zcUVsZoCsEl86vdL8FEeRwBE+phkhYT.F2.zXEydDNmZ6mVMn4kK8D1qvG3bH0a0RGSrGDsdo5eeioKDJ3M4L48bogpkvGFIVwVDCkQRGCpHQYTQrqXfjw61hH8XOBgM1YfSGEMjIcyPuUICmCAlFLtLLFJP6P4VACdg5KbxJvXb3jUFMIBvAkKUxCyOA4+v+U+AIaCCUJCjJr.lwFDSU3ZXahrGz9nnGkp5Sp2ZliqSmGrnBRA3Ig51p3PBw37vxNhfUi+MENN.n.50v++blErcF3UUZnK31UUm.j0s7iSWCYt1DOE6r57AX8yo2Avuxq8fh5JXguohxGXCPobIO5Zwl9pvOpOjSbXlZU.tKHht1XOKAKENeD80dDutTYHghK0SxniZogQJhr7f6WvXeeJbDB5.nc.ve6AGZyLg+PwBfJ8i1Tbgl7iUqhtWuEiGZbD2XKxilP1B01VbB0ahyaQn8ccSIcgZcjTWneO94Cc5SOQmghKUWm0BxnoPAZ5g750RA4u6YYB40qkAjU5FGx+3O.e+5DP9ru7424abNK.xWyngG8KFP4lCm.2ec+ZuF39hpoC0kyD2WTMqPc4WyP8hA3tztPQFJEVP5NqE.MWxvQvE2DteFUjr05c0sVwm+pn25R5WhUzmn4ItyMuQWfjKgWcMsWELw+ibm3s+4ln8eQico9ToNOlp8INSPR6dKf1XZMMNIRtoux9AmltxFhhoqrevoYUYqNh6U1Q9Il+1Yc+k2ulNkF7lgw63uG7c6SQ+i38p88SOumR2WMjewvep86U+YgjHcbDBYO0sCPo3yRF3ww7h401FIY5XvUzBwP2SV9o28Oe72dITEiMETZ4m9GUwX0UL3zfKiEfmngJr.MBMsl3z3w3Clonw3S5TVFjD7.oMsTsHvEyum63anNpp7kmrNOAyoNX+7pYkrNeBlSst+U0zLmmeIgij7H62rNQRBCBv0thMKFWmdr5coZmofQcpeeov8+laA5PL8DOzTemTHKsPfDUSOO3YtETu2VMtTEzw53lgQ40JibT2e3gllv6R9.0aZx1laNC1bqYvl0mAat8LXyGNC1bmYvlO5kZCb0sOcfT3neypRP6sBJtv3s3D06UBJ9Q+M.NBYIA

Check this:

https://forum.hise.audio/recent.rss

Not sure if it's helpful though

Yes, all Math.xxx functions can be used. You can even call Console.print to output the value...

Yes I am already using the SharedResourcePointer class in a few things - it's used to share image resources and other stuff across plugin instances.

However this is just a tool for sharing data and to setup a communication between instances with callbacks and complex data transfers is way more complex (especially if it needs to be a wrapper for HiseScript). Also there are hosts who run each plugin instance in a different process (AFAIK Bitwig does this), so you'll run into many troubles even if you get it working on your system.

I would strongly suggest to stay away from trying to implement this feature unless it is the core feature of your plugin (like it is with MIR).

If you really need is, go C++, use HISE as C++ framework and build your inter-plugin communcation system from the ground up.

Oh, BTW, you can also use the Expression property in the modulation target popup to make it use the frequency domain. Just enter this formula:

input > 0.0 ? (1.0 / (input * 0.001)) : 0.0

The Expression property didn't work on the tempo_sync node, but I've fixed that. It basically lets you write a mini SNEX expression with input being the variable for the, well..., input.

I've just added a UseFreqDomain property to the core.tempo_sync node. If it's enabled, it will convert the millisecond value for the tempo into a frequency in Hz so you can feed it to the oscillator / FM, etc...

I've also added the missing oscillator types (saw / triangle, square), but be aware that this is the most naive implementation only suitable for LFO stuff - if you want to use it as actual sound generators, they will alias extremely terrible (I'll add a core.polyblep node with the exact algorithms from the WaveSynthesiser HISE module soon).

I wouldn't try to use the JSON file approach in a real project, seems way too hacky.

The problem with interprocess communication is memory management and since there is no one single solution it usually requires getting your hands dirty in C++ (or even C) with the specs you had in mind.

AFAIK 10.7 is the oldest supported macOS version

Lol they better make the non-buggiest DAW on earth because I don‘t see any plugin developer spending 2000k+ € to get a testing rig just for their software.

just slap a core.peak node after it and it will take the output of the jit node as mod source.