The sanity check failed (???!!!???)
impossible to export anything from hise standalone without this message !
don't find any info about this raging error coming again and again and ...
please help me !
What does it say beside Sanity check failed? It usually gives more information like VST SDK missing, etc
hello Christoph !
no, just this.
i also tested tested with new from scratch (empty) project.
console: Master Chain:! RELEASE_RESOURCES_CALLED
empty project so that say i d'in't created a GUI interface and after that the sanity error.
Well, then add an interface
The sanity check will test a few common pitfalls so that you don't end up with cryptic compiler messages or non working plugins and not having an interface is one of them.
interface added, compiling and:
Re-saving file: C:\Hise test\Binaries\AutogeneratedProject.jucer
Error when saving: At least one of your JUCE module paths is invalid!
Please go to Config -> Modules and ensure each path points to the correct JUCE modules folder.
Compiling 64bit Standalone application Hise test ...
Microsoft (R) Build Engine, version 14.0.25123.0
Copyright (C) Microsoft Corporation. Tous droits réservés.
MSBUILD : error MSB1009: Le fichier projet n'existe pas.
Commutateur : C:\Hise test\Binaries\Builds\VisualStudio2015\Hise test.sln
Compiling finished.Cleaning up...
Le fichier spécifié est introuvable.
Le fichier spécifié est introuvable.
Appuyez sur une touche pour continuer...
You have to setup HISE for exporting plugins & gather some SDKs or you'll be in an endless loop of errors & missing file notification. Please have a look at the HISE Tutorial, which covers these steps. You can fast-forward to part 5 if you're in a hurry:
also had a projucer login problem. not linked but... difficult to test the autogeneratedproject.jucer
now it's working and in projucer that say effectively i have a path problem for some Juce modules (juce_audio_plugin_client).
i made mistake somewhere in the settings section.
will see it.
You ideally don't have to open the Projucer (it'll be launched as command line utility from within HISE).
problem found fixed.
i downloaded and used the standalone .exe file from the installer (download page) in a folder and the source code in another folder.
so i downloaded again via github, compiled the standalone app and use THIS .exe file (in the hise master/projects/.../..../HISE.exe)
some yellow error lines when exporting for now but it export it and work (just tested the standalone app, not vst plugins), and my project is not finished, so ...
for now just another questions, not the same subject but...
1 -if i compile standalone/vst project with embedded samples files., another users just need the vst/exe file ?
2 - i put the vst sdk & asio (for standalone) in tools folder, but didn't understand how to use IPP files (my project use the conv reverb).
3- just have problem to use sliderpacks with arpegiator. Conflict. how to setup a GUI with separate note numbers, velocity, length sliderpacks (in 1.1.1 version)
thanks in advance.
- You obviously need to distribute the sample files along with the plugin / standalone binaries, as they will get streamed from the disk. I highly recommend converting your samples to HLAC monoliths before distribution as this improves both performance, file size, memory consumption and convenience. I've been working on an sample archiver built into HISE that compresses all HLAC monoliths to FLAC format (which gives another 20% - 30% compression ratio) and splits the archive into chunks of 500MB for better downloading. I'll also create a "Sample Installer Application", which can be distributed along your binaries, which extracts the samples from the archive and creates all necessary file links.
- You just have to install the IPP library with the installer from Intel after you registered there (for free).
- You can connect SliderPacks on your GUI interface to a SliderPack of any module, but this feature is still a bit experimental (I am using it for a current project, but I have to clean a few inconsistencies before recommending it to use by other people.
thanks for answers.
1- yes i read all thread about samples and understood that the "embed" function in Hise is just for the IR file (for example), and that monolithic samples are just infos compiled in the final app; so we need to distribute the wav file with the app (standalone and/or vst).
2- ok. i though IPP files must be placed in tools as the vst/asio. each client using the app should download install IPP (or not) ? we could recomend it ?
3- found the problem (in front of my eyes of course). Each time i created a sliderpack, linked it to an arpegiator function, i just let the sliderpack index at 0. so it created crash problem. so i changed this index for each sliderpack (3 in total, the note numbers, velocity & length) and all working good for now
thanks for explanation.
PS: monoliths files AND encrypt samples files/folders (like the maize sampler, but in better way) should be really good.
PS2: i lovely dream finding BDD chorus (like juno chorus), another BDD chorus (like SDD-320/Dimension-D chorus) modules in hise. if you do that you become my king
You only need IPP to compile the plugins, the end user doesn't have to install it (it just a library toolkit that has a fast FFT which gets embedded into your plugin).
Encrypting samples is not a very smart thing as it has a huge impact on streaming performance, but with HLAC compressed monoliths, you basically have one big chunk of audio data which you would need to split manually to load it into another sampler, which is about the same effort as using a tool like SampleRobot.
If you find some open source code chorus I could take a look at and maybe embed it into HISE, another possibility is to license a closed source chorus algorithm from a 3rd party developer and use the DSP API to load it into HISE (I am doing this with a project and it works pretty flawless).
Roland Dimension-D Style Chorus.
it's coded for the RackAFX architecture and i don't know if it's open source.
for the Juno style chorus just invert the HPF cross mod ouput (put the left to the left, the right to the right = so no cross mod anymore)
and change the phase and wave of the second LFO signal (the -180°).
tried this and it works. so i know the code but just for rackafx, i don't know how to convert it to hise/juce script (or Hise module).
Christoph Hart last edited by Christoph Hart
Ah, yeah, I've encountered this project a few times but this Rack-AFX code is really terrible to adapt to other platforms as it's using it's own parameter definition system and LOTs of boilerplate code that makes my eyes hurt when I skim through the files.
If you're familiar with the architecture of Rack-AFX, you might give it a shot to convert to a HISE DSP-plugin using this pretty simple API:
You can then load it as .dll or embed it into your plugins.
good news for the API. if i remember well the rackafx code was created about a "rough" code. i will try to find it (http://basicsynth.com or http://musicdsp.org or else). I will try to find it.
i compiled the rackafx projects as .Dll so with this API i maybe will try to implement it in Hise.
if i don't write stupid things ERS made the dimension-D chorus in Juce....