Joshua

just want a frequency from my MacBook mic, but somehow it just stops reporting freq after 3 seconds when I sing a middle E (or any other note haha). I updated to latest Max (7.2.1) but still... also the help patch shows this '3 seconds limit'. Is this a feature or a bug?

My patch (sending freq over OSC and reports in console):

fzero-stops-reporting-pitch-after-3-seconds-bug

I'm not able to reproduce your bug on either MacBook I have access to. Could you tell us a little more about your audio setup? Vector sizes? Which version of the OS?

PS, you probably don't need the OpenSoundControl object in this context, although it won't hurt anything.

I'm not able to reproduce your bug on either MacBook I have access to. Could you tell us a little more about your audio setup?  Vector sizes? Which version of the OS?

PS, you probably don't need the OpenSoundControl object in this context, although it won't hurt anything.


Hmmm interesting, ok I updated to the new release. Seems to work fine indeed. Great!

Just got back to Max after 20 years so I feel I'm fooling around (trail & error).

Thank you for checking and for the OSC hint!

Hmmm interesting, ok I updated to the new release. Seems to work fine indeed. Great!
Just got back to Max after 20 years so I feel I'm fooling around (trail & error).

Thank you for checking and for the OSC hint!


I wonder if there is been a regression here. I'm trying to use fzero~ but have found that it will stop reporting after 1-4 minutes, consistently. I've tried it with various Audio Status settings with the same results. Even the simplest of patches at the default settings will not work for me for more than a few minutes:

Can anyone confirm this behavior, or better yet, have a solution?

Max 8.1.10
macOS 10.14.6
MacBook Pro (Retina, 13-inch, Late 2013)

Update: I have run further tests on a newer MacBook Pro (2019, 16inch) and can confirm the issue there too. Perhaps not quite as quickly, but it's already happened several times.

I've also been running a test on Windows and have yet to see the problem there.

Update: I have run further tests on a newer MacBook Pro (2019, 16inch) and can confirm the issue there too. Perhaps not quite as quickly, but it's already happened several times.

I've also been running a test on Windows and have yet to see the problem there.

I have the same problem on Windows. 30 minutes or so, fzero~ stops working. (Probably depends on computer, and depends on processor speed ...?) 

As a work-around, I created "fzero working checker". This automatically detects fzero stopped, then automatically restart the DSP. (also sends heartbeats as OSC message, this is just additional. )

Why I created this is, I found that if one fzero~ stops, other all fzero~ also stop working.

However, this is just as a temporal solution. I'd like to know how to solve this...

I have the same problem on Windows. 30 minutes or so, fzero~ stops working.   (Probably depends on computer, and depends on processor speed ...?) 

As a work-around, I created "fzero working checker". This automatically detects fzero stopped, then  automatically  restart the DSP.  (also sends heartbeats as OSC message, this is just additional. )

Why I created this is, I found that if one fzero~ stops, other all fzero~ also stop working.

However, this is just as a temporal solution. I'd like to know how to solve this...

Hi All. Strongly suggest you report this to cycling74 support will the details on how to reproduce.

I'm experiencing this very frequently just after the 2 minute mark. 

Has anyone reported/had feedback from Cycling74?

I'm experiencing this very frequently just after the 2 minute mark. 
Max 8.5.7
MacOS 12.7.2
Intel, 2019, 16-inch

Has anyone reported/had feedback from Cycling74?


I'm experiencing something similar - except that it appears to be triggered by interacting with the Max UI (even just clicking on 'About Max').

It's not instantaneous either - it looks like updated output slows to zero-updates over the matter of a few seconds - as if recalculations are getting swamped.

Further info - if I momentarily disable, then re-enable, the input source (I'm using ezdac~) - then fzero~ starts working again.

This is an issue for me too. I'll report, but wondering if anyone has updates?

if you get such fzero~ problems use something else instead,

or if restarting dsp solves the problem, try :

FZero~ stops reporting pitch after 3 seconds (bug?)