IPP Missing in Plugin Export
-
Thanks David! Using those settings, building HISE itself with IPP works fine, without needing to modify anything in VS. However plugin export still runs into some new ipp-related issues.
I tried poking around, but I just end up following back a bunch of #includes in different files with no real idea what I'm doing.
If I also enable IPP in the Visual Studio project as above, the plugin compiles, but it does not load in any DAW. Reaper does not even display it in the plugin list, and FL studio shows it as having an "error" in the plugin list. Disabling IPP and building again results in a vst that loads fine.
-
@Zorpley Yeah I haven't solved it either
-
Huge thank you to @DanH for having the foresight to save the old IPP installers (I was kicking myself for not doing the same). I can confirm that using IPP from the link in his post here works fine.
Here is the direct link to the correct IPP version.
Here is a backup link in case the Dropbox one stops working for whatever reason.
This kind of nonsense in software development drives me nuts. If Intel had just kept the old links up we could have avoided wasting our collective time.
-
@Zorpley I think I like the new installer better, though I'm not sure what it changes that's incompatible with HISE, I don't know the smaller details.
I think the developer will get around to trying to fix it, because third-party downloads of old software are unreliable and sometimes pretty sketchy. It's unsustainable to continue relying on something like that. Of course scriptnode seems to come first for now, and that looks like a pretty cool feature, so...
-
@AudioHobbyist Have you managed to get the new installer to actually work with HISE plugin exports?
-
Nope! I was just mentioning I like the new version better. Unfortunately it just happens to break HISE's compatibility, for whatever reasons. @d-healey has probably had more luck than me, and he hasn't solved it either.
-
Has the export issue been solved yet ?
-
@lalalandsynth Nope, use the older version of IPP.
-
I don't know what the situation is with IPP now in HISE, but the old dropbox link expired so here's an internetarchive link just in case: https://archive.org/details/intel-ipp
-
A year on and I just had this same issue for the first time, so I thought I'd update this thread for anyone else in my shoes. I got the same slew of ipp.h errors when trying to compile the master branch with VS2017 and IPP 2021.5.3.585, but I also got it to work by choosing "Static Library" in the Project > Properties > Intel Libraries for oneAPI dialog in VS. I didn't change anything in the HISE Standalone.projucer file (or elsewhere). I opened my finished HISE project and everything worked as expected, including the convolution reverb and analyzer, so I thought I was home free, but trying to export my plugin resulted in yet another slew of IPP errors. I downloaded IPP 2020.0.166 from the archive.org link above, plopped it on my desktop, and tried exporting again. To my shock and joy, it worked immediately. I didn't update any paths anywhere so I guess it just needs to exist somewhere on your computer? Seemed too good to be true but I'll take it.
Also a heads up: If you have both installed and recompile HISE, the VS Project > Properties panel will have two categories for IPP. The 2020 one says "Intel Performance Libraries" and the 2021 one says "Intel Libraries for oneAPI." So if you changed the setting for the new version and then downgraded IPP to recompile, you'll probably need to reenable it since they're different options.
-
C ccbl referenced this topic on
