Is this expected behaviour?

@orange That simply isnt true, SE is 32 bit/64 bit/VST3 and AU.
Synthmaker is updated on a near weekly basis, but is a hobby project now of one of the developers, not a real commercial enterprise.

It is very sad that any comments by people struggling are met with the kind of comments shown here though, sarcasm and elitism do nothing at all to grow the userbase, and my comment stands as fact, a LOT of people have picked up HISE, messed with HISE, gone straight back to Kontakt, just because you do not like that fact, does not mean that it isn't true.

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.

https://docs.hise.audio/introduction/{LINK0}

https://docs.hise.audio/introduction/{LINK1}

https://docs.hise.audio/introduction/{LINK2}

https://docs.hise.audio/introduction/{LINK3}

https://docs.hise.audio/introduction/{LINK4}

https://docs.hise.audio/introduction/{LINK5}

There you go, as i said, try the links, that is the links in the documentation installation page to the GIT, to the compilers, to Steinbergs website, to intels website.

Pretty much the first thing that any new user is going to try and do, install.

No of the links work, just go to the very start of the documentation, try to go to the git or the compilers, you aren't going to get many people on board with broken links everywhere, I know it is more important to work on HISE itself, but honestly, basic stuff like that needs to be right.

@d-healey said in PACE (iLok) have acquired JUCE:

proprietary

Well, commercial is generally the point.

@d-healey said in PACE (iLok) have acquired JUCE:

GNU GPL

Yes but if they stop selling the licences for the current codebase, you cant use it to make commercial plugins, right ?

I doubt very much that they don't intend to push heavily and/or even force iLok usage, it could even be as simple as "JUCE is now free to developers, but you have to use iLok" acquisitions are made to make money, and if the business of iLok is more valuable than the business of JUCE (Which you would have to assume it is given they where able to procure JUCE) then JUCE will be used to leverage more iLok business.
How much this affects HISE in the long term is debatable, I would have to assume that Christopher already has back up plans and such if anything nefarious was to happen with JUCE, there are alternatives for him to implement if he needed to.

https://juce.com/discover/stories/juce-announces-acquisition-by-pace

Have to see how this one plays out, but i would expect some changes to JUCE licencing.

This has been requested for a long time, a VSTFX version of HISE for making effects.

Broken image links, look under scriptnode/performance for example.

A lot of the Next:.... at the end of a section are completely wrong, they point to the wrong next section, example project management/projects folders (2)/Binaries points to audiofiles via next, next is actually images.

A lot of it is poorly formatted too, @Christoph-Hart do you want give me a log in and i will start to tidy it up, things like...
Minimize Colorpicker processor ID Mute Meter Routing Matrix Gain Pan and Delete
are much easier to read as
Minimize/Colorpicker/Processor ID/Mute/Meter/Routing Matrix/Gain/Pan/Delete
Just a simple example of tweaks.

I can fix any broken links too.

All the links on the 'Setting up VST/Plugin compilation' page are broken.
Will list whatever else i find as I read through.

Also is there an option to change the .ch extension to something else, so you would set it per plugin, I know from experience that some dope somewhere will notice that all HISE plugins use .ch and starts trying to swap the files out with this that or the other hahaha.

@Christoph-Hart unless you want your users to have access to the wav files for direct use, so using wav compromises performance ?

@d-healey this doesn't make sense to me, a non lossy format would have to be uncompressed to wav and use the same RAM, a lossy format would be lower quality and wav is just better in that case (Disk space is of little interest to me to be honest)

Whats a ch1 file ?
Can't expansions just be the individual wavs ?

This definitely needs theming options moving forward, UI sizing options are going to become more common as screen sizes and resolutions get ridiculous.