Last time I checked you couldn't instantiate more than one PD instance, which is a knock out criteria for anything that wants to run as plugin, but I heard there were some efforts to remove this restriction.

When it's there, I'll think about a PD wrapper for HISE. It might be pretty great desigining your DSP in PD and wrap them in a HISE instrument.

@christoph-hart It is a bit like regex in the fact that it is very powerful what you are able to do with very few characters of code. Its actually quite brilliant, it just takes a bit of getting used to because it is a shorthand textual representation of dataflow networks like pure data or max/msp.. you can split signals with < (think of the less than being like to wires splitting out visually) and then you would have the processes separated by commas.. and to sum together a group of parallel you would use the >.. and the "~" represents feedback for recursive z-1 filters etc.... @10 would get the memory at 10 samples ago.. delay lines etc.. it makes alot of sense if you can happen to find a good tutorial.. I have a bajilion things bookmarked for faust and there are a couple getting started guides in there but you can probably find most of what I looked at from their website and github repo readme

The problem is building LLVM and faustlib, but then it it should be pretty straightforward. It will probably only be available on macOS / Linux though as building LLVM on Windows is the Bowser of software development.

The idea is to have the JIT compiler available in HISE for rapid development and it when you export your plugin, the faust compiler will create C++ files that are embedded in the plugin so that the exported plugins have no dependency on Faust (Faust is GPL but the generated code inherites the license of the used libraries, so it plays nicely with commercial projects.

Do you know how polyphonic synthesisers work in Faust? Since HISE is a framework for virtual instruments, it would be pretty stupid if it couldn‘t use Faust for making sound generators.

@christoph-hart a bit off topic but I've been playing around with csound also, and it's polyphonic by default. Opcodes included in csound are in fact modules that would be great for hise. I mean you can load for example the 'pluck' opcode and it's a fully functional Karplus strong module http://www.csounds.com/manual/html/pluck.html
There are 1500 opcodes LGPL out there

Very exciting to have the power of Faust DSP connected to a sample engine/ plugin generator/GUI powerhouse! Keep us posted, this is very interesting!

In regard to polyphony, with my experience its very easily implemented inside Faust code using nvoices, however I don't know the exact way it works inside the compiler. Currently it's similar (in my eyes) to how csound does polyphony. (It "just works").

In regard to including Csound (and this is a cool idea) I feel that especially for physical modelling having access to the DSP code is much more flexible than using an opcode. Mind you currently Faust isn't the best for FFT resynthesis, (hopefully it will get that soon).

I'm not a Windows user, so can't comment on LLVM for that platform, mainly Linux, MacOS. (Addicted to POSIX).

@christoph-hart I think it would be a very BAD idea to build functionality into HISE that cant resolve to plugins that work across all platforms, sure (as I understand what you are saying) you might have some facility ONLY on the Mac platform that generates the C++ from Faust, but then there needs to be a way to "import" that C++ into HISE on any platform.

The macOS limitation only applies to having the JIT compiler embedded into HISE as Development Tool. When you compile the plugins, the faust compiler will
generate C++ files that are natively compiled on every platform.

So in order to develop DSP in Faust you need a Apple computer but the generate plugins will run everywhere (everything else would indeed be very stupid).

This being said I am trying to get the windows build done too - I am doing the majority of work on windows so it‘s rather selfish