With the mod matrix system each connection can have a intensity and you should also be able to set it programmatically without the matrix floating tile using the API.

For targets that dont expose a mod chain you can just define a UI knob and give it a matrixTargetId. You‘ll loose the precision of the real mods but if it‘s acceptable then fine.

The modwheel could also be a global source modulator using a control modulator.

@observantsound Confirmed here on Linux

@observantsound You can use both references at the same time. Just use the one that works for the bypass, and the other for your sampler job

What I said might work, but do as @David-Healey said it's better implementation even if the reference are the same behind the scene 👍

@David-Healey Yes the Global Modulator Container worked beautifully for this.
Thanks to your video I've now also understood the global modulator container better.

Regarding the body + release in one sampler:
That's what I've tried first, but it's bugged when using together with loop regions.
It's what I described in this earlier post you commented on:
https://forum.hise.audio/topic/14799/loud-click-artifact-when-using-releasestart-with-looping-enabled/14?_=1781354181861

I haven't gotten around to testing it with 48kHz samples yet.
But by now I've found enough use cases to split apart the sections into dedicated samplers.

@observantsound said in Usinge the same sample files in two different sampler links them when editing.:

Is this a known bug?

It's by design.

@observantsound It's probably something to do with how the stretching algorithm works. I also noticed your sample is 44.1kHz, 48 might produce better results.

@d-healey Using the txt property seems like a nice idea.
The video was also helpful. Thx!

@observantsound
What about automatically setting the root for factory samples though?
It seems like I can either do set root automatically OR use the token parser but not both... : / ?

Maybe I do it like this?
Drop everything in, detect root note automatically, export sample map as xml, then process the file to set each sample in its own group?

@observantsound

Here's a partial list showing the sort of thing I (and it seems David) do:

// THE SOUND SOURCES include("VoiceModels.js"); // LAF // include("LAF.js"); include("PatternPreLoader.js"); // THE HEADER CONTROLS include("HeaderControls.js"); // MASTER CONTROLS include("MasterControls.js"); // EDITOR CONTROLS include("EditorControls.js"); // REALISM CONTROLS include("RealismControls.js"); // THE STD CONTROLS // include("StdControls.js"); // SAMPLER AREA include("Samplers.js"); // SYNTH OSCILATOR AREA //include("Synths.js"); // ENVELOPES AREA // include("GainEnvelopes.js"); // FILTER AREA // include("Filters.js"); // FILTER ENVELOPES include("FilterEnvelopes.js"); // TREM VIB AREA include("VibTremSpace2.js"); // UNISON AREA include("UnisonSpace.js"); // CONTROL AREA include("ControlSpace2.js"); // FM AREA include("FMSpace.js"); // LOOP PLAYER //include("LoopPlayerAndBrowser.js"); // THE FX AREA // include("SendEffects2.js"); include("MasterEffects2.js"); //include("update.js"); // the ARP include("Arp.js"); // the CHORD PLAYER include("chordplayer.js"); /// the RANGE SETTERS include("RangeSetters.js"); // SETTINGS // include("settingsspace.js"); // SOUND BROWSER // //include("SoundDataLoader.js"); //include("SoundBrowser.js"); include("VoiceExpansions.js"); include("voicetaggingSelector.js"); // SOUND randomisation include("SoundRandomiser.js"); // Authorisation & Demo include("Authorisation.js"); // THE GLOBAL MODULATORS // include("GlobalModulators.js"); //PRESET BROWSER include("PresetBrowser.js"); include("presettagging01.js"); //PATHS include("Paths.js");

@DanH same result...

@d-healey @observantsound I'll try recent commits if something has been fixed or there's a feature I want to test / implement. But otherwise, for existing products, I'm super cautious about exporting updates with brand new commits - learn't the hard way that unless you fully test your plugin with a new commit you can't be sure your plugin will work.

Ok followed Davids instructions and built Hise from source on Windows.
Was honestly much easier to do than on Mac even though David said otherwise in his video.

Visual Studio seems clearer than Xcode, and the fact that both SDKs are already in the git folder makes it easier as well I think.

Ok good to know that the whole auto complete is a bit inconsistent.
So it's not just me doing it wrong!

@observantsound no it will be useful for people asking the same question

@observantsound well every single line of code in HISE prepares something for you that would be difficult to achieve in JUCE so just pick whatever feature set you will use in HISE.

Ah yes, indeed a typo. Embarassing!!

Makes sense that some built in functions only work with certain target types.

Thanks!

Custom popup is the way:

This video is for a lottie panel but same process applies (1:39).

https://youtu.be/5aFbxEY2eRQ?t=99

@d-healey thank you, that just helped me too.