@schitz I don't know serum but I glanced at a few demo vids, and like @seb-harmonik.ar says, the stuff you want to look into is waveshaping and wavetables.

For the particular mirror effect, I take it you mean the possibilty to draw a wave segment and have it played back with a mirrored segment as discussed here: https://www.youtube.com/watch?v=JVCH-IiDmnc&t=311s - I made a crude demo patch to illustrate how that can be done with some basic waveshaping and table tricks. Mind you, this is "proof of concept", not "plug and play" -> WaveDrawMirror.pd

Since you asked for resources, why not check out Miller Puckette's book -> http://msp.ucsd.edu/techniques/latest/book-html/node26.html (wavetables) + http://msp.ucsd.edu/techniques/latest/book-html/node78.html (waveshaping) - Don't get scared by the hairy math, there are illustrative examples with counterparts in your pd installation (help->browser->puredata->3.audio.examples)

@mikkejos22 It could be that inharmonic partials in the lowest piano notes affect the ability of [sigmund~] to identify the fundamental.
A pure sine wave probably works down to 41Hz but a complex wave is problematic.
This site by @katjav is an informative read (for everything fft)......... and https://www.katjaas.nl/helmholtz/helmholtz.html specifically for your problem.
The fundamental is often not actually the strongest harmonic in a complex wave.
You might find that increasing the number of samples for the [sigmund~] window will help.
David.

@mikkejos22 There does seem to be a limit.
Some suggestions here........... https://forum.pdpatchrepo.info/topic/13480/sigmund-lowest-detectable-frequency-41-hertz
And doubling the frequency first should help a little. See G06.octave.doubler.pd in your Pd/doc/3.audio.examples folder.
David.

In an attempt for a complex transinstrumental project (turning one instrument into another) I ran into a rather unexpected issue. The Sigmund~ object is used and and I pass it as sigmund~ notes . I thought this would be a simple note tracker however when testing it on my piano any time the note was lower than about C3 or E3 it would not output any frequency for the command where as any other note provided it was loud enough would. Is there any way to ensure a stronger response to bass frequencies out of sigmund~?

@60hz Yes...... a tcl plugin.
Derived from the hard work put in by @seb-harmonik.ar............ https://forum.pdpatchrepo.info/topic/10943/a-little-pd-mod
Curves have eluded me so far although maybe doing his whole vanilla Pd modification would work (not sure using windows7).

It requires sys_gui from the hcs library to send messages to tcl if you want to turn it on/off.
segmented-not-curved.zip

David.

I am starting to dabble in using sigmund~ but it seems to take up a good bit of the CPU. Also, the numbers move so fast I am not sure the best way to "capture" the data generated. I am using average, but that does not seem to capture the data well.

I am trying to use sigmund well, but am struggling.

Hello!

I'm using pd-vanilla (0.50.2-3) on ubuntu studio 20.04
It was installed by default (so I didn't build it myself).
When I try to create a sigmund~ (or even fidle~ or bonk~) object, I have this error:

/usr/lib/puredata/extra/sigmund~/sigmund~.pd_linux: /usr/lib/puredata/extra/sigmund~/sigmund~.pd_linux: undefined symbol: __pow_finite
/usr/lib/puredata/tcl/../extra/sigmund~/sigmund~.pd_linux: /usr/lib/puredata/tcl/../extra/sigmund~/sigmund~.pd_linux: undefined symbol: __pow_finite
 sigmund~
... couldn't create

There is a file /usr/lib/puredata/extra/sigmund~/sigmund~.pd_linux
I red about an almost same issue here https://github.com/pure-data/pure-data/issues/975 but didn't find a solution I may understand.
Some says this problem is common since 20.04 but didn't find any other topic about that searching on google.

Would someone have any clue?
Thx!

EDIT: I found out that on an other boot I have (MXLinux), installing puredata (which install by default in 0.43 (or 49? not sure...)) gave me sigmund~ working fine. so I tried to copy the sigmund~.pd_linux file from this build to the one on my other boot (backuping the original one of course). But it didn't work.
Maybe I could try to install an older version of PD on my ubuntu studio (I need to use it on this one, because I didn't find how to build processing for MXLinux, which is essential to my usage). But I don't know how to proceed (where to found the package, plus I'm really not good in building package successfully ...)

Hi! Thank-you for this.. I think I misunderstood what minpower could do! Essentially, I was trying to use minpower to stop sigmund from reacting to anything too quiet, in that I wanted the resultant sounds from sigmund to react to the input - the louder the input, the more it reacted, the quieter the input the less you heard from sigmund (if that makes sense atall?!) I'm getting the sense with further testing that this is sort of how npeak reacts anyway?

thanks again for replying!

Hi,
Isn't the -minpower flag meant to set a lower db threshold by which the analysis will take place?
In other words unless the minpower value is reached the object won't analyse the incoming event.
Also 50 is the default so in fact you don't need to flag it if you want to set the minpower to 50. This could also be why you are not noticing any effect.

If npeak is working are you not getting the result you want?
(to see the results:
[sigmund~ -neak14]
|
[route 0 1 2 3 4...]
|
[unpack 0 0 0 ...]
|
number boxes for 14 outlets

If you are getting too many/too fast values you can slow down and spread out the analysis by increasing the -ntps and -hop values.

You can reset flags by sending the object. a new argument value in a message box.
This is detailed in "pd setting parameters" in the sigmund~ help file, and in fact the -minpower flag is the one they use as an example.

This is a pretty common way of updating some arguments to some objects in Pd, super useful.
Hppe this helps!
best,
Jorge

Hi All - first post here, I'm pretty much as green as can be with PD but have been working on a 'live' patch for a while now...

I think i'm confusing the order of something here in sigmund~. I'm trying to use 'minpower' to measure the level that is reporting a pitch but wherever I have it in the argument - it doesn't seem to have any effect whatsoever!

currently written as "sigmund~ -minpower 50 -npeak 14 peaks"

npeak works regardless... have I done something completely idiotic here? am I missing a stage? Also, assuming I can fix this issue - can I use a number box/slider to change the minpower number in real time?

Many thanks indeed