@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.

@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.....

@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.

@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😁

@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

@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.

@Ajak Try and see what happens. Im curious lol

@d-healey
Damn it! :-)

Thank you.

@duma said in Need Help Exporting Mac Version of a VST3:

@d-healey i dont have 99 dollars am I at a loss??

If you want to release plugins for other people to use on Mac then yes.

@Yinxi definitely the second one.

@Oli-Ullmann Thank you so much! Big respect 💪

@d-healey I see. Thank you so much.🍻

@Orvillain Niiiccee thanks this is precisely what I need. I agree the create C++ code for global cables is a bit clunky but once you get the hang of it it's not so bad. Here is the doc I think you are referring to:

https://docs.hise.dev/scriptnode/list/routing/global_cable.html

1000054321.jpg

Figured it out. It does support addModulator. This is how you do it:

d3660d2c-72ae-45d4-8e6d-f5110a221950-image.png

Content.makeFrontInterface(600, 600); const var builder = Synth.createBuilder(); builder.clear(); const var generator = builder.create(builder.Effects.SlotFX, "generator", 0, builder.ChainIndexes.FX); const var slotfx = Synth.getSlotFX("generator"); slotfx.setEffect("Hardcoded Master FX"); const hardcoded = Synth.getEffect("generator_Hardcoded Master FX"); const numP = 4; for (i = 0; i < numP; i++) { hardcoded.addModulator(i, "MatrixModulator", "P" + (i+1) + " Modulation"); } builder.flush();