I did some further digging and noticed that the callback setting's value somehow ended up in a non-bool state, aka not 0 or 1.
Running "defaults read org.puredata.pd" (a system command that accesses the per-application preferences), yields
... callback = 100277760; ...
I'm not sure how this happened, maybe from one of my test builds? In any case, this value does not actually check the check box in the Audio dialog so the setting was enabled internally but I couldn't see that looking at the GUI.
Now that it's back to 0, everything is working as expected. I won't look further for now, but if this comes up again we might know where to look. It looks like a possible conversion issue.
On Aug 2, 2019, at 11:12 PM, Dan Wilcox danomatika@gmail.com wrote:
Ok. I figured it out. I thought I was going crazy and, since I many different builds of Pd for testing various things, I was also getting a bit lost as to what I might have changed and when.
At some point, I had enabled the "Use callbacks" checkbox in the Audio dialog. Using Forget all settings, then restarting Pd and enabling that checkbox will make Pd hang. Try it out Alex...
I know various questions keep coming up about this feature. Is it needed and, if so, is it needed on all platforms. For example, if it doesn't apply to macOS maybe we can hide the checkbox.
On Aug 2, 2019, at 10:59 PM, Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com> wrote:
Em sex, 2 de ago de 2019 às 17:50, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> escreveu: I tested with the following builds from Miller's site: 0.49-1, 0.49-1-i386, 0.49-0test5, 0.48-2, 0.48-1, 0.48-0. (0.47 and previous do not run as the GUI can't find Tk 8.4).
*All* hang my on system after doing the following:
- open Pd app
- turn on DSP
- open audio test patch
- turn off DSP
GUI goes unresponsive and pd core process pegs CPU. I then have to use "killall pd" on the command line.
not a problem for me doing exactly what you listed
Pd-extended does not hang and is able to restart audio after toggling DSP.
This is a strange issue as I don't remember when it started happening. I feel like Pd was running fine when I first updated to macOS 10.14, so I wonder if it's some sort of issuer with my system only. This is also not a problem on my macOS 10.13 machine at work.
On Aug 2, 2019, at 1:35 AM, Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com> wrote:
Em qui, 1 de ago de 2019 às 19:27, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> escreveu: You can also open the Activity Monitor app and search for "pd." If the process has hung, it may also display "Not Responding" next to it.
Well, like I said, I've been using Pd 0.49-1 without anything funny happening, no hanging whatsoever. At least without noticing it, and it all looks fine by checking activity monitor.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/