Starting to use HISE is one of the biggest pains in the neck I've ever had
-
@gorangrooves It's just that I wish there were an alternative where I can just kind of hop in and learn building an instrument, not building the software to make the instrument in the first place. Like, say, Kontakt for instance. But I'm not a fan of Kontakt.
I did learn of something called Linuxsampler which extends the SFZ format with KSP-like scripting called NSKP (aka not-KSP) but I have no idea if it's actively developed. It probably isn't as flexible anyway.
We'll see how far I get if my motivation ever comes back.
-
@AudioHobbyist I feel you. I also wish the process was much more straightforward. I think the main reason why the website is outdated is that Christoph doesn't have the time to update it. He is single-handed building this incredible platform, so that doesn't leave much time to update everything. I can also totally relate to that too.
The thing is that in order to compile plugins, you need to utilize the source code of HISE and JUCE. And all of that has to be hooked up and working perfectly with Visual Studio and/or XCode. Even then, when you expect that 2+2=4, you actually get 2+2=3.48735 and then headaches of trouble-shooting.
Have you checked out HalION by Steinberg? I think that is a much better option than Kontakt. End-users can download LE version of the software for free, which can load your completed Library. You can also design the GUI right inside the HalION. It is the next best thing to building your own plugins in HISE.
-
@AudioHobbyist Why not start with the older version which is ready to go?
Have a play around. You can do loads with it. You might decide it's not for you, and then you've saved loads of time not having to compile the scriptnode version. You'll have a plugin ready to use extremely quickly I reckon, I did, and eventually moved to scriptnode after researching the compiling process thoroughly (and posting a few qs on the forum!)
The extra stuff in the scriptnode branch is quite advanced (mostly). Cross that bridge if and when you get to it.
-
@gorangrooves said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
The thing is that in order to compile plugins, you need to utilize the source code of HISE and JUCE.
Makes me wish the HISE player wasn't dropped! But if you get far enough to compile HISE in the first place...
-
@DanH I just worry about bugs, mostly. And scriptnode being advanced as it may be, I'm not a stranger to tinkering with more complex things - it's just the whole compiling process draining my energy.
-
I wouldn't start with an older version. Start by compiling, once you can do it successfully you'll be able to export your own plugins from HISE, you can't do this using a pre-built version.
Something else you might want to look at is Decent Sampler - https://www.decentsamples.com/product/decent-sampler-plugin/ - It's not Open Source but it might be flexible enough for your use case.
And that call + screenshare offer still stands.
-
@Rudra-Ghosh That may be, but if you want to build HISE you should use 2017, and you should not update the projucer application that comes with HISE.
-
@Zorpley I don't use Projucer Application that comes with HISE.
-
I am using the JUCE that comes with HISE, and I've done the following:
Uninstall IPP completely, and Intel OneAPI
Set the "use IPP" flag in HISE to 'disabled'
Use Visual Studio 2017 with the correct Windows SDK installedI'm still getting the exact same error, which is as follows:
Error C1083 Cannot open include file: 'ipp.h': No such file or directory (compiling source file ....\JuceLibraryCode\include_stk_wrapper.cpp) HISE Standalone_App [...]hi_streaming\hi_streaming.h 69
(repeated 20 times over for different parts of HISE, all saying ipp.h is not found)
Warning C4068 unknown pragma (compiling source file ....\JuceLibraryCode\include_hi_zstd_2.cpp) HISE Standalone_App [...]\hi_zstd\hi_zstd_2.cpp 1
(repeated 3 times for similarly named files, like hi_zstd_3.cpp)I'm just terribly confused at this point.
-
save and open in IDE (vs2017)
-
@ospfeigrp That seemed to do it, thanks.
For some reason that extra flag is not mentioned in the github readme. It looks like I'd have to use an old IPP installer someone else posted here to get that to work, unfortunately, since Intel changed everything.
Hopefully the developer figures out the best way to get things going with newer versions, because relying on third-party downloads of old software isn't the greatest. Or most reliable.
-
@AudioHobbyist said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
@ospfeigrp That seemed to do it, thanks.
For some reason that extra flag is not mentioned in the github readme.
Yeah it's weird, the option in hi_core should be all that's needed but for some reason we have to also set the flag in the extra definitions too.
-
@Rudra-Ghosh You should use the Projucer application that comes with HISE.
-
The one thing that HISE does really well, force you to give up and go back to using Kontakt, SM/SE etc, I have brought up these issues before, but teh website still never gets updated, and unfortunately that means that just getting HISE set up before even doing any design is "The journey to the sorcerer" it feels like some nice side project for people who are just bored with using full JUCE, sadly not the goal the developer was aiming for.
-
Alright, you heard the man. Party's over, let's go home...
-
@Win-Conway said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
The one thing that HISE does really well, force you to give up and go back to using Kontakt
I started tinkering with HISE in 2016ish and had to move on cause I didn't fully understand what I was doing. Ended up making my library in Kontakt. After that, I started playing with C++ & JUCE and eventually found my way back to HISE.
Now that I know it's more of an extension of JUCE, I'm very thankful for the effort @Christoph-Hart puts into HISE. -
@Win-Conway said in Starting to use HISE is one of the biggest pains in the neck I've ever had:
force you to give up and go back to using Kontakt, SM/SE etc,
I think SM/SE can't even be in the comparsion list because of the ended support and ended updates (No AAX & VST3, Windows only and I don't even know 64 bit support has been arrived or still not yet in 2021!) In short, they are already dead platforms.
I am sure Hise will be one of the best audio plugin development platforms after the forthcoming SNEX engine. Because it will open ton's of possibilites. And also it will open much more joyful part of the SM/SE platforms. Yeah this transition might be painful like giving birth of a child, but it will definately worth :)
Thanks to @Christoph-Hart for building his miracle ONE MAN ARMY platform and thanks to the other contributors for this platform....
-
force you to give up....
If anyone gives up that means he/she is not ready for programming or developing audio software in any framework. The goal of a good developer must be always swim against difficulties and overcome it. There is no word for ''Give Up".
Be like ROBERT BRUCE
-
It's painful to setup and compile.
-
@AudioHobbyist Absolutely True.
