@ally It worked! Thank you @ulrik!!

@d-healey It hides a panel and un-bypasses a module based on a flag, p1. The panel was not showing but the module was bypassed, which is a mismatch. I ended up figuring out that f1 was firing after all and the issue was solved by explicitly setting the panel's starting visibility in the script before the functions run. All other hosts were showing it (it was visible when I compiled) but PT hid it. Still not totally sure why, and there's definitely some difference in how something is handled, but what I described specifically was a false alarm!

@ally the effect slot can only host master effects but good reminder to remove the polyfx from the list.

Just came looking for this again and noticed Christoph solved this a couple of weeks ago - https://github.com/christophhart/HISE/commit/2057eb72499e0be24b8effe0e908588d40d8311d

We now have Modulator.setIsBipolar() and Modulator.isBipolar()

@Christoph-Hart Woohoo, perfect! Thank you!

@ally using per voice oversampling is hugely ineffective so it‘s deliberately deactivated.

You can enable a global oversampler with Engine.setMinimumSampleRate() if you need that but usually aliasing on the oscillator level should be fixed otherwise.

@ally Check out Aaron's post from a few days ago - https://forum.hise.audio/topic/9280/latest-ipp-2021-10-build-issues

Got this working, thank you everyone for your help! The fix was just updating Visual Studio past 2017. :)

@d-healey thanks!

@ericchesek Good thinking, it does appear to be that midi cc message(s).

After extensive testing, I think it may be a bug or at the very least a less than ideal behavior.

I downloaded some of the various Hise instruments that are linked on the main page of the Hise site as well as even bought a couple commercial releases that were made with hise.

It appears that if in the MIX tab <> Auto Select Automation Parameters <> is on, the behavior in the video posted above happens.

If you have that mode unchecked, it does not happen.

@d-healey You know, I kept thinking "I wish there was a way to only have to compile the changes I made" during my many hours of waiting... Good to know that exists lol

@ally

To make it easier with just one step, just add --force to the signing code. So the signing code will be codesign --force -s ......

Thanks everyone for the clarification! Based on the general consensus I thought I'd successfully exported a universal binary (I had 2 versions of Xcode on my Big Sur computer, 10.3 and 13.2.1) and didn't have a way to check until I recently borrowed a fresh, Rosetta-less M1 laptop and it didn't work. In lieu of holding the laptop hostage, I looked into how to check on any Mac via Terminal:

Export plugin Right click > "Show package contents" > Contents > MacOS > [plugin executable file] Type "lipo -archs " into Terminal and drag the executable in. Terminal returns "x86_64 arm64" if it's a universal binary and "x86_64" if it's Intel only.

Mine were Intel only at first because HISE was using the older version of Xcode to export (I'm guessing because that's what I used to compile HISE itself), so I just had to open the autogenerated Xcode project in the newer Xcode version and export from there. Everything was already set up correctly in the file, so I assume you would not have these issues if your whole setup was not based on an older version of Xcode.

@Casey-Kolb Coming back to say thanks! I replaced those 3 waveforms with pngs and that seems to have solved it. It wasn't super reliably replicable so won't be 100% sure till the plugin is released and people do or don't complain lol... but I haven't gotten the error again yet.