@ILIAM
@d-healey is talking about something like this:

const var knobs = [Content.getComponent("Knob1"),
                   Content.getComponent("Knob2"),
                   Content.getComponent("Knob3"),
                   Content.getComponent("Knob4"),
                   Content.getComponent("Knob5"),
                   Content.getComponent("Knob6")];

const mods = [];

for (x in knobs)
    mods.push(x.createModifiers());
    
    
for(i = 0; i < knobs.length; i++)
{
    knobs[i].setModifiers(mods[i].TextInput, [mods[i].disabled, mods[i].disabled]);  // No text input
    knobs[i].setModifiers(mods[i].ResetToDefault, [ mods[i].disabled, mods[i].disabled ]); // No Double click to Default
};

@ILIAM
Phew, unfortunately I'm not familiar with this topic. I'll take a look when I have time. But maybe someone here knows something about it. :-)

@ILIAM
I did not try your code but if it works, it will also work in a loop like this:

const knobs = [Content.getComponent("Knob1"), Content.getComponent("Knob2")];

for(k in knobs)
{
    k.setModifiers(mods.TextInput, [mods.disabled, mods.disabled]);  / No text input
    k.setModifiers(mods.ResetToDefault, [ mods.disabled, mods.disabled ]); / No Double click to Default
};

@Christoph-Hart
Great, thank you very much! :-)

@Christoph-Hart
Ok, ScriptNode is really fantastic! When you integrate custom nodes such as precompiled RNBO effects, the possibilities are truly endless! Thank you so much for bringing this to my attention! :-)

One question I can't find the answer to:
How can I switch nodes on and off from the UI?

As far as I understand, I have to create a parameter with a range of 0-1, which I then connect to the node's power button. However, this doesn't work for me. Is there a trick to it? Simply connecting a cable between the parameter and the node's power button doesn't work.

Many thanks,
Oli

@orange
When I load your snippet, I can see that it works. However, I have tried it several times now and it won't work for me. Is there a trick or something special I need to do? Simply dragging the button to the node's on/off switch doesn't work, unfortunately.

Many thanks,
Oli

@Christoph-Hart
Hey Christoph,
Thanks a lot! I'll take a look at that! Thanks for your support! :-)

@Christoph-Hart said in Modulation does not work when processorID/parameterID is set dynamically.:

that shouldn't be the reason, you can replicate this easily with scriptnode.

Puh, unfortunately I'm not really familiar with Scriptnode yet. But I'll take a look at it! :-)

What do you mean? If you're just reloading different networks into the same Hardcoded modules you can leave the processor / parameter attributes constant, no?

I will test this thoroughly tomorrow and provide feedback here. It didn't work during a quick test, but I will create a new test project for this purpose.

@Christoph-Hart
I have the same problems with HardcodedMasterFX. And I use SlotFx because I wanted to use the HISE internal delay for its tempo sync functionality.

@Christoph-Hart
Hmm, my use case is as follows:

My plug-in has 8 effect slots. The user can select any effect per slot.

However, I don't want to create a separate slider for each parameter of each effect. That's why I change the processorId and parameterId of each slider appropriately when loading an effect. And I adjust the min/max/middlePosition values. Except for the modulation, this works perfectly!

The only solution I can think of is the following:

I always leave the min and max values of the sliders from 0 to 1 and control the effect parameters via the slider callback.

Depending on which effect is selected, I multiply the current value of the slider by the maximum value of the effect. For a frequency, for example, sliderValue * 20000 (With Math.range(20, 20000)).

This should work for unipolar parameters. With bipolar values, i.e., if the parameter ranges from -1 to +1, for example, it gets more complicated. But even that will definitely work with a little math. :-)

However, that would mean a lot more code and is not as clean as the current solution, which makes extensive use of your API.

Or do you have a better idea?

PS. I use hardcoded effects and the effect slot from HISE.

@Sampletekk
If you have selected “Embed Audio Files” in the project settings, they will be integrated into the plug-in. If not, you will need to copy them to the correct folder using your installer.

@Christoph-Hart
I just noticed that this only seems to happen when the min/max/middlePosition values of the slider change. If these remain the same, everything works fine even when dynamically assigning the processorId/parameterId.

@Christoph-Hart
Hey Christoph,

As the headline says, modulation via matrixTargetId no longer works if the processorId/parameterId of a slider is changed dynamically after onInit.
If you change the effect when modulation is set, even the entire slider stops working.

Is this by design or is it a bug?

Here is a snippet to demonstrate the behavior. Just change the effect and neither the modulation nor the slider itself will work.

HiseSnippet 1996.3oc6Z8zaaajEmzxLNRsaay1TjE6hEfvXOnrapgnriSBJBLiksREpcrPj6eVDTjNlbn0TSNCK4vr1XQt2a87dauteJ1uBEneA5o83h9MX22LCE4PIYaUi3Xm.qCBZd+Yd+lYdy6OjpeByCmlxRLLar6QwXCy20ZvQT9vNCQDpQuMLL+CVogLd2CGDR7wI8QInHLGmrKNkar9QwnzTrugoYsGKTvr97FxO+xZqiBQTObIICiufQ7vaQhH7Rp8c+LRXXWjOdWRjlzq31yiQ6vBYY.3pY0xHF4c.Ze7SPBwlyx3SQoCML+yV2E2B6b2UCdvJdn12qcvxK6sb6Grpumev8Z4b+UWwK.ubf28MLu1l9DNKY.GwwoFlyuNy+nACY+Mpx.eAIkrWHVLvwX.XYE4trPewRTP0nyPRne+Q6ZoFFlKzubOrlZO7lVaS7IEzK2K+.IC6RMz2.MmqJ7pUAdN5vqkF7lBjL0fz7JHcCqAdIjXdIGAddGqdT3rL.AmS5PQIqwb+TMqNLPBJeoHzA3tIvfBMZtZqV2wF951eRiFvYUJ29EnD6Oix1y9g1izaeLuCKJlQgAMWTvzYwREDtVfvRWNgnCDtZeUyEEzGSLXV1icrSbgDBsJFrTpPHJOgE1AEFtG3A0DlvQryYUZGbP.1imBV4YK1YHKIKcw6XuX+gnTb2uZwutQCBMjPw1AYTONgQsmbxZ5MBT2A1NByv2tweuQcgTBvroz.MysyyjBX+w1NeMfg5gLOTXNF.HH0QrJyRRfoKWUgfMpSBZpz8gOz1YoV2tQcvH0E6tBqzbwHBEPdqkDmMUniNDn6LIchueHtOKkHVVRUu6XhDOxyomOvWgRA754271iK5nfDiI5i37DxdYbLnSKoRub7ES6icwz93VMsaAeN8UjypSQpyoE0K+jFZtHOgww6PaJcDZ7xF1iyJHXp7xcnBwISksHbYxIoXSZVzd3Dc2PgfPHgpwYrN93L5gA8T26zDjQ6QI7chwziK3nQ9kUHlzb4nBDkKiH8A4QjjWdVmcnAwWDPp39jgD1ZoObMFeJdu7oPkZRNAKXICwLlxe+O4Z7481.wQhni4fB.ZLNgSD6AlafeAjaREqrt0F3zC3rXIpyuMCYOlQbeXgYc+V2iJW.+UWBGGkJlAUrkF4AVL.+X3XvbNC4NVgAabpqxRS8yGnYpeL0sp6eIH9GtQHve8vcQIR2bvtVQLeCsKBBKJVMOeD7z77E0GzMA+cYXp2QNFQ5o7WwUtNz1xmLMDj.j4mEh3UyJJpcHmg.s5ohDoanvp3H8ZKdkkpbVg3Mr5S3dCmNFmaJXT3weNfw7BL9MVprAk.bdK3f5boZBcyeck4+8VONjsGJrbiBtQAHAqpp3Oly1tfucg.NmPMi+3rVyX7LWy33w5le1h0cJk7M+ktR9lU+3ObhilzWi21pTX5MTvzxZqt6juSA+pDXNmNvVmDyBQIB9EAkx4+Ou0+5+tlvCoWoCl6O39knWfCXIQ4A5Klosv6C1TmxtXHNLTWpmty3fHFiOjP2upe2Mc2hwh2jhfcAe8IQFAExuCEPTR9mWSLs6x1FkBwT6.U8cftM5sOkkfU0LnSuSVJmEMZAH6.Z.GGKSpY9LqUWYI3SveQ78C5.es7NuZF+qIPlyIe7O2L6kJ7DJNxE9DWByInPYgi2kTTdhYtp81clqmxx3vk0skU7.gZdRVz.H0fGFrNkhCSGU0U93Vhwx64Xpubv+C9jyzQL1LmoyHlFpIWqzRJ1SUx0BiWiEbFTfZAJ5Q8wGpHncNXYAsmY7nrCyYeMqOtfflPPuLfVu.JfUknpUkc62uxCy4wIrrX4l8MUDvojTbhsjtyqhmhyrmQVEkr61UBsgRRHP4kpEbgw+2EtySv4yojTFkIgxihXYTtNny4tAlmQq.8bFChSvnJApEne.FfpubJSqbks14QMDK7FaMDWfkqWo.h5iv3.RTbHdS3xPHzQWdTuMvAnrPdAUcPtM3CDOjQIURt+TLbSd+8wI5PepqGnkejdR6a59TbHFR0WR5O4tETtKJQcm+LsU37q9g7M0iqemkBt1hal1u41k0a24ppbbtfx9W2RjpArnvzumbfsBQmTL6hrYiW2oJy03gRWqnl1SJl24ua5MTquKF+yWGEJLi6CuqkJs03kSN2kiqnPEExjmWfv6VJ38NVhdgjkyHQ1GYMp2H6Gio3jI6g7b+oMriGGfvtIHZZLKE6T8tWDYWFEmVg5XZzdpZTgpx6vYRRUjRrUzE1Jzj65tiH1VmXeDsxjAiqLSaSNTu0UU4apRk1I0C1XD6yU54MKLE+kDe9PGcEKI2Vm7mhR7GuK6ymBtt1UEbcUl6KzSQ3pzk65utkEbktss7nz9h4r70Ql3WyY6yen4uur.mpOo77hdlomN9T5E+WVaZ4qTcyNY9JnYlwe530t5oieUf12HaQpVQKRx+wHRSeM4qsrpwOW5iYgQum3QugTUCZUdoo5nP6MlpNW9F91ccKn1V+0y1Ei82q7oK7MAA+m0pTC1EQyY+V0J8s3tytxFytMhPdIrm6o9yXHbittjBb9Qk+27passXrsyD+ENLhfn8O2yq5TMghsOqJt7YUwUNqJd2yphqdVU7dmUEu+oqnHY7ix3rH0cbn6u9apdAilEucSyZF+emApXt.

All the best,
Oli

@d-healey
That's right. Because with SlotFX.getCurrentEffect(), you always get the effect loaded in the slot. So you could also implement it in the effect class and still have access to the functionality from a slot.

So I believe... :-)

@Lindon
Yes, that's right, it's pretty simple, and I'm now doing something similar for the HISE internal effects (not for the hardcoded effects, because the function works there).

But with SlotFX.getParameterProperties(), there's much less code to write. And that's better for maintenance and if you want to add new effects in updates.

@d-healey
Great, thanks. I'll see if I can learn something... :-)

@d-healey
Maybe he'll do it when he sees this post. :-)

Can you tell me which file you found the code in? I searched but couldn't find the right one...

@d-healey
Hey David,
I just tested it and you're right! It works with the hardcoded effect! :-)
Do you have any ideas for the “normal” slot effects?

@Christoph-Hart
Apparently SlotFX.getParameterProperties() does not work because the value is not defined.

Here is a demo snippet:

HiseSnippet 1101.3oc2Vs0aaaCElxIpnQ6BZw1a6Eg7jxPVfctWLLrz3KsFaN0nNKHCECALTGEyEJRMR5rHLzel6+w9GrcnjrsbS5VfQ2dX9Aabt98QdtPOTqXfwnzDufSyy.h2G6OJWZG2dLkKI86P79BeiPY6c6HAOFzCoZZJXA8ofwRNNOiZLPLwyakW3BvasUIEe9iu8XpfJYvbUDxYJNC9ddJ2NW6vi9NtPziFCmxSq48tG0mojsUB0Djbq32jjQYWSuBNg5bqgO4kTyXh2W5uGzDZs29IOaWFc6C1NYmcX6r8y1OlEmbPyVGt+trDXmD1gDuG0MlaU5QVpELDuUOVEmOZr5Wkk.bF2vuT.NgVjQHxkp6oDwtinSKo8XtHd3zaMCAyxv42gqTdG949C3w7Y5meW9jBCgyin9EnWiEo2JKPuV0oWyZz6dnjWMJsZIkdp+HllmYmawwmOxuuDqkITrNUmJk9RZbVC+1JzCocqT50POMJLKhn8a1byP7qM95f.rVYrgtNkvuIrnCZqq.6HWmy4Qq6zu9ht0VkdoB8cZ9QuQUYJIJTFPgGtnlIrkw4jzpUh1Tg3RrgHBS3TyUlliCjj.LqAQw4iChAp3IBrEzXibtsPliVmagTy5aFtdAWST5HHjKmllMBVat+z339n2QfyStTvkPXxDIyxUxv6xoH1zy1lg2PESfMB9sxz4PtaA.QU37lBGB+pvV+Dl70vLXTBXqLMGuYrZ2M+ziyroQrrlAZKGLQarAF0aQVETiOmnrvqjQEnF71fv20TRx8Zqh8BPeulcSr5+t.ijSRuDz0OyNGwtxEa08e+s50mDYk8J0bTI6K41WkAx227IopAyMVTwJzUawPwSpFJJpTGqtkvicyDyJdjBZWeoF4G52gZoSSFl2427ntNvM3FtxIt076.lqsprBeqp93NnGHz2NC1i94ixmyge7nhtTh2u6Gzdh9Fn6uDLhmlIfWC2.5KqDbaiCPJdiRLwUSB5.BZdP6wJ8DSvvwTCz67fQfL18C0NQSw5QPIoPUCUh7YBcSyr43ucxkzTNyD7bIUja.z+wzLWhdIUGyT3ZxvATC1OFVWmKWYiURNC05V.N.vxfTkBAmn3F3EZjrCQ5AZRJEO39deVwSC2YKFt+zM.6nZ8kptCakA7ntvlL21JogayqWE+fso8gRwm5OjaYiueN13d3H1f8uAGqde5S7K23Lmfq5267+CdLpB+G6W9vPAzOpnoeQvW4ACdqGN39SmKqFaJP+SKP+hoppyhSlj1iKvlY2BJOWMoWuS6JoHxeXYI40JbFUd0.pUycs+Hxiv+1CCvBjTBhBBzvsKqTt4TB4leKD9S7SkwVNYuJislZ7+MXjRYZ0ErxM4tR7iKzf2sxh+X3Z9Cbxgsd2k2DRJt54BFawTcm.2dYCbmkMvcW1.2aYCb+kMvCV1.O7eNP2KCOehUkVtgjPFLrawisdd0l5H+01mppv