Can't figure out how to compile project/export as standalone plugin

Bicrome

Today I've installed HISE following this tutorial, with Faust and FFTW.
I want to make my own effect plugins, and I understand how to do so using ScriptFX, but I can't seem to figure out how to export my projects.

Actually, first of all I must say that I don't really understand how the file management works on HISE, even after watching this video. If I've understood correctly, I should create a project for each effect or instrument that I want to make, and inside the project, when I hit Ctrl + S I can save what I've made as a preset, inside the project, and that way I can have different iterations of my effect or plugins as different presets inside the same project folder.
Am I right? Please help me in this aspect too. And to open different projects, do I directly open a preset? Or what? I'm really confused about this.

Now, exporting. I've installed HISE correctly on my machine, as I've previously said. I only have a single instalation, and everything is up to date. On HISE, I've disabled using IPP and enabled exporting as VST3. I've then run the export wizard and everything went OK.
But when I go to Compile Project it gives this errors:

> Perform sanity checks
> Create C++ autogenerated files
> Create binary data files
> Exporting the pooled resources
Export audio files
Export image files
Export samplemap files
Export MIDI files
DONE
> Create embedded data files
> Launch system compiler...
Re-saving file: C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\AutogeneratedProject.jucer
Finished saving: Visual Studio 2022
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit FX plugin lo-fi_knob ...
Versión de MSBuild 17.14.14+a129329f1 para .NET Framework

  CopyProtection.cpp
  Plugin.cpp
  PresetData.cpp
  BinaryData.cpp
  include_hi_core.cpp
  include_hi_core_02.cpp
  include_hi_core_03.cpp
  include_hi_core_04.cpp
  include_hi_core_05.cpp
  include_hi_dsp_library_01.cpp
  include_hi_dsp_library_02.cpp
  include_hi_frontend.cpp
  include_hi_lac.cpp
  include_hi_lac_02.cpp
  include_hi_rlottie.cpp
  include_hi_rlottie_1.cpp
  include_hi_rlottie_2.cpp
  include_hi_rlottie_3.cpp
  include_hi_rlottie_4.cpp
  include_hi_rlottie_5.cpp
  include_hi_rlottie_6.cpp
  include_hi_rlottie_7.cpp
  include_hi_rlottie_8.cpp
  include_hi_rlottie_9.cpp
  include_hi_rlottie_10.cpp
  include_hi_rlottie_11.cpp
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  include_hi_rlottie_12.cpp
  (compilando archivo de origen "../../Source/Plugin.cpp")
  
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_core_02.cpp")
  
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_core_04.cpp")
  
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_core.cpp")
  
  include_hi_rlottie_13.cpp
  include_hi_rlottie_14.cpp
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_frontend.cpp")
  include_hi_rlottie_16.cpp
  include_hi_rlottie_17.cpp
  include_hi_rlottie_18.cpp
  include_hi_rlottie_19.cpp
  include_hi_rlottie_20.cpp
  include_hi_rlottie_21.cpp
  include_hi_rlottie_22.cpp
  include_hi_rlottie_23.cpp
  include_hi_rlottie_24.cpp
  include_hi_rlottie_25.cpp
  include_hi_rlottie_26.cpp
  include_hi_rlottie_27.cpp
  include_hi_rlottie_28.cpp
  include_hi_rlottie_29.cpp
  include_hi_rlottie_30.cpp
  include_hi_rlottie_31.cpp
  include_hi_rlottie_32.cpp
  include_hi_rlottie_33.cpp
  include_hi_rlottie_34.cpp
  include_hi_rlottie_35.cpp
  include_hi_scripting_01.cpp
  include_hi_scripting_02.cpp
  include_hi_scripting_03.cpp
  include_hi_scripting_04.cpp
  include_hi_snex.cpp
  include_hi_snex_62.cpp
  include_hi_streaming.cpp
  include_hi_tools_01.cpp
  include_hi_tools_02.cpp
  include_hi_zstd_1.cpp
  include_hi_zstd_2.cpp
  include_hi_zstd_3.cpp
  include_juce_audio_basics.cpp
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_scripting_01.cpp")
  include_juce_audio_devices.cpp
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_scripting_03.cpp")
  
  include_juce_audio_formats.cpp
  include_juce_audio_plugin_client_utils.cpp
!C:\Users\PAU\Documents\HISESourceCode\hi_core\hi_core.h(538,10): error C1083: No se puede abrir el archivo incluir: 'ipp.h': No such file or directory [C:\Users\PAU\Documents\HISE Projects\lo-fi_knob\Binaries\Builds\VisualStudio2022\lo-fi_knob_SharedCode.vcxproj]
  (compilando archivo de origen "../../JuceLibraryCode/include_hi_tools_01.cpp")
  
  include_juce_audio_processors.cpp
  include_juce_audio_utils.cpp
  include_juce_core.cpp
  include_juce_cryptography.cpp
  include_juce_data_structures.cpp
  include_juce_dsp.cpp
  include_juce_events.cpp
  include_juce_graphics.cpp
  include_juce_gui_extra.cpp
  include_juce_opengl.cpp
  include_juce_osc.cpp
  include_juce_product_unlocking.cpp
  include_melatonin_blur.cpp
!Compilation error. Check the compiler output.

Also, what I was trying to export was a really simple filter (which could serve as the base for a one knob lofi plugin):

HiseSnippet 1382.3ocuW06aaaDE+nrohsRaQBZ6t5lcQpgj+JwnCR1VVsBo1QMz0HaNmIOFcPGuig7nsTJ5T6P15Z8T+WIKcqcJCEnaMCYpCAn+Az9tijhjgxNNBsQFvP28t28989526T+.gMILTDfLpc3XeBx38LsFykC1c.lxQ85fL9XSl3yboGOjKNote.IjHazDsyXebXHwAYXL2WnNpwhyizedUqcvLL2ljsEBcjfZS9JpGUlsa+12kxXcwNjCod4N85s6YK36JXhH.VyY1.4isGheD4.r5XULQeINb.x3SM2X00rW241Nqt5FasoMdSxVtXW2lq4r95admsZt1V30uyljFafLptmCUJBrjXIIDYL+NBmwVCDmwiMvQzP5ILhZQSjEX43s6JXNJWTsKZ2ATlS+z3UHBtk9YQu4hidej49TG5j8yhh2PKndlF4CfFUJBu4J.ul4gWibvaJPxHGjlOFR2zzxNf5Kyjnvy0M6wkj.WLjmxCk3yhLdl4tB3.b4Jd3gjtAvhIJrzlMZbq5v+V9yci31RpfWWvOPHI2iuzx091ZKV66pU+0E45NUYJyDHXLRvTEqJMBtLEWhG4cBI3V0OEyhHSNH39EiolWbLMeJ2N1qycPAuGmJumOgeQEBnjPkJ9mfJ3nRcz+CRh9VLpCI.Qgf70LuKzJ0DoAb9lDz2zqCVhSuF3FAq3SBjTkCXzgbJzDEmTWzrCIbnT3qOqmufqruwBuQiNJyf71imrnse6PIw2h9jTD09OexOzRRFIU0JLgKsth..4m528bzbEZ6Tu6CZBMoAP+IThnjTUqBziWpbDZDDNQLrrX2ghCIQ.jdKTRpp63gT437bL+m0xbUg3MM6Sk1ClNFqLELBow+OvXBQy6atmqKwVlAv4M69f2crJ0RR8fMUFuPkvz3SdpYVuKLDAJVHGJ5yviWJD64yH2Gv3speBSXOTUDVtgOovaG0IVxd.lyIrvYgWn5UNpz7xSJ2WDIo7GsOVFPg1JyCh7rfQV1jcSPGrmQEE8P75Fp0p5BKB2Qu3efOIBapVajHrYpvLlEzAD4Yhfg5zQx2g983XenNHer6H.9jfPUwIzv2XE3Oz1Ll3LEEAMorERJ585KXi8GH3Ta0VwmHE5a6IhT7Iw3Oqlemz7Spq.ShODSYpV.qnPfiz4dbK3dzi+gRPiCDNv2tVWrMDyG2GKGnZkTrrPcKIXE6I0uEbi7kPwi8KHVku5mx2n3FqnrS5SFhgF3QdZRQ3ACvk.xiicZ.UUYwELCO08XxiQEP2MLcoL00tRhzxXYhhuIqphpLxnTV8twWb1Wguzi6PFMIemyo.PNYEDA2mxOpv.i1+b68wiJt2Sedaqgjyh8mTh7u262ZEOxua.4wQPtYL5PfX+PgVYnD6TXFixH4OQGhKNhIeMa9is2NRJ7fVGMsGJGBqlGgme94K+KehQAD9HW0mW1pHBewe7Wu72idgFgyY90kr6Z5O+cqKztyWJxfV8YkhLnUaqrPU8fFzQkF8l6BMKegPOPoK7UsJEpe3G144IgZKOgPN.nGJXK8P0YvV2nsUwoyZ6G6P6qJnuTGpZYi7pVkMBv8LEiTxIu9u9SWaakoWzbONFnJcPuVtI6QKnhEzF487XzqelvUEek1XuQvcwwrbSkgIScngw3R+NJNQOYPY+4xVhhoLTuUYR2b+7ufIeu.5sPOUM7ay4yhhEBb5YtpUvKJpDSO1K7HkTaLKMP.A6Y4IiuSlb4gsCDGaGOLV4PKn2ABPbMG5hl6qVWeJuC1C9kRGaaW7pJo3pyphqMqJt9rp3FyphaNqJd6YUw67lUT8CYS53UE3.eU+8zEgFFokxvjRz+BHUk0wL

I also get errors when i Export as FX Plugin.

Idk why I'm not figuring this out... I've searched in the Forum and the Docs, but got nothing. Maybe I've done something dumb idk.
It's the third time that I compile HISE, so I'm sure that I haven't done a mistake there.

So... how do you compile your HISE project and export it as a plugin?
By what David said in one of his videos, i understood that I needed Projucer to compile my projects in to standalone effects... idk

Also I forgot that when I try to export it always says "The source code has a different commit hash than the HISE build. This will likely lead to undefined behaviour including compile errors or undetected errors. In order to proceed with the compilation, type 'I know' and click OK."

If i go to Help --> About HISE, on the Git commit hash it says load current hash... , and if I press the button next to it that says Show commit in GitHub, it opens the folder where the HISE.exe is located (C:\Users\MyUser\Documents\HISE\projects\standalone\Builds\VisualStudio2022\x64\Release with Faust\App).

Thanks in advance, guys. I love what HISE can do so i hope that the community can help me with this.
Cheers

HISEnberg

@Bicrome Have you set your HISE path to point towards HISE in your project settings?

Screenshot 2025-07-11 at 12.42.09 PM.png

Bicrome

This post is deleted!

Bicrome

@HISEnberg It already points towards the folder that I've created to store the source code that the Export Wizard asks for: C:\Users\MyUser\Documents\HISESourceCode (I manually created this folder to store that source code).
Is it the right folder?

HISEnberg

@Bicrome Ah I see that you also have IPP enabled. Did you download the library for it (I think it's in David's video on how to do this). I believe the recent develop branch has also had problems with IPP lately. You really only need IPP for some niche use-cases so you can also disable it before compiling HISE (There is a flag in the Projucer you can set for this).

Roadmap to HISE 5

@Lindon said in Roadmap to HISE 5: what about building without IPP on Windows??? Set this to No

Forum (forum.hise.audio)

Bicrome

@HISEnberg Before compiling HISE with the first video that I mention on my original message, I did it following the video that you have linked. That time i downloaded IPP, but then I've uninstalled it and installed FFTW. I have disabled using IPP when i compiled HISE with projucer, and on HISE itself too. Idk why it gives the error message.

The only thing that I didn't do that Dave said its to do this, but because the option wasn't there!

What am I missing?

HISEnberg

@Bicrome Oh nice that video is much more up to date so it's probably better to follow that one. Your project is still trying to link to IPP meaning 1 of 2 things:

IPP is still enabled. After you disabled it you recompiled HISE correct?
You're working with an old binary that's linked to IPP still. In your project go to Export > Clean build directory. This will clear out your build folder and you can try building your plugin afresh.

I think try the second option first.

Bicrome

@HISEnberg Second option didn't work.
I've tried to recompile HISE, now as debug and without Faust.
In the output it said that it could open the file fftw3.h: no such file or directory.
shit.

But my laptop has dual boot with Linux Mint aswell. Would installing HISE on Linux be less of a headache? I don't even care about IPP and FFTW at this point. Just let me export my plugins . But if I use it on Linux, will HISE still export Windows VSTs? Because I have my windows partition only to make music with Ableton.

d.healey

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

FFTW.

That FFTW setup is already out of date :) but coming very soon is a new setup and I'll update the video with it.

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

I should create a project for each effect or instrument that I want to make, and inside the project, when I hit Ctrl + S I can save what I've made as a preset, inside the project, and that way I can have different iterations of my effect or plugins as different presets inside the same project folder.

One folder per project.

Use ctrl+shift+s to create an XML file - one per project.

Use ctrl+s to create a .hip, these are not human readable so can't be recovered (easily) if something goes wrong. You should only use them for little test patches rather than as the main project file (that's what the xml is for).

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

And to open different projects

File >> Load Project. Then load the project xml - you will be prompted to automatically when loading the project.

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

I've disabled using IPP

The check box in project preferences?

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

The source code has a different commit hash than the HISE build

This means that the version of HISE you are using is not built with the version of the HISE source code you have.

Check your system, you probably have two copies of the source code - it's possible the Export Wizard downloaded one.

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

Would installing HISE on Linux be less of a headache?

Nope.

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

If I use it on Linux, will HISE still export Windows VSTs?

You need to export on each OS separately.

Bicrome

@d-healey said in Can't figure out how to compile project/export as standalone plugin:

The check box in project preferences?

Yes!

@d-healey said in Can't figure out how to compile project/export as standalone plugin:

it's possible the Export Wizard downloaded one.

I think it did. But should the version that the Export Wizard automatically downloads be the right one?

And thanks for the other answers aswell!

d.healey

@Bicrome said in Can't figure out how to compile project/export as standalone plugin:

But should the version that the Export Wizard automatically downloads be the right one?

I don't like the export wizard, it does stuff automatically and unless you know what it's doing it leads to confusing situations like this.

I'm not sure if it downloads the master or the develop branch but either way I think it's best that you don't use it and do all the downloading manually.

So search your system and make sure there is only one copy of the source code.

Can't figure out how to compile project/export as standalone plugin

Roadmap to HISE 5

27

1.8k

12.1k

105.6k