@d-healey No... I said they are based on waveguide synthesis. For example, the Audiomodeling website straight up says that about their SWAM strings. Based on waveguide synthesis. Karplus-Strong is just a simple, early form of waveguide synthesis.

@christoph-hart Oh, I should've thought of pitch modulation. Duh. By the way, was the wavetable synth ever updated? I remember you were working on a tool to help turn crescendo samples and such into wavetables. I find myself needing access to such things the more research I do. On a side note, is it possible to perform pitch bends interpolating between all the pitches represented by a wavetable?
@hisefilo I think the hnode thing that Christoph was working on might be what you're looking for, but it's not out yet. I'm also highly interested in that for my purposes (imitating acoustic instruments via synthesis).

@remarkablex I see - I guess I got confused because this doesn't seem to be required in VST instruments.

After adding another routing matrix and doing so, everything works out like it should. Thanks for the explanation.

@Christoph-Hart Well, suppose it's time to start another attempt to learn JUCE. Thanks for all the info; I wasn't even aware that documentation existed!

@Christoph-Hart My thoughts exactly, it just seemed pretty hacky. I wouldn't know where to even begin on adding C++ code to a HISE project, I'm honestly very new to working with open-source software of any kind, but that seems to be the solution - JUCE's SharedResourcePointer thingamajig. I've worked with code before, including C++ (not that I remember much of it because it's been so long), so I'm confident I could learn, but I haven't got the foggiest clue where to start. Or even where the C++ would get put, I don't know if HISE itself has support for C++ or if I'd need to do that within JUCE.

I noticed that when all instances of the plugin are closed the memory shared is deleted - but is there a way to do that when a single instance is closed? Just deleting the data that plugin was contributing? I assume there is, but I've not worked with JUCE before at all aside from a brief attempt.

@Lindon As interesting as it is, that solution would be hard to work into anything more than a personal use plugin, unless there's a way to detect if plugins are loaded in different project files in order to create 'channels' as lined out in the above experiment. Maybe I should check some JUCE forums to try and see what other people might be trying.

Well, that was an educational attempt at the usage of json files. But I can't help but wonder if there's a cleaner, more 'proper' way to do this. One less prone to bugs rising up from working on multiple projects.

Maybe @Christoph-Hart can chime in before we go too far and start designing an even more convoluted solution...

@d-healey That's an interesting idea. The file would need to be re-written and re-loaded any time the project in the DAW is loaded, or it would somehow need to be able to be saved with each project.

Example data would be things such as stage positioning, early reflection strength, which stage every player is being set in - that data would need to be polled with a timer, I think. I worry that using a timer would affect performance when doing absolutely nothing. I wonder if there's a way to only poll while the VST's GUI is open... but then again, that wouldn't work for shared data that isn't purely visible. It seems like implementation of that could get incredibly messy. That's also just examples from VSS2, which is one of the few plugins I'm aware of that communicates with its other instances.

I'm pretty sure VSL's software uses some kind of LAN network. I know VSL's sample players share loaded samples with each other - if you load the same patch on two different instances, the sample pool is actually only loaded once. It's hard to actually tell how that all works, and the answer is probably proprietary, which is frustrating.

I can't remember if I asked about this before, but -
There are some examples of plugins that network with each other somehow out there. For example, Virtual Sound Stage 2 is able to display the stage position of every other instance of the plugin, as well as synchronize certain settings, such as which hall has been chosen. I think VSL's MIR does this too.
How does that work? Does it use LAN networking? Does HISE have any similar capability, and how would I approach doing that?

@d-healey My build succeeded with that one, so it's definitely a scriptnode-specific problem... Frustrating that I can't use the latest version, but whatever. I suppose I'll try again in a month or so when Christoph releases 3.0 (that is what he said, right?)

@d-healey I have no idea which branch is actually the stable release anymore, which one is it?

As far as I can tell, everything is arranged correctly, including the SDK files. I am trying to build HISE again because my last build keeps randomly pressing a specific MIDI note for no reason, while I'm testing the instrument, which is incredibly annoying.

While building in Visual Studio 2017 I get these errors:

I'm not very experienced in having to build GitHub projects, so I have no idea what to do here. The trouble of having to build HISE makes it pretty annoying to use, but it's the only tool like it. Grr.

@hisefilo I checked it out, it definitely allows for more detailed shaping, although I have to do all the shaping in the attack phase. Still seems that if I release the key before the note is fully built-up, it stops right there and ruins the effect. I can filter out all note-off events, but then I wonder how to add a choke key. I also worry about the CPU hit, if the note continues playing silently - I shall have to experiment more.

Tl;DR that seems like a step in the right direction, thank you!