@Oli-Ullmann I reached out to Ableton last year for a NFR copy of Ableton 12 to test plugins and they were more than happy to accommodate me. Worth a shot ;)

@dannytaurus There are methods to force your own order:

UserPresetHandler.setPluginParameterGroupNames(Array pluginParameterGroupNames) UserPresetHandler.setPluginParameterSortFunction(Function customSortFunction)

@dannytaurus I've just hit this problem for the 100s time a couple of days ago and it alway melts my brain...

What I do is to force "init" in the postCallback when the presetFile is undefined, meaning it's init time...

Another way could be to save the label in preset, but this only brought me more pain down the line

@observantsound You can use a global modulator for this I think

https://youtu.be/Y2XhAEE1IBI

Also you can use a single sampler for sustain and release - in most cases. I posted a video about this on Patreon recently: https://www.patreon.com/davidhealey/posts/how-to-create-156513314

@Bart I was testing with Win10. I've just tested on a fresh install of Win11 using the free trial of FL Studio, not sure if it's the same as the beta version, probably not.

Again no crashing here, I'll see if I can find some other FL Studio users to test.

@brucerothwell said in HISE 4.1: Obtaining Peak/RMS Values from Script to a Scripted UI Meter?:

Can external DisplayBuffers be accessed from scripting, or are they intended only for AudioAnalyser / visualization components?

I don't know, I haven't used them.

@brucerothwell said in HISE 4.1: Obtaining Peak/RMS Values from Script to a Scripted UI Meter?:

I have, however, figure out how to use the MatrixPeakMeter, and see that responding to audio.

The peak meter floating tile can be styled using custom look and feel to apply your filmstrips (search the forum, there are examples showing this).

@zachhealy1005 said in Linux:

If I go to my home folder and delete the hise folder is that actively deleting the hise source code from my computer

Yes. And remove any other copies you have too in the same way.

@zachhealy1005 said in Linux:

I'm just curious why is it that you have to compile it?

I thought I explained this above and I covered it in the course. When you "export" from HISE what is really happening is HISE is building a JUCE project for you. That project needs to be compiled to turn it into a plugin. If you can't compile HISE you can't compile your project.

@zachhealy1005 said in Linux:

Like on all other operating systems you basically just de-package it and it automatically installs it on your computer for you why with Linux do you have to do it so manually

Linux is a special case because there are so many distros and library variations that providing a binary that will work across all is not possible. Also all the prebuilt binaries are out of date almost immediately because the HISE source changes so frequently, and as I mentioned before you need to be able to compile it anyway, so a prebuilt version isn't much use other than for exploring HISE - also covered this in the course.

@zachhealy1005 said in Linux:

I'm letting you know the process you have on their does not work for unbuntu studio.

It would be helpful if you let me know which part of the process doesn't work. As far as I know all the packages should be available because Ubuntu is built on Debian, but they might have different names so you'd need to check that.

@Felix-W said in The Legato between samplers:

will point KS to the legato Sampler

I don't understand what this means

@Lindon Here's the fix, just two lines need changing:

https://github.com/christophhart/HISE/pull/983

It is related the default state being saved when loading the first expansion.

There is a detailed comparison of various pitch algorithms.
Rubberband performs really well and it's not too difficult to integrate into Hise.
I think there's even a detailed post somewhere here on the forum about this topic.

@pgroslou Even the Lite models of the previous version, which consume less CPU, don't work; only the standard models work.

Hopefully, the A2 NAM (which has two versions depending on CPU usage) will be integrated without any problems.

@DanH said in Matrix modulation connection is broken in exported plugin:

He can drop that
addModuleStateToUserPreset call unless he needs the container's own chain
state in presets.

Yep I need it, so I can't remove it, then 2 MatrixData blocks it is and will be...

Two root-level blocks means two live ScriptModulationMatrix instances at save
time. Unlike most Engine.createX calls there's no caching — each call to
Engine.createModulationMatrix() constructs a fresh object and registers a
fresh state manager, even for the same container ID. So ustk should search his
scripts for a second call (a second script processor, an included file, or a
call inside a function that runs more than once). Restore-side it's mostly
benign (each manager restores from the first MatrixData child via
getChildWithName), but it's the smoking gun that two matrix objects are alive
— and two objects both performing remove-all/re-add restores on the same tree
is exactly the kind of thing that could leave the runtime side confused.

Nope, no smoking gun here.

The signal path goes stale if:

the container's child modulators get rebuilt after the matrix restore
(remember MatrixData restores last, but postPresetLoad, sample preloading →
prepareToPlay, or anything his preset postCallback does runs after that),

something worth investigating, especially prepareToPlay that has been modified recently to fix another matrix bug...

Practical suggestions for ustk

Grep the project for createModulationMatrix — ensure exactly one call, in
onInit, stored in one const var. If duplicates persist in fresh saves after
that, an old instance is being kept alive.

Always had only one here

Drop addModuleStateToUserPreset("Global Modulator Container").

Nope, need it for what it does. And anyway I tried without and it doesn't seem related to the issue.

Check whether the broken targets' source modulators are bypassed/disabled
at the moment the preset finishes loading (the active-list trap above).

Nothing's bypassed

Note whether broken targets are MatrixModulators in mod chains vs.
script-slider parameter targets — they use different listener paths
(MatrixModulator::onMatrixChange vs MatrixCableConnection), which would narrow
it to one code path for a proper bug report to Christoph.

Only MatrixModulators in mod chains here, not direct parameter modulation

@ustk Ok I think im understanding. Thank you.

@Christoph-Hart I'm also still encountering this issue.
I've also tried all kinds of formats
"{PROJECT_FOLDER}/Scripts/test.js"
"{PROJECT_FOLDER}/Scripts/ScriptProcessors/test.js"
"{PROJECT_FOLDER}/test.js"

I also get onControl cannot be parsed.
My test.js is a file I saved after adding a blank script processor to my container.

1:
"Right-click/connect to external script": Works!
"Rick-click/reload connected script": Works!

2:
Adding script via Builder.connecttoScript: On Control cannot be parsed.
"Rick-click/reload connected script": Does not work "because connected script is not a valid HISE script. OnControl( cannot be parsed"

function onVoiceStart(voiceIndex) { "Hallo"; } function onVoiceStop(voiceIndex) { } function onController() { } function onControl(number, value) { }

@Sampletekk David, I bow in your general direction!

@David-Healey 👍

@resonant It's optional, HISE will fallback to a less efficient algorithm that's all.

Hi all, good to be here :-) I'm the developer of StripKit, glad you like it. If you guys have any features you'd like to see or any bugs you'd like to report for me to fix, please feel free to contact me here or shoot us an e-mail.

@David-Healey This worked thank you

@svkpowa Aha ok, just took a look at it and it's probably not needed for new projects.