@d-healey
https://docs.hise.audio/working-with-hise/project-management/expansions/index.html#features
Under 'active expansion'
It's the first result after searching 'expansion' in the documentation

@ospfeigrp That seemed to do it, thanks.

For some reason that extra flag is not mentioned in the github readme. It looks like I'd have to use an old IPP installer someone else posted here to get that to work, unfortunately, since Intel changed everything.

Hopefully the developer figures out the best way to get things going with newer versions, because relying on third-party downloads of old software isn't the greatest. Or most reliable.

This is coming from the perspective of someone who's never had to deal with compiling from source just to tinker around with samples and put together instruments, to be fair, but I'm at my wit's end here. And pardon me if the title comes off as rude, I just feel frustrated.

Firstly is that the current 'release' of HISE is well out of date, which means, from what I read here, is that it's recommended to compile it from the scriptnode branch. Which is mentioned NOWHERE on HISE's website (except that it's recommended to compile it yourself, with NO mention of which branch to use...) or readme, by the way.

So I go put together the dependencies, which is also slightly unclear; the process isn't exactly lined out for the inexperienced. Apparently I have to put SDKs in tools/SDK or something. And then I install Visual Studio (2019 specifically, because I couldn't find 2017, which is what the JUCE included with HISE asks for? apparently?), though I'd love to avoid literally anything that forces me to sign in to continue using it, because I can't make heads or tails of how to compile it without that despite hours of searching.

And it has to 'retarget solution' or whatever, probably because I was trying to use 2019. Okay, I do that, and all I get are errors no matter what I try changing, so I've pretty much given up now. I can't help but think; are there any like... alternatives? I don't like Kontakt much (and it's a proprietary platform that I consider anti-consumer) and SFZ is relegated to text editors and a single player from Plogue that doesn't allow custom interfaces still.

I'd love to use HISE, but honestly, it's just the complete opposite of user-friendly so far. I haven't even been able to THINK about starting to use it yet, despite additional hours of trying to put things together (not including my search for alternatives to using Visual Studio), and everything documented is obscured - behind having to search this forum - at best, as far as I can tell.

Aside from alternatives for someone like me, is there something I'm missing that'd make my experience much easier, here?

EDIT:
Oh, and it seems that the install process for Intel Performance Primitives is different from what the readme is expecting. Because I ended up installing something called 'Intel OneAPI' or whatever, and selecting IPP from there. And most of the errors thrown at me in Visual Studio are from files titled 'ipp', so that might have something to do with it?

@d-healey JUCE 7 only added official support for LV2. CLAP support is not yet official. They also have yet to add any support for Wayland, which will become a problem soon - Linux DAWs are starting to consider Wayland support, as evidenced by PreSonus' beta release. VST3 GUIs straight up do not show up as of right now.

@tobante Interesting, I didn't know HISE made any modifications to JUCE. Is there any developer documentation, for would-be contributors?
LV2 or CLAP, anything to get away from Steinberg is a welcome change; I don't really care which one takes precedence, but official JUCE support tends to work way better than any third-party patches anyone makes.
The Linux world is starting to make the final strides of a really big change from X11 to Wayland, too, so keeping up to date is an absolute necessity in my eyes. I'm even aware of one DAW that has made the move to Wayland, which is REALLY unusual.

I'll be waiting for that blog post.

It has been around (or over, I didn't count exactly) a year since this was last mentioned.
JUCE 7 adds support for a plugin format that has some wider adoption lately; this was one of the main reasons it finally got added.
Christoph appears to believe CLAP will be the format that wins out, which is fine, but JUCE themselves would have to add support for that too - which would again mean updating to a newer version of the framework. I think it would cause less technical debt to keep up-to-date with JUCE in the meantime.
In addition, I believe they have been slowly working towards Wayland support on Linux, such as decoupling X11 windowing code - this WILL have to happen eventually.
Is there any reason there's not been much movement here?

@d-healey
Interesting. Is there no way to access data from the extension's host?

@d-healey
I'm afraid that doesn't exactly clear up my confusion - is that from within the full extension or from the plugin hosting the extension? As in, does the extension have to have the feature to unload itself with a button, or does the plugin have to provide that?

My understanding so far is that it overrides EVERYTHING that was originally in the project.

Just had another thought - if a full expansion essentially replaces everything else going on in the project, how do you 'reset' things? For example, if you want to load a different expansion?

@d-healey
This begs the question whether full expansions can have smaller sub-expansions.

@d-healey
https://docs.hise.audio/working-with-hise/project-management/expansions/index.html#features
Under 'active expansion'
It's the first result after searching 'expansion' in the documentation

@d-healey
'no different than any other expansion'
The documentation on expansions implies otherwise - what's the deal with that?
It explicitly states multiple can be loaded, but there is the concept of an 'active expansion'.

There's documentation on expansions, but nothing about 'full instrument' expansions - how they work, whether you can load multiple at a time, how that works with saving parameters (as in when the project in the DAW is saved)

Do they just override everything already present, or load in a new container, or what? Somewhere on D. Healey's channel I read he planned on releasing a video about this, but that doesn't seem to have happened yet.