I'm trying to make my patches more Vanilla/libpd compatible:

1. I've been using [z~] for audio delay in PD-extended. What alternatives are there in Vanilla?

2. This patch currently contains katjaas' external, [helmholtz~] for pitch recognition as well as the .dll files needed for [vcf_bp6~] (Thomas Musil) to work. I am curious about the nature of externals in a Vanilla environment and the integration problems they might pose with libpd. It seems problematic (though I'm not sure if this is actually the case) to have a long list of abstractions/.dlls needed for your main patch to work. What is your general approach when you find vanilla objects insufficient? filter.zip Are abstractions better than .dlls?

3. [prvu~] is useful for monitoring amplitude when testing a patch. What can I use in Vanilla? Of course, since this is only needed for monitoring purposes, I don't need it for any kind of libpd patch, so for now, I could just copy the .dll into the folder...

Heavily modified first post.

Changed topic questions.

I think you have to use [delwrite~] and then [delread~] or [vd~] (with a [sig~)....
David.

@whale-av Hey David, I wasn't alerted to your reply for some reason...

Yes, that's what I was afraid of. Yesterday, I remembered having used [delwrite~] with [vd~] in the past.

I've made a vanilla [z~ ] abstraction with [delwrite~] and [delread~]. The equation is (samples_to_be_delayed / sample_rate) * 1000. I've tested it against [z~ ] and it gives the same results.

As for [helmholtz~], you can use [fiddle~] which will do the same. Maybe [helmholtz~] is a bit more efficient, but [fiddle~] is a standard vanilla external.

@alexandros Hey, thanks for the tip! I followed your instructions and it works well. Just to make sure the delay line is always bigger than the delay time, I put $1 as the delay line... Not sure if there's any disadvantage in making it so unnecessarily larger than the delay time, e.g. in terms of cpu consumption. vz~.pd