I am trying to build it on Ubuntu and create a package, need help
-
I followed the instructions on the readme and realized it is more involved than expected. If I manage to build it, I'll try to create a Hise Ubuntu package and scripts so it can be made part of the regular release cycle, but I need help. Can someone with experience guide me?
-
@javilon you'd need to be updating the package every few days to stay up to date. Also users still need to be able to compile HISE to be able to export their projects.
-
@d-healey About updating every few days, I guess you mean update it with every new release. That most likely could be done with a script that builds the new .deb package after compilation, right? And about the need to compile in order to export projects, I have this question: Is HISE meant to be only used to create and export instruments or is it also meant to be used as a general sampler where you load up a patch inside HISE in the same way you would do to Kontakt and use the sound? Because in that case a .deb package would be extremely useful for Linux people that usually don't have many options for modern samplers.
-
I guess you mean update it with every new release.
If you're talking about tagged releases then no. HISE rarely gets a new release. But it is updated every few days on the develop branch and that's what pretty much everyone is using.
Is HISE meant to be only used to create and export instruments or is it also meant to be used as a general sampler where you load up a patch inside HISE in the same way you would do to Kontakt and use the sound?
HISE is like an IDE for developers to use to create plugins/apps, it is not end user software like Kontakt. However it is possible to build HISE as a plugin so you could run it in a similar manner to Kontakt but there will be performance issues since the projects won't have been optimized and compiled.