thank you, will study this, could you please add the missing

clone oddHarmonic~ 25
... couldn't create

@jameslo said:

what does it mean to low pass filter a signal at Nyquist, since the filter itself is subject to the Nyquist limit? Or maybe you have other reasons to do so?

Yes, that was wrong, I made many mistakes in that patch.

I'm still not convinced that comparing a signal with its upsampled version is meaningful. How do we know that the upper harmonics in the upsampled version are present and aliasing at the normal sample rate?

I see your point and I am not sure.
If this is the case, that whole concept would plop.

for measurement I wonder whether we should be instead passing the normal signal to an upsampled subpatch and then measuring how much energy is above 22050. Then again, that signal would look like a stepped signal in the upsampled environment, and that seems like it would have a lot of additional high frequency energy

No, I don't think so, as niquist reflects before upsampling. Even when using some upsampling filter, as in [inlet~]'s help, you can't un-alias an aliasing signal by upsampling !?

maybe you should try fft-split~

Yes, I was thinking about some steep FFT-filter,
https://forum.pdpatchrepo.info/topic/12245/perfect-filter-square-shape-filter
but don't know how to tweak it for different sample rates and with fairly precise cuttoff frequency, yet.

Bessel was not a good idea, high order Butterwoth is stronger, and everything needs to get calibrated, because the filter-slopes are messing with the result.

@jameslo @seb-harmonik-ar

Did you come up with something?

I made this:
qalias~.pd
quantify_aliasing_3c.pd
ups~.pd
(EDIT: all three UPDATED again and again now!)

Uses Bessel-filters from IEMlib.

As quick test bed:
Copy/paste or write your own object-chain in qalias~' arguments,
Thx to @svanya !

What do you think?
How to implement the FFT-filter?
How to improve?

To my surprise [osc~] starts to alias above 3400 Hz and [cyclone/wave~] is even worse!
I convinced myself that I can even hear it.

Do you know how to make a less distorted sine @ 44100 ?

@jameslo marvellous, thank you very much!!!!

Just added inlets~ and outlets~

generate-matrix-mixer-io.pd

EDIT:
Guess what, I couldn't hear anything )

Bug fixed: [r~] instead of [r]
mm_send.pd

Is there already some non-binary matrixmixer~ with signalrate modulation inputs?

How would you patch such?
A smart way with [clone] and subpatches?

Ideally I'd like to create

 [mmix~ 4 4] 

and get 4 inputs~
4 outputs~
and 16 modulation-inputs~

Which operating system?

At first: is Jackd server running?

Did you select Jack in PD's dropdown 'Media'? (there where you clicked "Configuratión Audio")

Check the routings of Jack in the commandline or with qJackctl.

EDIT: Retrigger the Trigger-boxes or use[*~ 1]instead of [*~ 0]

Linux has Jack audio routing.

Windows:
Jack on Windows
https://jackaudio.org/faq/jack_on_windows.html
seems not to be supported by all the DAWs

and VB-Audio Cable
https://vb-audio.com/Cable/

Did not try any of those two.
On some soundcards, like RME, you can do virtual routings, too.

@lacuna said:

(I would also recommend learning Vanilla first and start using other libs once you know basic vanilla-vocabulary.
...right click on the blank canvas > help , shows all vanilla objects...
Else you might be browsing huge lists of ojects of many libs for each problem to solve, instead of finding the solution by thinking in Vanilla, with it's limits in mind. )

I remember learning PD-Extended as beginner, and the crowded "extra" folder was overwhelming, as downsides:
There were libs for very specific tasks, that I never would have thought of (and get distracted by), different objects doing the same or almost the same, objects, that can be build with 3 Vanilla-objects, different authors with different terminology, design- and documentation-philosophies, ect.

The learning curve was steep, but in that time I thought Vanilla would be lame and only being used for embedded projects or by purists.

The death of Extended was a great loss, but later a revelation to me:
You can do "everything" (ok, not really) with Vanilla while the vocabulary is small.
And Vanilla is small enough to last, to get bug fixes, and run stable.

@ludnny not exactly what you are looking for,
but @IOhannes uploaded more vids,

And a shortcut for fast delete would be nice!
Just like an eraser tool!
Like:
hold ctrl+click on an object or wire
would be more immediate than select > delete.

I don't know why, guess the wavelength is too long for the FFT to follow the whole circle? But bigger window-sizes don't work neither...

Downsampling improves tracking of lower frequencies:

[sigmund~] in a [pd sub] with
[block~ 64 1 0.5] or 0.25 or 0.125 or 0.0625 ...

Yes, nb. 1

and don't change URLs or paths because links would break.
Just yesterday I was looking up the equations for waveforms in sinesum, knowing I can find them there.

In such a small community, every contribuition can help some.

I don't agree with, people don't touching Extended today, as many patches/contributions are made with/for it, those aren't maintained nor rewritten.
Once in a while I am running Extended to study some old patch and learn from it.

Making clear that extended is long outdated should be enough.
Highlight that it really does not go deep into DSP nor PD, with the strong advice to use other resources today.

Also, many libs, listed in the Flossmanual's objects dictionary are still available and up to date.
Those lists can still help in searching for some object for some specific task or fixing "red boxes", and I am not aware of something similar: Deken is missing descriptions of objects/libs.

(I would also recommend learning Vanilla first and start using other libs once you know basic vanilla-vocabulary.
...right click on the blank canvas > help , shows all vanilla objects...
Else you might be browsing huge lists of ojects of many libs for each problem to solve, instead of finding the solution by thinking in Vanilla, with it's limits in mind. )