@solipp Thank you!

@ddw_music This is basically what I ended up doing. It's clunky, but it works. It looks like the feature request on github that @oid mentioned would fix the problem in a much cleaner way.

@solipp Thank you! There is an issue with pp.xypad. When zoomed in (ctrl+ on Windows), the green dot does not track with the mouse. Pd's default text size is too small for me, so I'm almost always zoomed in on Pd patches. I believe I've seen a similar issue with the scroll bars in other Audiolab objects.

@alexandros Yes, I tried enabling Init. It did not work.

I'm using [savestate] to save the state of a toggle in an abstraction. If that abstraction is in the main patch, it works properly. If that abstraction is imbedded within another abstraction, the state isn't saved and restored properly. This seems like a bug to me. Is there a way to save the state of a toggle that is in an abstraction inside of another abstraction?

I've attached a zip with three files that demonstrate the problem. test_save_toggle.pd is the main patch. It has two instances of the test_save_toggle2.pd abstraction. If you set the toggle in one of those and save the patch, the state of the toggle is saved correctly. The main patch also has two instances of the test_save_toggle3.pd abstraction which only contains an instance of test_save_toggle2.pd. If you set the toggle in one of those, the state of the toggle is not save correctly.

test_save_toggle.zip

@porres I'm not going to try to debug your code for you. Have you had anyone else try it on Windows? Don't you care whether it works properly on Windows?

@porres If you can't do anything about it, then you shouldn't call it paf~. Miller Puckette invented paf~. His paf~ is the standard. Yours doesn't work the same or sound the same as Miller Puckette's paf~ on Windows.

@porres @porres If the code on Windows was the same as the code on Mac, they would work the same. They don't work the same, so they must be different.

Here's the object I made from F13.paf.control.pd:
mypaf~.pd

And here's a version of your patch that uses it:
1767288702629-paf-test.pd

@porres There is different code running on Windows than on Mac. That must be where the problem is.

FWIW, I made a module using the implementation of paf~ in F13.paf.control.pd, and it works the same as Puckette's compiled paf~, with the same differences from else/paf~.

@porres You can see the problem in my previous post, but it's easier to see and hear the problem with lower bandwidths. Here are the results using your patch with bandwidth=10.

@porres Puckette's paf~ and else/paf~ give different results and sound different. As you can see in my last post, all of the harmonics have different volumes. The second and third harmonics are louder in Puckette's paf~. All of the other harmonics are louder in else/paf~. The differences are even more dramatic with lower values of bandwidth.

@porres I had to add paths to your patch. The result is the same as my patch.

@porres With Puckette's paf~, the 528hz peak is -6dB. When I don't multiply else/paf~ output by 1.3, the 528 hz peak is -8dB. When I multiply else/paf~ output by 1.3, the 528 hz peak is -6dB, like Puckette's paf~. This image is with bandwidth=10. The peaks are the same with bandwidth=80.

@porres I'm using Pd 0.56.2. I tried this on both Windows 10 and Windows 11 and I get the same results. What OS are you using?

I don't add externals to Pd's path. Does else/paf~ expect to find something in the path?

I had to multiply else/paf~'s output by 1.3 to match the level of Puckette's paf~. Is that the same for you?

@porres I’m away from my computer for a few hours. When I copied the else modules, I didn’t copy the subdirectories. Is there something in a subdirectory that I need?

@porres It's easier to see and hear with bandwidth = 10. It's also easier to see if you set the top of the pp.spectrum~ range to 2024.

@porres I already uploaded the fix.

@porres I can easily hear the difference between Puckette's paf~ and else/paf~ with bandwidth set to lower values. The difference is more subtle with higher bandwidth values. When using formants to create vowel sounds, the bandwidth is normally under 200.

@porres My patch used some of my own objects so I made a new patch that doesn't use them. Oops, there was a problem with the first one so I uploaded it again.
paf~test.pd

I multiplied the output of else/paf~ by 1.3 so that the level of the highest peak would match Puckette's paf~. I used a frequency range of 30 hz to 2024 hz in audiolab/pp.spectrum~

@porres The cosine version looks the same as before with fundamental=264, formant=650, bandwidth=10. The top spectrogram is Miller Puckette's paf~, bottom is else/paf~

I just noticed one small difference; the cosine version has a small peak below 40hz that the previous version didn't have.