Stefano Scarani

For the first time I use fzero ~ (since the excellent fidle ~ and sigmund ~ no longer work), and I find that it does not allow analysis above 2500 Hz. And more: testing with a ~ cycle, at 2000 Hz tell me that we are around 1000.

For  the first time I use fzero ~ (since the excellent fidle ~ and sigmund ~  no longer work), and I find that it does not allow analysis above 2500  Hz. And more: testing with a ~ cycle, at 2000 Hz tell me that we are around 1000.

For  the first time I use fzero ~ (since the excellent fidle ~ and sigmund ~  no longer work), and I find that it does not allow analysis ab

fzero~frequency-limit-2500-hz

I don't know about your problem, but here you can find 64-bit versions of fiddle~ and sigmund~:

Hi Stefano,
I don't know about your problem, but here you can find 64-bit versions of fiddle~ and sigmund~:
http://vboehm.net/downloads/


Thank you very mutch, it's a great news. 

2000Hz seems to be working fine for me here:

2500Hz is a real limit, though. The fzero algorithm trades good low frequency performance for poor high frequency performance.

You add nice content to teach a lot to others. Couponstechie giving 

 through this you could save more on shop of security cameras.

You add nice content to teach a lot to others. Couponstechie giving lorextechnology Coupon codes through this you could save more on shop of security cameras.

You might be able to get around that by upsampling it inside a poly~. Away from my computer at the moment so can’t test this, but if 2500 is represented within the algorithm as a fraction of the samplerate, increasing the samplerate should raise the cutoff point. You can test this by simply increasing your samplerate. If that works, wrap fzero~ in a poly~ Yourpatchname up 2.

You might be able to get around that by upsampling it inside a poly~.  Away from my computer at the moment so can’t test this, but if 2500 is represented within the algorithm as a fraction of the samplerate, increasing the samplerate should raise the cutoff point.  You can test this by simply increasing your samplerate.  If that works, wrap fzero~ in a poly~ Yourpatchname up 2.   

Yes, I agree. In any case the new fiddle~ and sigmund~ are better.

Yes, I agree. In any case the new fiddle~ and sigmund~ are better.
Thank


FWIW, the upper limit for fzero~ in Max 8 has been upped to about 8800 Hz.

More specifically, the max frequency is set to the sample rate * 0.2. So, higher frequencies are possible at higher sample rates. Realistically, the algorithm probably needs at least 10 samples in a period to work properly. 8820 Hz at 44.1 kHz sample rate is 5 samples, which is really pushing it.

I think that's nearly the top of useable fundamentals for audible music. I can imagine wanting to identify other fundamental frequencies, but I think that these are a bit of an edge case? At that point, the hottest fft bin is always the correct answer because there are no salient harmonics.

More specifically,  the max frequency is set to the sample rate * 0.2.  So, higher frequencies are possible at higher sample rates. Realistically, the algorithm probably needs at least 10 samples in a period to work properly. 8820 Hz at 44.1 kHz sample rate is 5 samples, which is really pushing it.

I think that's nearly the top of useable fundamentals for audible music. I can imagine wanting to identify other fundamental frequencies, but I think that these are a bit of an edge case?  At that point, the hottest fft bin is always the correct answer because there are no salient harmonics.

fzero~frequency limit @ 2500 Hz