Brainspot wrote:These steps work for me
Run an application inside the Terminal.
1. Locate the application in Finder.
2. Right-click the application and select "Show Package Contents."
3. Locate the executable file. ... on my Mac its on /Applications/DaVinci\ Resolve/DaVinci\ Resolve.app/Contents/MacOS/Resolve
4. Drag that file onto your blank Terminal command line. ...
5. Leave your Terminal window open while you use the application.
After dragging the file to the Terminal, the Davinci Resolve application opens. I went to Fairlight and clicked the R button, and a popup appears asking to allow the Microphone on the Terminal. After I clicked yes, the microphone recording now works.
You can try this as a temporary solution while BMD is figuring out a way to include it in the next update.
Hi
Thanks for posting. I tried this and have replicated the same behaviour.
The app on my system is 'resolve' and the type is 'unix executable' when you're looking for it in finder.
Drag that to the finder, Resolve starts up as it should and then yes, when you click 'R' on a record track, it asks if Terminal can access the microphone.
Lo and behold, Terminal is added to your microphone security and privacy preferences, so it would appear as we suspected that for some reason Resolve 16.x is not forcing the OS to ask for that permission set.
If you create an alias in your finder to the Resolve unix executable and copy that out of the package contents to the level of your davinci folder, it makes it one or two less click steps to repeat and have this on hand to drag and drop into a terminal window as the route for starting Resolve up.
Thanks for posting a good work-around until BMD come up with a patch.
How's that progressing BMD guys, any idea on a timescale for customers on the development investigations and release schedule?
Hope everyone's keeping well in your respective national lockdowns, depending where you are.
Jason