Adding External FX Libraries to the HISE source code

[HISEnberg]

Does anyone have experience doing something like this?

Currently I have a handful of libraries I pull from (MIT mostly) and I integrate these directly into a HISE project. However, a more seamless workflow at this point would be to include them into the HISE source code and just use Projucer flags to include/exclude them depending on the nature of the project. That way I can organize them in Scriptnode according to their source, or include them when working on my C++ nodes as I have been doing.

I'm just curious how much extra labour it will be and if it is worth pursuing. I suppose this would compliment the HISE store concept Christoph is working on?

[Christoph Hart]

@HISEnberg don‘t do this - the entire c++ third party node system gives you a robust and established way to pull in third party code through a well defined interface. What do you want to do that isn‘t possible there?

[HISEnberg]

@Christoph-Hart Basically I just want to be able to centralize and organize my workflow, but if it's going to cause more issues then I won't bother. It's true the third party system offers most of what I need.

Currently I may have 5 projects which all use xyz-github repo, meaning I copy the files from this repo into the HISE project. It would be nice to keep them in a central location and just add them into HISE as necessary.

But now I am seeing the potential weakpoints: if the xyz-github repo is updated then I now have 5 projects that could break if it is updated instead of just one. I also realized I can just do this in my HISE project if it really is a big concern (#include CentralFilLocation//xyz-github repo)

Other than that there are small UX things I would want control over. First is not having to recompile nodes which are already complete. In Scriptnode it would be adding a tag for which library the node comes from (instead of just project). Likewise if the combobox had subcategories it would help organize things a bit. Probably a leftover remnant of my MaxMSP days where you could install external libraries from other developers. :)

Note too these are fairly petty requests and really come from the perspective of th discovery phase (do I want this compressor or that one, this model of saturation, etc.). Not the development phase (I always just extract what I need).

[David Healey]

@HISEnberg said in Adding External FX Libraries to the HISE source code:

Currently I may have 5 projects which all use xyz-github repo, meaning I copy the files from this repo into the HISE project. It would be nice to keep them in a central location and just add them into HISE as necessary.

You could add it as a submodule to each project, or perhaps it will work with the global scripts folder.

[Christoph Hart]

Ah yes this is exactly what is supposed to be adressed with the HISE asset manager - it‘s basically a poor man‘s git submodule to load in / include another HISE project.

[HISEnberg]

@Christoph-Hart Nice you are always one step ahead. I'll wait for the asset manager then! In the meantime I'll learn a bit more about submodules in Github as @David-Healey suggests.

[ustk]

Coming right on time (well, when ready...) as I am to release a set of plugins based on the same engine so if fixes and updates can be done just once for the bundle I can already see the benefit of this!