I confirm that Dave¡¯s workaround below works on my configuration (4.2.05.24 on a M2 MacBook Air/ Sequoia 15.0.1) ? Thanks Dave!
I confirm that I too have zero issues with the mic access on my three Debian Bookworm boxes. ? I only have the mic problem when I byte the Apple :-(
toggle quoted message
Show quoted text
On Oct 11, 2024, at 09:07, Dave, W1HKJ <w1hkj@...> wrote:
I am the original and principal developer of fldigi.? I run the program on several different Apple h/w and OS versions.? The issue described below is only associated with the latest h/w and OS releases, including Sonoma
14.6.1 on all both Intel and Apple silicon.? I too count exactly 43 clicks to get past the microphone gate keeper.? I do not know what process in fldigi's start up code is causing the problem.? I can tell you how to avoid the gatekeeper.
- open a terminal window and execute the following set of commands:
- $ cd /Applications/fldigi 4.2.06 (for latest version)
- $ cd Contents
- $ cd MacOS
- $ cp fldigi ~
- $ cd
- $ ls (you should see the contents of your home folder with the fldigi binary present)
- run this copy of fldigi in one of two ways
- from the terminal window
- or from the finder
- open finder to the home directory and double click on the fldigi binary icon
- Either way, fldigi will open as a terminal application.? Be sure that you have granted microphone access to the the terminal.? You do this in the System Settings for "Privacy and Security"/Microphone.
- you may minimize the terminal window, but do not close it or fldigi will also close.
73, David,
W1HKJ
On 10/7/24 18:33, John Biccum, N7TIN wrote:
No, sadly nothing new on this issue in this version.
I¡¯m running??4.2.05.24 on a M2 MacBook Air (Sequoia 15.0.1) and confirm the "FLDigi would like to access the microphone¡± issue IS still present in this version.
It still takes *exactly* 43 (forty-three) clicks of the ¡°Allow¡± button before the ¡°microphone¡± (IC7300 in my case) is allowed access.
I wonder why it *always* works after the 43rd ¡°Allow¡±??
Could that number be helpful in find the the cause of this issue?
Anything new on the "FLDigi would like to access the microphone" problem?