Starting to use HISE is one of the biggest pains in the neck I've ever had
-
I officially give up. Visual Studio 2017 turns up the exact same errors, and I had to complain on a forum to be indirectly redirected to an obscure video to be redirected to an obscure thread on this forum that has an obscure link to finally reach the download.
First of all, right off the bat in both versions of Visual studio, I always got "Windows SDK version not detected, retarget the solution" or something, which I do, which tells me which version I might have, but which doesn't seem to actually change the output... get the exact same errors, so I go into the project properties and manually change it. Fun. That gets rid of that error.
But now on both versions, this is what happens: 20 different errors of 'ipp.h' is missing. I tried disabling IPP, though I'd like to use convolution. Exact same errors. -
..As you see I use VS 2019 with JUCE 6.0.7 (since I develop plugins in JUCE too)
Use the latest Scriptnode..with the Intel Performance primitive.
See the sys requirement for IPP.
https://software.intel.com/content/www/us/en/develop/articles/intel-integrated-performance-primitives-intel-ipp-2020-system-requirements.html -
-
@Rudra-Ghosh said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
Use the latest Scriptnode..with the Intel Performance primitive.
I appreciate that you're trying to help, but I'm sorry - this doesn't give me any hint as to what's working for you and what's not working for me. I have IPP installed. I have nothing outside of IPP's requirements. I placed the SDKs in the correct folder. I tried using VS 2019 and VS 2017. I am using the latest version of the scriptnode branch. All I can tell is that it works on your computer, for whatever reason.
-
@AudioHobbyist show me your error details
-
-
@Rudra-Ghosh Like I said, it turns up ~20 'ipp.h' files completely missing. Whether it's 2017 or 2019. I've been trying all day and it's gotten late enough that I should go to sleep, so I can't try again to get another log to paste here.
I have no idea what I can glean from those screenshots. -
@AudioHobbyist use..ipp v2020.3 or 2020.4
-
@Rudra-Ghosh The only way to install IPP now does NOT let me select a version.
-
@AudioHobbyist Get a sleep now.....do a fresh start tomorrow. :)
-
This is the version working at my end...2021 January version should work too...
-
@AudioHobbyist said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
This is coming from the perspective of someone who's never had to deal with compiling from source just to tinker around with samples and put together instruments, to be fair, but I'm at my wit's end here. And pardon me if the title comes off as rude, I just feel frustrated.
This is the first stage of becoming a HISE user. We've all been there.
For the simplest build use Visual Studio 2017 (via the obscure forum link - thanks Microsoft!) and build without the IPP. I haven't been able to get the latest version of IPP to work with VS2017. Unfortunately Intel prevents us from downloading earlier, compatible, versions of IPP.
Once you have Visual Studio 2017 installed and you've removed IPP things should be smoother. If you're still struggling let me know and we can get in a call with screen sharing and I can walk you through it.
You've also got more fun to look forward to with setting it up on a MacOS system.
-
@AudioHobbyist As @d-healey says start without IPP.
However, if you do want it later here's the last installers I downloaded last year which worked with VS2017 / XCode 10.3:
DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
https://dhplugins.com/ | https://dcbreaks.com/
London, UK -
@DanH That was a smart move! Thanks
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey Yeah I figured I'd keep hold of them just in case!
-
@DanH Life saver. It's completely insane of Intel to have removed the old downloads.
-
@Rudra-Ghosh I agree, HISE is not easy to get started with, but once you get over the initial hump it's much nicer. For this particular issue, do not retarget the project, but rather add the correct SDK version to Visual Studio. The version it's looking for is 10.0.16299.0.
You can add the SDK by running Visual Studio Installer, clicking Modify by Visual Studio 2017, then going to Optional, and checking it in the list.
Hopefully we'll improve the docs soon, at least to remove conflicting information.
-
@Zorpley No... I have VS 2019. I don't use 2017... And I have SDK 10.0.16299.0 installed.. look the GIF... it's 2019.
-
@Rudra-Ghosh I believe I had quite a lot of trouble with 2019 and never got it to work. Installing 2017 is the way to go.
-
@Zorpley For my case it is just opposite. I don't know why.. but somehow 2019 works perfect for me with JUCE 6.0.7
