node/scriptnode ahdsr envelope release timing mismatch

[Morphoice]

@DanH yep the visual curve should be changed too... it fooled me once or twice lol. also the release seems very very curvy for a default unchangeable curve...

[Morphoice]

@DanH i'm not fixed on a release curve control, we can call it damping ratio/factor if that helps as long as we get one ;-))))) we'll have to shoot a few beers towards @Christoph-Hart

[DanH]

@HISEnberg said in node/scriptnode ahdsr envelope release timing mismatch:

@DanH This might be useful for you then ;)

Paint Routines ADSR

@ulrik I've updated this. Since I don't really understand how the getBounds() work, and the last version didn't look right when changing the Attack Level I ...

Forum (forum.hise.audio)

Ah yes I did look at that before. I'll take another look. @ulrik do you think you could figure out how to add nodes for the curves?

[Christoph Hart]

Nah the behaviour of these envelopes are kind of set in stone - it would change the sound of all existing HISE projects if I would start tampering with those curves.

You can change the skew factor of the target parameter which gives you some control over how the envelope affects the modulation.

[Morphoice]

@Christoph-Hart that makes sense. then again, a new seperate envelope with different parameters would be a good idea. Once I find out how and where the modules live in the source and how to add my own I might give it a try.

[Christoph Hart]

@Morphoice Maybe it's time to finally give in and add a clone of the flexible envelope from KONTAKT. It might be tricky because I would have to somehow attach semantics to individual table points (so that eg. table point #1 always marks the attack level while the sustain loop will happen between table point #5 and #6) or whatever.

[Morphoice]

@Christoph-Hart count me in ;)

[Lindon]

@Christoph-Hart said in node/scriptnode ahdsr envelope release timing mismatch:

@Morphoice Maybe it's time to finally give in and add a clone of the flexible envelope from KONTAKT. It might be tricky because I would have to somehow attach semantics to individual table points (so that eg. table point #1 always marks the attack level while the sustain loop will happen between table point #5 and #6) or whatever.

why not define (and display) a set of 3 zones: Start, Middle, End

the user can scale(drag) these zones, but everything in the Start zone(as many table points as/you like) will always execute exactly once at the start of the envelope(the attack portion) the middle area can again have as many areas as you like but will always repeat(the sustain portion), the end portion will again have as many points as you like but again will execute only once at note end(the release portion).

If you mandate that the last point in each segment must be the same as the first in the next segment then it should work fine - in fact the table envelope is 2/3 of the way there....

[d.healey]

@Lindon said in node/scriptnode ahdsr envelope release timing mismatch:

in fact the table envelope is 2/3 of the way there....

Yeah the table envelope is just missing a sustain section, so why not make a new table envelope with three tables?

[DanH]

Envelope looping would also be a great feature

[DanH]

@d-healey So we'd have to display 3 tables on our UI to control an Envelope?

[d.healey]

@DanH Actually I wasn't thinking of it being a front-end feature - I don't think Flex envelopes in Kontakt are controllable from the front-end... but this is HISE so you could control it from knobs, buttons, sliders, tables, etc. However now that you mention it, perhaps there is a better way, and I'm sure Christoph will find it.