Roadmap to HISE 5

Orvillain

Just pulled your most recent commit - sha a97795e41aa643cf3b2dfccd0ee69204f16f22ff

"fix DLL compilation on Windows complaining about IPP"

and only getting one error now:

!H:\development\HISE\HISE\hi_tools\hi_tools.h(233,10): error C1083: Cannot open include file: 'ipp.h': No such file or directory [E:\Client\Repositories\client-synth\client-synth-hise-project\DspNetworks\Binaries\Builds\VisualStudio2022\client-synth-hise-project_DynamicLibrary.vcxproj]

Christoph Hart

xcbeautify still needs changing to the UB build

This is done.

and only getting one error now:

yeah, IPP went completely crazy here, I'll do a couple of attempts to fix this but it seems that it causes issues based on which IPP version is installed (my build server breaks but on my local windows machine everything works)...

Orvillain

@Christoph-Hart said in Roadmap to HISE 5:

yeah, IPP went completely crazy here, I'll do a couple of attempts to fix this but it seems that it causes issues based on which IPP version is installed (my build server breaks but on my local windows machine everything works)...

Sha 4e6592a70a0a7e512693d5568ef3451a833616be ... this fails here too.

I upgraded my local IPP just to check that too. My install location for IPP is:
C:\Program Files (x86)\Intel\oneAPI\ipp\2022.2\include\ipp

I know they kept futzing with some of the install paths in the past, but I thought that had all settled.

Christoph Hart

@Orvillain does it work if you switch of UseIpp in the compiler settings of HISE?

Orvillain

@Christoph-Hart I've tried disabling IPP in the preprocessor definitions USE_IPP=0 and rebuilding HISE, and no difference. Is there anywhere else I should disable it to test with?

Christoph Hart

Orvillain

@Christoph-Hart said in Roadmap to HISE 5:

Nope, still not working. I've actually had that turned off all day, and I've tried various ways of compiling HISE to turned off IPP, and it still fils. Weird.

The latest develop commit gives me:

!H:\development\HISE\HISE\hi_tools\hi_tools\IppFFT.h(35,10): error C1083: Cannot open include file: 'ipp.h': No such file or directory

d.healey

@Orvillain Have you tried opening the autogenerated juicer file in projucer and adding USE_IPP=0 to the extra preprocessor definitions?

d.healey

Working on Linux (without IPP), haven't tried exporting yet.

Peek 2025-07-03 18-25.gif

Orvillain

@d-healey said in Roadmap to HISE 5:

@Orvillain Have you tried opening the autogenerated juicer file in projucer and adding USE_IPP=0 to the extra preprocessor definitions?

Yep, I covered that before.

But here's what is WILD....

I rebuilt HISE with USE_IPP=0 AND USE_IPP disabled in the hi_lac module..... and with the use IPP flag disabled in the project compiler settings.... it complains:
!H:\development\HISE\HISE\hi_tools\hi_tools\IppFFT.h(35,10): error C1083: Cannot open include file: 'ipp.h': No such file or directory

But if I turn the project compiler flag ON???

It compiles the network no problem.

So again, to restate it - I have IPP disabled in the compiled version of the HISE standalone, both in the preprocessor definitions, and in the hi_lac module. But I have to have it enabled in the actual project compiler settings, in order for the networks to compile.

This is all very strange. There seems to be some misalignment of the feature booleans going on under the hood.

dannytaurus

@d-healey LOOK AT THAT BEAUTIFUL RELEASE CURVE! 🥰️

Christoph Hart

OK, time for a matrix:

Task	Projucer Compile Flag	UseIppSetting	Works
Compile HISE	USE_IPP=0	n.a.	OK
Compile HISE	USE_IPP=1	n.a.	OK
Compile FX DLL	USE_IPP=0	UseIpp=Yes	nope
Compile FX DLL	USE_IPP=1	UseIpp=Yes	OK
Compile FX DLL	USE_IPP=0	UseIpp=No	OK
Compile FX DLL	USE_IPP=1	UseIpp=No	OK

Is that the case over there?

both in the preprocessor definitions, and in the hi_lac module.

I think you must not touch the preprocessor definition in the source code, as this will override the UseIpp setting. Just change it in the Projucer project for HISE, then resave & compile. Whether the project compilation (both plugin export & FX compilation is using Ipp is solely depending on the UseIpp flag (as this will properly set the OneAPI setting to work).

But as first step you should be able to compile HISE with IPP.

d.healey

@Christoph-Hart The USE_IPP setting has moved from hi_core to hi_lac - any particular reason?

Exporting as VST3 working here on Linux

Chazrox

@d-healey

via GIPHY

Orvillain

@Christoph-Hart Here are my results:

Task	Projucer Compile Flag	Projucer hi_lac IPP Setting	UseIppSetting	Drew Results
Compile HISE	USE_IPP=0	Disabled	n.a.	OK
Compile HISE	USE_IPP=0	Enabled	n.a.	OK
Compile HISE	USE_IPP=1	Disabled	n.a.	OK
Compile HISE	USE_IPP=1	Enabled	n.a.	OK
Compile FX DLL	USE_IPP=0	Enabled	UseIpp=Yes	YES NETWORKS COMPILE
Compile FX DLL	USE_IPP=0	Enabled	UseIpp=No	NO NETWORKS DO NOT COMPILE !H:\development\HISE\HISE\hi_tools\hi_tools\IppFFT.h(35,10): error C1083: Cannot open include file: 'ipp.h': No such file or directory
Compile FX DLL	USE_IPP=1	Enabled	UseIpp=Yes	YES NETWORKS COMPILE
Compile FX DLL	USE_IPP=1	Enabled	UseIpp=No	NO NETWORKS DO NOT COMPILE !H:\development\HISE\HISE\hi_tools\hi_tools\IppFFT.h(35,10): error C1083: Cannot open include file: 'ipp.h': No such file or directory

Now what I can't quite explain is that I've always had useIpp enabled inside the project compiler settings. So I don't even know how I started getting this issue.

My result from this post:
https://forum.hise.audio/post/105984

Were with the settings prior to updating from the latest develop branch and rebuilding - and IPP would've been enabled for everything.

The new network I created today, that compiles according to the chart above... doesn't seem to instantiate correctly. I'm still investigating this one though, so ignore for now.