Roadmap to HISE 5

[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.

[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.

[Orvillain]

@Christoph-Hart said in Roadmap to HISE 5:

I think you must not touch the preprocessor definition in the source code

Just to clarify, I didn't edit any code. I'm talking about the setting here:

[Chazrox]

@d-healey modes?? Please share!

[d.healey]

@Chazrox said in Roadmap to HISE 5:

modes?? Please share!

What you talkin bout Willis?

[Chazrox]

@d-healey lol

[d.healey]

@Chazrox Trigger, Note, Loop

[clevername27]

@Christoph-Hart Meanwhile, I was fired by all three clients because of HISE bugs and secret ScriptNode documentation. sigh

[Lindon]

@d-healey said in Roadmap to HISE 5:

@Chazrox Trigger, Note, Loop

yeah but how do they work?

[Christoph Hart]

@Lindon just like the ableton one which I completely stole the feature list from.

[Lindon]

@Christoph-Hart LOL damn! I don't use Ableton I will have to go look it up...

[Lindon]

@Christoph-Hart

damn it again. A quick cursory look and this doesnt seem to resolve the "Note Generator sends Global envelope data to non listening voices" problem....

[Lindon]

@Lindon maybe I should go away and state this problem clearly - there may be another solution...

[Christoph Hart]

@Lindon The note generation must happen one level below the global modulator container. You have to make sure that every voice that receives the global envelope data is started by the same event ID as this is the most robust way of assigning voice indexes.

So if you have this setup:

master chain
   global modulator container
      AHDSR
   sine generator
      Arpeggiator
      GlobalEnvelope / MatrixModulator

it will not work because the arpeggiator will produce new events where the global modulator has no idea how to assign that to voices. But if you either move the global container and the sine wave into a new container or move the arpeggiator to the root level it should work correctly.