@d-healey this seems wrong, the second parameter numSamples should be your stepSize (protected), not the position j

Also you need to protect it when reaching the end as Chris mentioned

for (j = stepSize; j < buf[i].length; j += stepSize)
{
    local position = j - stepSize;
    local numSamples = Math.min(buf[i].length - position, stepSize); // protect
    buf[i].getMagnitude(position, numSamples);
}

And why not starting the loop at 0 to save some calculations

for (j = 0; j < buf[i].length; j += stepSize)
{
    local numSamples = Math.min(buf[i].length - j, stepSize); // protect
    buf[i].getMagnitude(j, numSamples);
}

https://forum.hise.audio/topic/9229/tutorial-macos-code-signing-notorising-and-installer-part-ii-added?_=1737473961595

@d-healey Do you mean, by making a chain reaction by listening to surrounding components state or something similar?

@Dominik-Mayer Yes !!!

@tiesvdam something like that?

HiseSnippet 845.3ocsUstaSCCE1tsFsVXRLId.h1uZQUSocc8hlPrsdApftEQGSCgll7RbZrVhcThyJUn89viBON7F.1IsKorN.UwRShx4xmyWO96bhQ.2jDFxC.vRmNym.fOCMdFS3z0ASYfg8.vMPW1ejwoeBbzLebXHwB.g4eiJJrXAP7wOd8QXWLyjj5B.NiSMIum5QEodMN3cTW2AXKxoTuLY23fglbVWtKORxj7HcfO17Z7DxwXUZ4Pf2hCc.vWhz2qIgzZWaKK7t6Z0rYyNs6znSMrsdC7U0Z1oQ8Fsp2tkM.9j9VTAOXr.KHg.Xgi3VyF6vmxRdAmQCoW4RTF0.iku4D2C3tVp+hJuftNTWKiEknPfbULRKX4SJXu.MhZQuyeZg64wAzRQjs.BysL8xuD8pkkd5Yn2JnDLCkJjPosPiMCn9hzHJ97TzPlfDXik6SYoRRtfbeCh5xkYvD63gulLHPZbGhxM00qpIuUY+Rkj6UgBsavAZFXFwsl1qzVfbBQzk64yYRixamDdaEljG2IjHLjEHwG3QBJiT1NhYJnbV4IUJ80REmrisTfbnqaY8yGLnQK0OI5hpHgpkVoPhiMXvdsiYybL8cco9gjxetidU4Yc04EKfZEfm1Kf6O1AawmFmil5pd70EUSWPkck80Jcak8WPMMN6XtfbBqbLEKcaIseOjs8JioJJAbWWRvJCq5AB9S.Kyh7thDTUVpciH2knbedYwC5gEOY01lI6QYRjyFxnhS7IrGRwCluwJe5iC6gEXkhatOYd9j.AUQAXOxMx98D8WQTOR30BtebtyUCxNRQbzMWnNUJB.0RMhIQc.9R5HA5AyxZLkZIjC.PvuKMcHzINhEVf62.Ha83VQtXwx8ipoVyCHqyK0DnD5rPpXV1oZ+2ZR+Wo3VHCpvzY0bL2J3nb23wfiyGssIpusMwTjRvBnAm+3LGCjLQXxHrHfJ0Anii7FKa1MIx2NSpNT5bXNkhLwVWYqp.iILqXieJOlGrlxFNOXsEAAdXy.9klIcWpgmaD6QxIV7GZJhFor0pAh63xVm8jyxuzzb4k5d.qut.2ccA1XcAt25Br45Br05Br8eGn5SsGFI3dIsM.vHi9wiqfv9LrTAFqVA+BP1GwEE

The size of the last parameter radius should be approximately of the same size of the dot
In fact in my example the shadow area is the exact same as the dot area

A nice companion for the math.map node

@d-healey Maybe a solution could be to run your own modal so you can keep track of its state.
Or could the MultiPage system be of any use here?

@Morphoice So you're talking about UI here, right? In that case I make the silder 0-100, so with a 0.01 stepSize it's feeling like 0.0 granularity
Then in the callback you can use component.getValueNormalized() so it's 0-1 again

@Morphoice @griffinboy The system is not consistant in apparence but behind the scene, a mid point sets the skew factor via a formula. This formula is reverted to get the mid point back from the skew, so in essence it is the same thing. Now for the user, it is indeed confusing...

@tsempire this thread as some info about this, but it's quite specific with no real snippet example https://forum.hise.audio/topic/1146/viewport/22?_=1736869127339

here's a very basic use of viewport
https://forum.hise.audio/topic/2541/viewport-item-text?_=1736869127349

@tsempire I personally use panel inside viewports (with childPanels), but I think you can get there by just using viewports with item lists
You need first to get familiar with those viewport lists, so when clicking an item you update the next viewport/column
Then get familiar with the file system to gather midi files and folders and populate the viewports

@tsempire That's a LOT of work

@Morphoice I don't know about Faust resetting the curve but:

• The curve you see does nothing but adjusting the skew factor behind the scene. So no it's not linear, it is exactly what you see.

• I personally only use the skew number, that's my habit, and it's one less node in the graph! But a cable_table would do the same (but of course is necessary for more complex behaviour)

• in the end, most of the time the curves I need are either linear or log, so the skew is often either 1.0 or approx 0.3 for a kinda log behaviour

• If the slider is snapping, it's probably because StepSize isn't 0.0

@tsempire You need to build it from scratch using the file system, and panels, viewports, etc

@d-healey And now it's a few other things that don't draw as in the original SVG so this is not reliable enough unfortunately... Can it be fixed or is it part of the JUCE thing? I don't know...
Decidedly, the graphic is showing a lot of limitations lately. Maybe we should discuss that in the meeting on Friday

@d-healey So that was it, here I have a circular gradient in the centre that is not showing in the converted SVG:

@VirtualVirgin Then it might be that your paintRoutine takes too long because it’s too complex. As @d-healey said a snippet would be helpful

@clevername27 said in Why Does Every ScriptNode Delay Break My Playback?:

Can you tell me what is different about jdelay from core.gain

Not sure what you are asking here. One is a delay and the other a gain, but you know this already

and why you are splitting the signal in the Network?

It was just for you to hear the comb filtering as you move the parameter with 0.02 steps increment. So you could hear the "smooth granularity"

For dynamic blocks, I present this interface to user;

Hmmm… seems a bit technical for users, no? Many of them are not necessarily confident enough with interface buffers length, so understanding internal blocksize might be confusing… (not trying to be pedantic here)

@clevername27 said in How to Modulate Gain with a Table in ScriptNode?:

why wouldn't that be internal?

What do you mean by internal? The modchain separates the mod signal from audio signal. But some nodes can do both so you don’t want them to blend. For instance an oscillator. And having a dedicated container makes things tidier, at least to me…

• ...why the pma block?

I’d say why not?
It does what the bipolar does but without the add parameter. I think add could have been added to bipolar And get rid of the pma but since the latter is older, it might be for breaking compatibility reasons… but yeah, we have two different controls that could’ve been one unique node…

@Dan-Korneff yeah it can be troublesome to be sure both are working (hise and plugin)