@d-healey @orange Interesting, the zoom handle I was using is crashing a lot too so I removed it... I'll study and try that implementation, thanks, Dave!

@d-healey Mmmm... The doc is talking about older version being overwritten, and since I was still testing things I didn't updated to a higher version number (still 1.0.0). That might be this, further testing needed...

@d-healey And it translates to the projucer so it should be good

@d-healey Its enabled

So the presets are embedded in the binary.

Upon an update that has new presets, the old ones are not replaced and the new ones do not even install, unless I manually remove the preset folder.

Am I missing something? A flag maybe?

@Orvillain I’d ssy the very first step would be to analyse the code of the existing module and try to replicate it. Just a copy/paste that you can use as a starting point for your own module

@Chazrox detached appears when you have more than one script in the module list. If you click in the module list to modify another script, or show its network for instance, this detaches the other scripts currently being edited. So if when you make a change, it's not compiled until you "re-attach" the script from the module's list and re-compile.

@Chazrox And when you compile, is the focus on the script? meaning not "(detached)". This happens when you edit another script at the same time, so the modifications aren't compiled.
I find myself being tricked a lot by this everyday... "why the heck this isn't working... Oh ok... silly me..."

@Chazrox Since it's a namespace, maybe it's in the main script... The console is definitely saying something about a missing semicolon so...

@Chazrox

@Chazrox What do you have before line 7? sometimes an error ahead can appear later, for instance when a line of code isn't closed ;

@aaronventure It shouldn't be limited to 16, but there's still a bug with the number of sliders an ExternalSliderPack can handle.
This might be of interest to you: https://forum.hise.audio/topic/11411/externaldata-sliderpack-seems-to-be-limited-to-128/13?_=1743103883757

@Christoph-Hart Although it seems a good action on you behalf, I don’t really see the purpose of this thread. It’s like going back in the days where we were constantly asking for fixes in the forum and you said that if we want better chances to see them corrected, we have to open an issue on git. And that’s what we are doing, but they are often not treated, letting us in a state of despair… (yeah I know I’m just trying to draw a teardrop from you, Chris )

So in the end, is the only goal here to get a vote system?
I’m sure that the priorities can be easily seen from the issue list, and then taken in order until the « full » issue list is cleaned.

I am not trying to print a bad feeling to this thread. It’s just that it’s already a pain sometimes to report issues that have already been reported multiple times (sometimes over a very ling period of time), as well report them in git, and finally see we have to do it again here.

Or maybe it’s just me and my laziness talking, and in no way I want to be demotivational or disheartening, I’d just like a bug report system we can really be relying on and trust, as a sustainable system

@d-healey I was thinking about the delete one as well and somehow managed to forget writing it...

As the title says, we have the postSaveCallback which is useful for instance for updating a label.
But what about renaming the preset? Is there a workaround?

@Christoph-Hart CMD+B is a bold choice...

@Adam_G Here's a start:

HiseSnippet 1480.3ocuW07aaTDEeVmrnZCszJp.NQ25CUNkDWuqc9pUUjD+AD0jV25zBHTU63cGaOj0y3t63l3VUQQhaEgJ+GzKbhK7W.phKvYtv0diKbfabfCg2rytY8lMjFEA0Ghx626qeyal27lsoG2l36y8PZ41Xz.BR6MzaMhI5UsGlxPqVCocB80w9BhmgBZkQCv99DGjl1DenDPK6jnfe+4GrB1EyrIwPHzs3TaxZz9TQLZyktB00sA1grAs+XVWYoUs4rpbW9PfOSnWBM.auItK4pXoYYzQeD1uGR675VcZaa0Y9xKXtn4hyWYQSyYWnckRV1NytX4xyU1oi0B34V.b50p6PEbuVBrf3CAcEtynV83awTI3VTeZaWhTvD0BxrBFUsG00oYTwwGgzlrYboZBUo5z5qScn6hGWxNYfBiXOFunok4fnj43TpzASIswnzjJJcJ8V1dzAhXMR97VgnwLxLAkTZQYdVF8pblfvDE6i2jzvCDVEj85fsIElqTooMf+L0kxkC1m7EF2G6YLf6eEVaiKaD4YWhnJu+.NCDJjWoNO3SrKOfy6eP9DpOexD0r90uyZK2XLur8HPIbMtM1cMNeykYNMHD2BR21+.2vkiETV2MntDy7SUzmHR4cXZjAIW3+WzizkJaAZLjYKnbVg7Nd3sZPcArlXQu7SazIRU2oM3s+7ox8vbYuvE.Z3ycIEG3Qg7K7jkQoVH5YykUtpvv5APJN.Byxv5ATf+rR2FPUUN4J3VX2gjBSYbdiYrJUJvBqaa79WNpPlzlJAljKaW4xS0LUnz1cB+Iyb2hR5KIdgnTOsAdZiREmET+notTzhwfytJWPtFqPv5I2ixYrWUc5ru5j0eOtqKwaeUK668NHGKvF1uMwaZXmGVW6ZHbNOYyi9+dyy38y1piCiYHmsJiJt1.Rnb51KT3YHnQKSHq.SEAsYmHrgpkK0g3gnPWzwzUaXn.FO9UfnCg2Y0C2K2G2u4p0vBrreOjQ.KGP7DTYAPqF49vMrpt+r50H9aJ3CfTs6wdj1qKButRk1w6BBR9apmnw.scb5+zkFMtPHATY6s0q4g61EC06nVAFwE0tazM3Yesnk.UP5GityN673jnVgFWVBGrZynoo+vbFF42cKYUm7WDDwdvv.gG8dF0utY9oklrJygrMnbFy.wFv4N9VeL2aSeX9AATzA65SBzsrTkhs2f3Se.rlA8Bugiot1HFtO0t0.hMnn+xLr6HehGXWo.itoO4lLG95XFLZxKQ3gXRDWiUiODJJUco1alPsbd4MvrtRNYUoXo3bFTX2VrNgMLjO4dDZKpi.F2oq8TMDpGg1smPJ8KpyT6t8N4K+LY7N5Rjw1QewvkNbAJ93Ybjdt2dhT5oQvbPtyPWrH4vQYYHTAzzmXRjbZCymJFM9yJ9Oah4gkhmRuIUX2a+4Xl8gix6H9efiguy33506zANLFSvI0a7IuBdTwLQWqTcn28I0uW39WxdvD73pC6q5tj2MqcLX4rBl4TJrRY7WUrVRBXFB7rK9N0C.rR9LRlS48BTIF3jAtLaHvi+4yTL.Xtnfdtm9UA.yu2XrvdAVbuA0LhpK86ybNERDWM96y7cJjTj0LEaMSQWyc46SN6LJjHBa7GmtmBIEiMSQYyTb1Z2x668EETHQbF8ks+QERJNakhyVo3rUDmew69qS87.jHN+7u46+VkMo3rUJNakhyki3L5Im83AQtbDmegFZKkMoOTjhykSw4xQb9t+14NuJxQb9t+zW+CJaRw4xo3b4DbtQiMpyjS5TcaSbn61N3up.cC9P4b20wP2Db0pNz+zBlGZSfdcFLMMnMJi79dkbIorjRsHAsU5ZvvzcBUZJk0BUZFo7URN5is832wV8PG40HGK.AV2rfucKK7QjfrgY522zG9To6XamLTobz5n5X4ipiUNpNN6Q0w4NpNN+Q0wEd4NJ+R1kGJ38UCBQn0aVO3EZZZi0Qf9G.2MnRUC

And you can get inspiration from here:
https://forum.hise.audio/topic/11023/snippet-a-zoomable-waveform-with-a-script-panel?_=1742900429232

@clevername27 said in All About Latency:

Questions

• How do I determine what latency to report (i.e. setLatencySamples)?

I see 2 ways:

• Direct measurements in DAW
• "in-plugin" measurements

Then make a latency array containing the value of the different scenarii you can refer to when reporting to DAW
I am making my table with "in-plugin" measurement that I later confirm in DAW (you save an export)
For this you can set a buffer with a peak sample that you play at the beginning of the chain and you record a second buffer at the end. Compare the two -> you have your latency.

• What happens when my plugins' internal latency changes during playback? (Short answer, I gotta think in terms of maximum delays.)

That's doesn't seem advisable. I am not sure DAWs like such a fickle dude. I know it's possible for plugin to report a dynamic latency, and for some DAWS to accept it. But they don't all seem capable to adapt (some yes, some at the next buffer, some when after a stop...)
So my approach would be to account for the maximum delay to report (constantly), then compensate "in-plugin" by adding delays up to the difference. But someone else might have a better expertise on this...

• How do I account for the latency incurred by external factors, such as other plugins not reporting their latency correctly?

Do you mean plugins playing on the same track/FX chain? They are not your concern... Or am I not understanding the question?

---

Current Strategy

3. Inside my plugin, I am constantly computing the actual latency.

How you do that? summing pre-guessed value depending on the configuration/state of the different DSPs or actual real measurements? The second is less error prone, hence my question...

4. Using a final SimpleGain module on the Module Tree, I set its delay to [Time Reported to the DAW] - [My Plugin's Current Actual Latency].

Yeah so that's what I was talking about 3 questions above... not sure it helps then...

But this is agonising, but sometimes I simply can't even figure out what the actual latency is…or even what that means.

That's where the question of computed values VS actual measurements makes sense

Just here to say this new functionality seems nothing else than just amazing... I'll try it next week on the FX I will release in a few days!

@aaronventure said in How to optimize Scriptnode Networks?:

The only node that will introduce any latency is the delay node

The oversampling does introduce latency too