I still need a lot of more details and maybe we should discuss it in the github issues http://github.com/porres/pd-else/issues/

So, do the externals show up for you on deken as the right architecture for you?

What is your architecture and OS?

'can't load library' or simply 'can't load an object' is the most general error that implies it can't find the object...

what happens exactly?

yeah, I'm working on a version of that too to incorporate in ELSE. I tried for years to include that into Pd Vanilla and will give it another shot for 0.57, but it's likely I'll redesign and include it in ELSE

For vosim~ just get any recent github actions artifacts from https://github.com/porres/pd-else/actions but you have to be logged in

I now added a version of SuperCollider's Formlet Ugen, but I'm not sure how to use that in this context

For those looking closely, the output scale of SC is bad, range can be from -2 to 2! I fixed it in my external.

by the way, just implemented SuperCollider's Formant Ugen as a compiled Pd object...

@ddw_music said:

spectrogram~ is from cyclone

cyclone does not have a [spectrogram~] object

ELSE has [spectrograpg~] though.

About formant synthesis with FM, I know Miller includes something like that in the audio examples (see F10). Is it related maybe?

nice, I had an older code 0.06 that I don;t know where I got it from and I tried to include that one back into Pd's extra, but it wasn't working. This [paf~], on the other hand is

sure, but I still have to mature, learn and be sure of things and it's always been weird to me cause you have vosim, and fof, and paf, and filterbanks and whatnot... it's just a hard topic to cover and now I have to figure out the relationship between these all. If anyone could help, please say so

I'm looking at messages I sent to the Pd list in 2017, where I was asking about how to do the Formant Ugen from SC in Pd, hahahah.... see? It's been on my list forever... and 2017 was the first year of ELSE's development and my live electronics tutorial dates back to 2008... anyway... in the thread I say that the thing seems related to the fof opcode in Csound. And now I have to look into the source code all over again.

thanks, will look into all that. i literally have had this in my to do list for over a decade, or even longer, like 15 years or so to cover this in my Live Electronics Tutorial, and this post now made me jump on this. Anyway, I can and should pull the object back since you do have a working windows version and I still have no idea what this is all actually about in details.

@seb-harmonik.ar said:

maybe should get on that

surely, I couldn't run it on apple silicon, for instance.

What was the source you used for this object? I'm doing a deep dive on it all now...

One thing I didn't get and changed, and maybe I screwed it up, is that I'm updating the phase step of fundamental and center frequency for every sample, but I saw that you were doing it only in some case conditions that I forgot now...

I am also looking into paf~ and several other related things and this seems pretty similar to paf~

grab [vosim~] for windows in https://github.com/porres/pd-else/actions/runs/20151921140

This is based on shadylib, I fixed some bugs, made some changes, will make some more like adding MC support and will study some more about the code, algorithm, other implementations before actually releasing anything. But i uploaded the commit so you can test and grab this one...

I will also work on paf~ and the other stuff

nice, this has been in my to do list for over a decade now

I can create some if you give me sources and point me to exactly what you're looking for

or...

from the help file of else/sfont~

let me recommend my ELSE externals instead of a nursing home

[pimp~] is [phasor~] + [imp~], which sends impulses at period transitions. The [toggleff~] (toggle flip flop) is an audio rate flipflop that alternates between 1 and 0.

it seems it stopped working in 0.56, as 0.55 is fine...

anyway, no idea how to fix this yet...

which version before exactly was working?

@sequentz said:

Any idea why this if failing now while with previous Pd version was working fine?

something changed and broke

I'll try to fix it

@ddw_music said:

Maybe like this? Instead of velocity --> envelope, derive a gate by way of [change]. Then multiply the envelope by the velocity value. The volume will change if the velocity changes on a slurred note. If you don't want that, it should be possible to close the spigot when slurring to a note, and open it only when a brand-new note is being played.

You're using [mono] here, it has a legato feature. On its own, it can control if you want retriggering or not, you can already do it, right?