MAC OS CATALINA

[FredLam11]

I can't launch Audacity ever since I upgraded my Mac to Catalina, so I am holding on to the Mojave on my MacBook in order to have access to Audacity!
May be I'll try the suggestions from some of the forum members, hopefully it can work!

[BonnieO]

Hi guys.

I'm running Audacity 2.3.2 on a MacBook Pro and for the first time, didn't do my research before upgrading to the new OS - Catalina 10.15.1 (19B88).

I've tried the workaround using the Terminal app. The command runs but never asks for any permissions. Upon opening Audacity and testing, there's nothing recorded.

I've also tried creating an alias for the desktop to no avail.

I've been following this board but thought I'd check once more before going through the pain of reverting back to Mojave.

Any idea when this hurdle might be overcome?
Any idea why the workaround doesn't work for me?

Thanks so much,
Bonnie.

[steve]

Any idea why the workaround doesn't work for me?

Try adding permission for the "Terminal" application to use the microphone, then try again launching Audacity from the Terminal. As far as I'm aware, permissions granted to the Terminal should carry over to applications launched from the Terminal.

[kozikowski]

going through the pain of reverting back to Mojave.

Post back how that goes. It should be possible from Time Machine, right? That's the street wisdom, anyway.

I use a backup system in addition to Time Machine. I got burned once with Time Machine when it didn't give me direct access to some work I really needed. I talked to one of the System Administrators at work and he said make a copy of /Users. That covers plain file versions of Desktop, Documents, etc. That's been very handy. I also have a folder called Installers-Keys-Settings which has application notes and Disk Images—and, in the case of Firefox, a dated copy of my bookmarks in both native backup and html.

All this assumes I have enough room on home backup drives. I don't use cloud storage.

Is that obsessive enough? I haven't lost anything in years.

Given where I live, California, Land of Fruits and Nuts, it is still possible to have enough geologic damage to wipe me out so I've been known to send backups to my sister in Schenectady. Thumb drives rule.

Koz

[kozikowski]

I am infinitely grateful to my sister for living in a city with a funny name.

Koz

[ibojan]

How do you do this? any steps? I am new to this

[melaniesandra]

It keeps saying "Bad CPU type".

Where did you get Audacity from?
If you downloaded it, approximately when did you download it?

I do have the same problem, doing the above mentioned workaround with opening audactiy within the package content, gives me a terminal shell reply
''~ % /Applications/Audacity.app/Contents/MacOS/Audacity ; exit;
zsh: bad CPU type in executable: /Applications/Audacity.app/Contents/MacOS/Audacity

[Process completed]''

I run Audacity 2.2.1 and downloaded this version just a couple of weeks ago.

[steve]

I run Audacity 2.2.1

Audacity 2.2.1 is a 32-bit app.
Catalina does not support 32-bit apps.

Audacity 2.3.3 is the current version of Audacity, and it is a 64-bit app. You can get Audacity 2.3.3 via the links on the Audacity website: https://www.audacityteam.org/download/mac/

[melaniesandra]

thank you so very much, it works again happy dance

[phraktyl]

Neither the Terminal or the shortcut work arounds worked for me with the latest Catalina (10.15.1) and Audacity 2.3.3. However, I did find another solution:

Hold down <control> when you click on the app and select Open. This allows you to bypass Gatekeeper for the app. Further, after you've done this once you can open the app like you normally would after without any workarounds at all.