@dannytaurus said in Scheduled knob task after initialization:

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

It can actually be used for other purposes.

But in my case, I'm actually using it for a bug workaround. When I buld a complex custom node with 23 parameters and use it in HardcodedFX, I noticed that in one parameter, the knob, wasn't getting its value during plugin initialization.

However, after init, when the knob is tweaked, the value is updated. That's why I chose this method. Creating a custom node with fewer parameters isn't a problem, by the way. As the number of parameters increases in custom nodes, the problems increase.

@lijas90 I usually chuck an Audio Loop Player in the module tree because it allows drag and drop of audio files to test with.

@Felix-W said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@CatABC said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@ulrik

@d-healey said in Sampler.setSoundPropertyForSelection(); seems to have a bug.:

@CatABC Use constants instead of magic numbers

Sadly, I tried using constants, but the problem persists. Also, if I swap the positions of HIGH_KEY and LOW_KEY, and need to move the smaller value to the larger value, the contradiction still occurs.

const var ComboBox1 = Content.getComponent("ComboBox1"); const var ROOT = 2; const var LOW_KEY = 3; const var HIGH_KEY = 4; const var C1 = 36; const var D1 = 38; const var E1 = 40; const var B3 = 71; inline function onComboBox1Control(component, value) { Sampler.selectSounds("C3"); if (value == 1) { Sampler.setSoundPropertyForSelection(ROOT, C1); Sampler.setSoundPropertyForSelection(HIGH_KEY, C1); Sampler.setSoundPropertyForSelection(LOW_KEY, C1); } if (value == 2) { Sampler.setSoundPropertyForSelection(ROOT, D1); Sampler.setSoundPropertyForSelection(HIGH_KEY,D1); Sampler.setSoundPropertyForSelection(LOW_KEY, D1); } if (value == 3) { Sampler.setSoundPropertyForSelection(ROOT, E1); Sampler.setSoundPropertyForSelection(HIGH_KEY,E1); Sampler.setSoundPropertyForSelection(LOW_KEY, E1); } if (value == 4) { Sampler.setSoundPropertyForSelection(ROOT, B3); Sampler.setSoundPropertyForSelection(LOW_KEY, B3); Sampler.setSoundPropertyForSelection(HIGH_KEY, B3); } }; Content.getComponent("ComboBox1").setControlCallback(onComboBox1Control);

Ultimately, I set up two methods to call different methods depending on whether the value in the combobox increases or decreases.😹

Wow, this method is so cool! Thank you for the code comments; they really enlightened me.

@Elisee18 I have an old video showing a method of doing this (it requires scripting)

https://youtu.be/_s7LTRz8pEc

@Ajak said in Modules Not Nesting In Containers:

the windows are driving me mad

You can build out your module tree in the sidebar, you don't need to open the windowed view.

@pcs800 well 95 samples would make hardly any difference at all... whats the measured latency of your plugin?

oh hang on youve already said:

95.9ms, that's great. But how do I get the plugin to report that to the daw?

Go read what @ustk said above.....

@HaizalD3 bot.

@d-healey Ah!! Well that can't be good. Sorry about the speakers. I'll have a read of the documentation and get to grips with scriptnode first, I've taken up more than enough of your time. Thank you very much for all your help.

@HISEnberg Friendly bump on this !!

@bendurso Big thx ! 👍

@d-healey i will create new project without any snex, so i will just ignore those all troubles. Thanks for service!

it worked @d-healey thanks ill test it now
it worked after I placed it inside c drives vst3 file
thanks for teaching us im so happy😊
I've made plugins in patcher but never made vst3 plugin now I can bring my patcher plugins to life😁

@Oli-Ullmann Yes I think you're correct. I checked the docs and there is a line about it not meant to be a dynamic state.

@HISEnberg Yes exactly! Since Hise is an instrument and PluginDoctor can only run FXs, you need to interface it with MetaPlugin first. You just get a warning in MP because Hise is still an instrument but just ignore it

update...

I figured it out...

I found the snippet in Docs and modified it for my usage. Yee.

const var rm = Engine.getGlobalRoutingManager(); const var mc = rm.getCable("bars"); const var pnlMasterPlayheadBars = Content.getComponent("pnlMasterPlayheadBars"); pnlMasterPlayheadBars.data.value = 0; mc.registerCallback(function(value) { pnlMasterPlayheadBars.data.value = value; pnlMasterPlayheadBars.repaint(); //Console.print(value); }, AsyncNotification); pnlMasterPlayheadBars.setPaintRoutine(function(g) { var a = this.getLocalBounds(0); g.fillAll(this.get("bgColour")); g.setColour(Colours.withAlpha(this.get("textColour"), 1.0)); var x = a[2] / 100 * (this.data.value * 100); g.drawVerticalLine(x, 0, a[3]); });

@ustk
Yes, thank you very much. In addition to LAF, there is also ScriptModulationMatrix.getModulationDisplayData(String targetId).

However, I actually want to use it for modulation, and I think both LAF and the function getModulationDisplayData run in the UI thread and are therefore not really suitable for modulation. But thanks for the idea! :-)

@Dan-Korneff I haven't ran into that one. Do you have a minimal test project?

@Orvillain
At one point I looked for a way to improve the sound of pitch-shifting, it seemed that the best solution was to build one in Faust or C++. By the way, I think the ScriptNode pitchShift node even bugs during compilation.

@Orvillain @ustk & of course @Christoph-Hart you guys are absolute gems, thanks for all of your input.

For anyone else who may stumble on this thread, the critical documentation is basically found here: extra_mod.

The discussion about doing this for a C++ node seems equally relevant if that tickles your fancy (mine was certainly tickled):
https://forum.hise.audio/topic/13868/is-there-a-way-to-give-a-custom-c-node-parameter-modulation-support-without-wrapping-in-a-network

@Ajak Try and see what happens. Im curious lol