When is HISE going to properly update and address their site & documentation? I check it every 6-12 months and it's always a little lacking. For example, there is no obviously-available feature list. It would make sense to detail what you can do with HISE. Custom DSP? Custom filters? Native code? Efficient disk streaming? Multi outputs? How about a comparison to Kontakt in terms of features? This should be clearly listed on a single page.
Next - all 5 tutorial links in the navigation are broken. The pages have a PHP error. A variety of documentation pages are either confusing or broken.
For example, this page has a missing explanatory image. Also, the layout makes little sense. I don't understand what the author is describing. The "Summary" part should be at the top. If I click "ScriptNode" I want a basic overview explanation of what that is, and some practical examples of how I might use it. I've read the page and I still don't get it.
Official HISE documentation
docs.hise.audio
The ScriptNode manual page is missing:
Official HISE documentation
docs.hise.audio
This page talks about a "scriptnode graph". What is that? Hmm, maybe I can check the glossary. Oh wait, "graph" is nowhere on this page or in the navigation. Also, this page is full of broken images.
Official HISE documentation
docs.hise.audio
I'm interested in the Wavetable Synthesizer module. The page on it describes next to nothing about how it works or how to use it.
Official HISE documentation
docs.hise.audio
Some pages have incomplete sections, like the Slider page. What is Filmstripping? I don't know. It's blank.
Official HISE documentation
docs.hise.audio
The examples area has some interesting stuff. But while a 1Band Dynamic EQ is fine, having only a single DSP example given the staggering amount of DSP possibilities out there, seems very sparse. I'm sure a HISE expert could cook up 4-5 more examples of things like... subtractive synthesis, a filter model, distortion model, or other very common DSP applications.
I'm certainly interested in HISE but it would be really nice to see these things addressed. I'm sure a lot of developers are tired of Kontakt's limitations and interested in a potentially superior option. Taking the time to at least ensure features are documented and presented correctly would probably do a lot to convince people to come over.