I didn't look at that patch, all I am saying is that I think it's important to have audio signals triggering the object. If you just want to use MIDI, you don;t really need it, but my library is fully sample rate accurate, like a modular environment. I wouldn't know how to do that with Vanilla, seems impossible or dreadfully hard/crazy with all my features.

The [slop~] object is sample rate accurate though.

@JuanMadrid said:

And you are right, to develope the ADSR with vline was complicated foir me. I spent several hours,

and for me it's important that the gate value is an audio signal and that simply can't be done with [vline~]. A proper envelope should also be able to be retrigerred while the gate is on. When I added yet even more features like I did, it simply gets impossible to be done with Vanilla.

it was historically immediate release by default, but in that particular version I was trying to accommodate more features and kinda screwed up... and now it'll be back immediate release with yet more features, so I was able to find a way to accommodate things.

It's hard to add features without breaking things.

By the way. I don't think [vline~] can be considered an envelope generator at all... you can do it, but it's a lot of hassle and it's only linear and very limited. For you to be able to deal with exponential curves and all the things I provide in my envelope generator is just virtually impossible with vanilla.

of course [else/adsr~] is much more powerful and offers more exponential curves. I find the one pole filter solution not that great, but I haven't bothered on trying to implement something like that in Vanilla

Note that the new stuff I pointed above are already part of the experimental/nightly builds of PlugData.

As for designing envelopes, I have the "Live Electronics Tutorial", an extensive tutorial and all things ELSE and Pd, which is also distributed as part of the PlugData documentation. I have an example on how to build exponential envelopes over there, see

here's a screenshot you'll find in chapter 17

I also have added something like this to the help file of [slop~]

this is what I have for the upcoming version, a more versatile and sophisticated time management system

I'm really sorry that I end up changing things a bit, but as long as PlugData is still at an experimental 0.x.x version I am doing this in favor of improving and enhancing the objects. When PlugData 1.0 is finally out (and I can't wait for Tim to do that), I made a pact with the devils that I should just stick to whatever bad decisions I had at the time and let it go...

What version of PlugData do you have?

If you have the last stable version 0.9.3 this is what you have and shows you how to set the envelope for immediate release or not

A new version of ELSE and plugdata is already up as part of an experimental 0.9.4 PlugData release and things changed a bit.

So there's nothing really wrong with the object, you just didn't check the help file carefully

I'm working on this one https://github.com/porres/pd-else/blob/master/Abstractions/Control/lsystem.pd

how would it be for audio?

@Dizzy-Dizzy said:

I downloaded the latest else library and I don't think the external has been updated yet for pi/linux?

nope, not yet... but you can get it from github actions

a real update might come in a month or so

@Obineg said:

try to implement something simple and common such as a tremolo or vibrato to the paf~ external using data rate and you´ll see what i mean.

my paf~ external has 3 signal inputs for that matter