@d-healey 🤷

I just went to the source to look into making an addNoiseToArea function and what do I find but sneaky undocumented HISE goodness.

You can pass an object to g.addNoise!

g.addNoise({alpha: 1.0, scaleFactor: 1.0, area: obj.area, monochromatic: true});

alpha = noiseAmount

The CI for the fix seems to have got stuck https://github.com/christophhart/HISE/actions/runs/12342377762/job/34442128570

Ok, if someone hits the same issue, I might have found a solution for this. I don't know if that's the proper way of handling it, but it seems to be working ok.

I chaned this bit, and replaced the assertion:

bool isConstant() const override { jassert(ns != nullptr); auto v = ns->constObjects.getValueAt(index); // objects and arrays are not constant... return !v.isArray() && !v.isObject(); }

by this :

bool isConstant() const override { if (ns == nullptr) return false; auto v = ns->constObjects.getValueAt(index); // objects and arrays are not constant... return !v.isArray() && !v.isObject(); }

@oskarsh It is in the official repo already. I've just pre setup my juicer file for my use case.

Well that was an easy fix

@aaronventure Thank you! Got it.

small necro to report that there's a leading slash issue which can only be mitigated by setBaseURL

35dd898e-aac5-4c93-8883-d43f11969774-image.png

@ustk yeah it has to resolve two things (the object t and the function getIntValue) vs. one (only the object, the math function is resolved at compile time.

But this performance difference is neglible - in UI contexts there are much slower things and if you are using anything string related in an audio processing context you have to sit back and evaluate life decisions that lead you into this situation of misery anyway.

Also Math.round still returns a float number IIRC while getIntValue makes sure that the var instance uses the integer data slot internally.

@oskarsh I don't think HISE compiles against JUCE 7. Your best bet may be to port the fix yourself.

@ustk if f isn't defined then .isFile() will return a function not found error. But I'm probably being over cautious.

@iamlamprey Yes that's correct. The jdelay node is supposed to be used with sample-based modulation so if you just move the slider it will jump to the value and create crackles.

The core.delay node creates a fade between the old time and the new time so it's preferred to be used when you have a static delay that you want to adjust with a UI control.

@Christoph-Hart that's a funny one 😂

@Matt_SF @Christoph-Hart is there any solution to this? I am currently hitting this limitation and I do not know how to work around this.

@d-healey I will be avoiding those then..sorry I should have read more carefully...

I see this has been fixed now :)