![]() This is, admittedly, a mess, with over a decade of installing Plug-Ins, migrations etc. This makes my think that the problem lies somewhere in my ~/Library directory. I have built audacity 3.0.0-alpha-from source at github, and it fails in the normal way for my usual user. I created a fresh “test” user on my Catalina system, and Audacity 2.4.2 works fine for he/she/it. (Recommending running via sudo, which isn’t really an option.) Make sure to save your work before trying to quit Audacity.įurther to my report somewhere above. There may be some issue about closing/quitting Audacity when you have invoked it in this way. If you open System Preferences, and look in the Security and Privacy pane, with “Microphone” checked, you should see that “Terminal” has been granted the privilege to access the microphone. In my case, once the permission had been granted, Audacity seemed to work normally. I forget whether the Audacity interface was already up, or appeared subsequently to the “yes”. With any luck, a box will float up somewhere asking you if you are happy for “Terminal” to access the microphone or sound-card or something. (I am not sure if the final “ ” is necessary, but it does no harm") you can enter, in a terminal window, command lines that start with “sudo”.Įnter this: “sudo /Applications/Audacity.app/Contents/MacOS/Audacity ” ![]() I assume your user has admin privileges, ie. The following is a “hack” to side-step the problem, that worked for me. The problem is that audacity cannot connect to your input source because of a bizarre permissions problem. The problem is not that the sample rate is wrong (though it may be). If your problem is anything like mine, then the error code is a red herring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |