@rzrsharpeprod I couldn't say without looking at the graph, but oversampling is usually used to reduce aliasing (i.e. in a saturation fx) and in that case I would advise to put only the 'processing node' you intend to oversample in that oversampling container - not the entire graph.
For modulation purpose you'd need to process your signal in block containers (usually 8 or 16 are enough) - put the modulation and the nodes you're modulating in these kind of containers.

@DanH In my testing, the original lane it tied to the old parameter "Input" and a new lane is created for "Input Trim" and vice versa.

@ericchesek yeah they are just a glitch that is nagging you to clean up after yourself…

@ustk

Yeah I'd just use a loop. I'm not sure why find is not doing what's expected though... Also you don't need to set the second parameter as myArray because that's already there in the third parameter of the test function.

This is what I would do

local myArray = [0, 5, 10, 15, 20]; local element; for (x in myArray) { if (sample <= x) { element = x; break; } }

@d-healey Thanks! I love your videos :)

@Lindon Same sort of thing I do

66ce1f15-f918-4911-b13f-2212abc0494a-image.png

@d-healey
a8efe79d236f2bb6503f7cff2c7a00a7.gif

@ericchesek you don't have to worry about note ids or any such thing. Just set the samplers' settings correctly.

When you specify maximum number of voices, that handles note chokes automatically. If it is set to 5, when 6th note is played, the 1st note is faded out based on your setting. You just tweak that to make sure the fade is unnoticeable.

You'll know you got it perfectly when you the instrument and everything sounds natural and normal.

@d-healey OK! It does appear to be something that's different with Nginx redirect headers.
Just loaded up a site with Apache and the redirects work as expected.

Nevermind, it was a sample issue.. Thanks anyways!

@ericchesek in addition, everytime a note is released you can kill it so you don't get a build up

@d-healey Sorry the link completely slipped my sight! This looks very promising and exactly like what I need. HISE keeps blowing my mind!

anyone seen this before? very frustrating

@Dan-Korneff I did the same thing - https://github.com/christophhart/HISE/pull/289/commits/9aab1f561ab364ee95682d5edbc6aa889d86fa76

Christoph hasn't merged either as far as I can tell but if you have your own fork you can pull in the changes yourself.

@Lumi283 Your example result is an array...

const result = [ { "_id": "65354a6e1f6318b08c7612cc", "expansion_version": 2, "url": "url2" }, { "_id": "65354a7706a49c291b423e1e", "expansion_version": 3, "url": "url3" } ]; result.map(function(obj) { Console.print(trace(obj)); });

@ulrik I solved the linking several Table Envelope Modules together problem using the broadcaster and transfering Table states using exportAsBase64 & restoreFromBase64.

I'm glad we have the Broadcaster functions 🙏🏻

@tobante Haha, yes of course, I'm sooo stupid, thank you! 👍

@Dan-Korneff Could you use the markdown panel? With that you can put a custom URL.

Oh I found the solution (still not sure why it goes crazy even when the script was cleared though).

Child panels are kept between recompiles, so it's necessary to clear them all out before adding them. Just put this after you create the parent panel.

for (x in Panel1.getChildPanelList()) x.removeFromParent();