@DanH It's super secret🤫- It is similar to Serum's

@griffinboy I see. Thanks, I'll give it a look.

@d-healey haha, only half the plugin's authorization is written on the plugin, we are routing it through our website's API, so it'll be a lot safer already, was just wondering if I had to do anything else to ensure even more security.

@xander my guess is your faust code works with a fix expected samplerate so that when you‘re oversampling it shifts the normalised frequency ratio.

@ustk This didn't fix it completely, but it definitely helped a lot, thank you

@xander try asking on the faust discord channel

https://discord.com/channels/1078607704769179729/1078607704769179732

@xander maybe put this in the HISE Faust github?

@d-healey Thank you! Makes sense, guess I can hardcode the parameter values.

@orange Alright, thanks, I'll try that.

@aaronventure Wow that was easier than I thought it'd be!

@xander global cable.

https://docs.hise.dev/scripting/scripting-api/globalcable/index.html

@xander You need to export (compile) separately on each OS you want to use.

For AAX you need to sign up for an AVID developer account, and you'll also need a PACE account and iLok for signing your plugins. You'll need to compile the AAX SDK on each OS before you can use it.

@Gab Unfortunately I don't think it has anything to do with IPP, as it lags with both IPP on and off.