Thanks so much for sharing your knowledge in all your Videos! Great stuff! Btw, close to finish my first sampler - wouldnt habe a Chance on that without your help!
Thank you! i wanted to go back into hise to work on a piano insturment and i've built the Hise 1.2, but i wanted to try the new scriptnode and i didn't knew it was in a branch so now i do
Thank you! When I first tried it, I missed the step at 8:56 (delete the second sdk sub folder from the path when extracting) and kept getting errors. Got it to work the 2nd time around
Thank you for sharing this valuable information! I've been attempting to build Hise with IPP, but I've encountered persistent errors. Specifically, I'm facing issues related to the expansion of IPP and difficulties in locating the specified path. I would greatly appreciate any insights or guidance you might have on resolving these issues. Thank you in advance for your help!
@@DHealey I am have a problem with IPP also. I have followed your Instructions in this video but in Juice, when clicking on Visual Studio tab, in the "Extra Preprocessor Definitions" section I do not have the USE_IPP=1 line. I have HISE-SCRIPT-SERVER-TIMEOUT=20000 and HISE-USE-VS2022=1. In my start window under Intel folder I do have "Intel oneAPI 2024". What would by my next course of actions?
Super helpful tutorial thank you but can someone explain to me why I have to make a build of hise in order to create the vst why can't I just export from the default program?
When you make a HISE project, HISE will generate a JUCE based C++ project for you. This needs to be compiled to turn it into an executable program like a VSTi or AU. The process of compiling your project is the same process used for compiling HISE. So it's always good to start by compiling HISE because that allows you to make sure you have a working setup - it also gives you access to all the latest features which aren't yet available in the prebuilt binaries.
Thank you! After git pull and update the local Hise rep should we recompile the release build? To do this just recompile solution is ok, or should we delete/clean the builds folder before that? Thanks again.
Why is the rule of thumb to always use the most updated branch? Isn't that branch more likely to have development bugs? Why not use the latest stable release or master?
All branches have bugs. The develop branch gets the fixes sooner, and also new bugs. Most importantly the develop branch gets new features which is why I recommend to use it. Also the master branch wasn't update for a few years at one point so you would have been left with an ancient version of HISE if you'd used the master branch. If you do use the master branch and you discover a bug, then you are stuck with that bug until the master branch is updated, which might be several months. Now the bug might also be on the develop branch, but it will be fixed there before the master branch. As far as stability is concerned the develop and master branches are as stable as each other. Occasionally a commit will be made to develop that prevents it compiling but this is usually resolved within a day.
thanks for video, sadly i cant export any plugins because it always says C:\Program Files (x86)\Intel\oneAPI\ipp\2022.0\include\ipp.h(24,10): error C1083: Cannot open include file: 'ippversion .h': No such file or directory [C:\Users\90530\Documents\HISE Projects\a\guzeldusunceler\Binaries\Builds\VisualStudio20 22\guzeldusunceler_SharedCode.vcxproj] and i tried 5-6 hours fixing it but i cant :(
To compile a plugin just use the export menu in HISE. This will create a batch file (on Windows) which automatically does all the commands - creating the juicer file, saving the project, opening it in Visual Studio, and compiling it. Once you have the juicer project you can also do the rest manually like when building HISE.
@@DHealey Meaning, I open Juicer and start a new project... this may be a dumb question, but do you create a new folder to save the new project in? Is there a folder I should avoid saving to?
@@curiousrodeo No you don't need to touch the juicer file or Projucer. Just go to the export menu within HISE and select Export as instrument. As long as you have already built HISE on that system the process should be automatic.
Unfortunately there seems to always be issues with IPP between different versions, but usually it's not too difficult to work around them. I don't use IPP myself so I suggest you make a post on the HISE forum and someone there will be able to help.
Thanks for this. If we'd also like to make plugins for iOS/iPadOS or Android, would we select and install Mobile Development with C++ as well as the Desktop version?
I've never tried exporting for mobile and HISE out of the box probably won't be able to. If you search the forum I think you will find some threads about it, one guy got pretty far with iOS, not sure anyone has tried Android.
I have followed every one of these steps to the letter and I am getting all kinds of Juce errors upon compiling it. Can you tell me what I ma doing wrong or is this video outdated given the components used now?
The majority of it is a one time thing, after you have the system setup all you need to do to update to the latest version of HISE is grab the latest source code and recompile. Some development environments can be a lot more cumbersome to maintain.
Ok, figured out the IPP build issue. For me it was finding but was not finding or . I traced through what ipp.h was doing. It actually ALREADY INCLUDES all of the other .h files needed by IPP. So here's what I did: In PostGraphicsRenderer.cpp #if USE_IPP #include //#include
WOW I am so excited to start using this !!! Wouldnt have done it without you!
Man this is crystal clear and a pleasure to follow. Thanks a lot for the video :)
Thanks so much for sharing your knowledge in all your Videos! Great stuff!
Btw, close to finish my first sampler - wouldnt habe a Chance on that without your help!
Thank you! i wanted to go back into hise to work on a piano insturment and i've built the Hise 1.2, but i wanted to try the new scriptnode and i didn't knew it was in a branch so now i do
You might have a bit of work to do to make your project work smoothly in the latest version of HISE, but it will be worth it.
Amazing work!
Thanks!
Thanks for this, very concise and to the point!
Glad you enjoyed it!
Thanks so much for the video 👌
Thank you! When I first tried it, I missed the step at 8:56 (delete the second sdk sub folder from the path when extracting) and kept getting errors. Got it to work the 2nd time around
Thank you for this tutorial. I could not build with IPP so built without. Working fine without it.
Did you get a successful working vst out of Hise without IPP? Just wondering, everything working?
Thank you for sharing this valuable information! I've been attempting to build Hise with IPP, but I've encountered persistent errors. Specifically, I'm facing issues related to the expansion of IPP and difficulties in locating the specified path. I would greatly appreciate any insights or guidance you might have on resolving these issues. Thank you in advance for your help!
Are you using the OneAPI?
@@DHealey I am have a problem with IPP also. I have followed your Instructions in this video but in Juice, when clicking on Visual Studio tab, in the "Extra Preprocessor Definitions" section I do not have the USE_IPP=1 line. I have HISE-SCRIPT-SERVER-TIMEOUT=20000 and HISE-USE-VS2022=1. In my start window under Intel folder I do have "Intel oneAPI 2024". What would by my next course of actions?
@@maddogmac8176 You can add that line yourself, it's just a textbox
I swear im doing everything right and I keep getting 24 errors saying “cannot open include file: ‘ipp.h’ :No such file or directory😑
I installed without IPP, hopefully I can make my VST with no problems though thanks for the vid!
Which branch did you download?
Super helpful tutorial thank you but can someone explain to me why I have to make a build of hise in order to create the vst why can't I just export from the default program?
When you make a HISE project, HISE will generate a JUCE based C++ project for you. This needs to be compiled to turn it into an executable program like a VSTi or AU.
The process of compiling your project is the same process used for compiling HISE. So it's always good to start by compiling HISE because that allows you to make sure you have a working setup - it also gives you access to all the latest features which aren't yet available in the prebuilt binaries.
Thank you! After git pull and update the local Hise rep should we recompile the release build? To do this just recompile solution is ok, or should we delete/clean the builds folder before that? Thanks again.
Usually you can just recompile, but some times you'll need to clean first. If you get errors, try cleaning.
I did everything to the T , I'm using all the latest downloads as of today 3/19/2024. No Hise EXE. showing in the Builds folder
Post your compile errors on the HISE forum and we'll figure out what's going on.
Why is the rule of thumb to always use the most updated branch? Isn't that branch more likely to have development bugs? Why not use the latest stable release or master?
All branches have bugs. The develop branch gets the fixes sooner, and also new bugs. Most importantly the develop branch gets new features which is why I recommend to use it.
Also the master branch wasn't update for a few years at one point so you would have been left with an ancient version of HISE if you'd used the master branch.
If you do use the master branch and you discover a bug, then you are stuck with that bug until the master branch is updated, which might be several months. Now the bug might also be on the develop branch, but it will be fixed there before the master branch.
As far as stability is concerned the develop and master branches are as stable as each other. Occasionally a commit will be made to develop that prevents it compiling but this is usually resolved within a day.
thanks for video, sadly i cant export any plugins because it always says
C:\Program Files (x86)\Intel\oneAPI\ipp\2022.0\include\ipp.h(24,10): error C1083: Cannot open include file: 'ippversion
.h': No such file or directory [C:\Users\90530\Documents\HISE Projects\a\guzeldusunceler\Binaries\Builds\VisualStudio20
22\guzeldusunceler_SharedCode.vcxproj]
and i tried 5-6 hours fixing it but i cant :(
Disable IPP in project preferences.
@ thanks! I became so frustrated that I asked the same question twice. Sorry for the spam :D
@@flagtrap5925 Did it work?
@@DHealey It worked wonders! Thanks!
Do we follow the same steps for VST, or will this be able to build VSTs?
To compile a plugin just use the export menu in HISE. This will create a batch file (on Windows) which automatically does all the commands - creating the juicer file, saving the project, opening it in Visual Studio, and compiling it.
Once you have the juicer project you can also do the rest manually like when building HISE.
@@DHealey Meaning, I open Juicer and start a new project... this may be a dumb question, but do you create a new folder to save the new project in? Is there a folder I should avoid saving to?
@@curiousrodeo No you don't need to touch the juicer file or Projucer. Just go to the export menu within HISE and select Export as instrument.
As long as you have already built HISE on that system the process should be automatic.
Hey i was wondering if you knew what this means and how to fix it.. c1083 cannot open include file
I'd need more info. Make a post about it on the HISE forum and post some screenshots or console output.
does it work the same with visual studio code?
No it requires a compiler, you need to use Visual Studio
what are solutions if Im getting many syntax errors and other errors?
@@DHealey
IPP not working 12 errors 4 warnings, David can you help.
Unfortunately there seems to always be issues with IPP between different versions, but usually it's not too difficult to work around them. I don't use IPP myself so I suggest you make a post on the HISE forum and someone there will be able to help.
Thank you david, I'll try a build without IPP as well! @@DHealey
Thanks for this. If we'd also like to make plugins for iOS/iPadOS or Android, would we select and install Mobile Development with C++ as well as the Desktop version?
I've never tried exporting for mobile and HISE out of the box probably won't be able to. If you search the forum I think you will find some threads about it, one guy got pretty far with iOS, not sure anyone has tried Android.
@@DHealey Thanks, I'll check out the forum. :)
@@DHealeyhise itself works on linux, but can it export linux compatible plugins?
Also are exported Ajax and vote plugins m1 native on Mac?
@@dfhm-pq2cf Yes
I have followed every one of these steps to the letter and I am getting all kinds of Juce errors upon compiling it. Can you tell me what I ma doing wrong or is this video outdated given the components used now?
I'd need to see the errors. Please make a post on the HISE forum.
found the forum but I noticed in the HISE-master folder in SDK that the zip needs a password? Can I have that?
@@gryphonsegg You need to use the develop branch, not the master branch
👏🏻👏🏻👏🏻
thanks for this video, but what a complicated installation process omg
The majority of it is a one time thing, after you have the system setup all you need to do to update to the latest version of HISE is grab the latest source code and recompile. Some development environments can be a lot more cumbersome to maintain.
ok
Ok, figured out the IPP build issue. For me it was finding but was not finding or . I traced through what ipp.h was doing. It actually ALREADY INCLUDES all of the other .h files needed by IPP. So here's what I did:
In PostGraphicsRenderer.cpp
#if USE_IPP
#include
//#include
I believe a similar solution was posted recently on the forum