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

@eokeefee The full displacement is then the slider height minus the circle height:

laf.registerFunction("drawLinearSlider", function(g, obj) { obj.drawOutside = true; var a = obj.area; var norm = obj.valueNormalized; var radius = 15; var cx = a[0] + (a[2] / 2); var start = a[1] + radius; var usefulDisplacement = a[3] - 2*radius; var cy = start + usefulDisplacement * (1.0 - norm); g.setColour(obj.itemColour1); g.fillEllipse([cx - radius, cy - radius, radius * 2, radius * 2]); });

@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

@d-healey Created new project, tweaked Mac display settings, tools & grid now visible on both projects:LAB2.png LAB.png

Opened HISE on Laptop, pressed left trackpad button to drag app for scaling & it just popped into place. Thanks for pointing me in the right direction.

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();

@Lindon For tables, shapes and consort, they can be saved as array values into the object.
table data points, paths as string, base64 states...

@Yinxi

Bunny

If you're using WooCommerce there is a compatible plugin too - however the downloads from the developer's site aren't working so if you need it let me know and I'll send you it.

And I assume these are the modulation colour references to use:

HiseModulationColours::ColourId::ExtraMod HiseModulationColours::ColourId::Midi HiseModulationColours::ColourId::Gain HiseModulationColours::ColourId::Pitch HiseModulationColours::ColourId::FX HiseModulationColours::ColourId::Wavetable HiseModulationColours::ColourId::Samplestart HiseModulationColours::ColourId::GroupFade HiseModulationColours::ColourId::GroupDetune HiseModulationColours::ColourId::GroupSpread

Is there any limitations around which colour a particular parameter should use? Or is it really just down to how you want it to appear in the module tree??

And for the ParameterModes, would it be these ????

modulation::ParameterMode::ScaleAdd modulation::ParameterMode::ScaleOnly modulation::ParameterMode::AddOnly modulation::ParameterMode::Pan modulation::ParameterMode::Disabled

@d-healey seeing the number of people legitimately falling in that trap, it's a pity there's still no warning in the console