Yes, but this is only if you don’t need to use the microphone:
Go into the ChuckMainInstance.cs script, scroll down to the Awake() method, and comment out SetupMic();
This will disable the mic, and, at least in my experience, eliminates the OS prompt to give access to the microphone (when launching builds for MacOS in Mojave and Catalina)
Scott,
For the unskilled, do you have step-by-step instructions for the "easy workaround"?
In my own attempts, I have been (unsuccessfully) trying to alter the Info.plist to force it to prompt for Mic access.
Thanks,
davd
-----------------
David Loberg Code
School of Music
Western Michigan
PS - I’ve seen a version of this issue with Chunity and Unity when building games for MacOS and running them on Mojave or Catalina. There is an easy workaround that involves commenting out the mic setup stuff in the ChuckMainInstance (thanks Jack!), but I’m wondering if there may be other sticky issues…?
This looks promising for trying to manually convince the system that miniAudicle needs microphone access:
-----------------
David Loberg Code
School of Music
Western Michigan
In OSX 10.14 and 10.15 the System Preference => Privacy settings now have a feature to control third-party access to the mic and camera. The problem my students are encountering is that miniAudicle doesn't show up as an identified app on the list, so they can't click the box to allow access, and thus they can't use adc in ChucK.
Is there either:
a) a ChucK workaround?
OR
b) a system file or something to which miniAudicle can be manually added as a recognized app that uses the microphone?
Thanks,
-----------------
David Loberg Code
School of Music
Western Michigan