Issue on macOS 10.14 Mojave

[meshonline]

Hi, I updated from macOS 10.13 to macOS 10.14, Soundflower has no problem, but no sound at all.

So I examined with Apple's CAPlayThrough sample project, I routed system sound output to Soundflower(2ch), I found that the input contents from Soundflower(2ch) are all zero, so the output contents are all zero too, thus no sound.

Before updates, Soundflower works very well.

[mattingalls]

open Audio MIDI Setup and verify all volume sliders are up and no mute buttons are enbaled.

[meshonline]

Just checked Audio MIDI setup, all volume sliders are up and no mute buttons are enabled.

[mattingalls]

well rebooting is always a good thing to try. i haven't looked at that PlayThrough sample code in a long time, but one thing that can result in silence is a feedback loop, -- if that or another app is reading and writing the same audio back to soundflower you will get that and it seems like the OS has a limiter or something that can get in a bad state when that happens

[meshonline]

I may found the reason, Apple have enhanced the runtime security on macOS Mojave, any apps that access runtime resources need to be authorized and properly code signed. To achieve this, you need to enable the 'Hardened Runtime' under 'Capabilities' tab in Xcode, and check the corresponding items, such as 'Audio Input' etc., when sign the app, there is a new option '--options runtime'. Refer to the video(https://developer.apple.com/videos/play/wwdc2018/702/), the contents from 27:00, but I have not tested yet.

[mattingalls]

Not applicable to Kernel Extensions

[mattingalls]

and just to be sure... you are using the 2.0b version? (which is signed) https://github.com/mattingalls/Soundflower/releases/tag/2.0b2

[meshonline]

Yes, I am using version 2.0b.

[meshonline]

I've tried to enable the hardened runtime with CAPlayThrough, Xcode automatically does code sign with the option of runtime added, but it won't help, I wonder if other persons have encountered this issue, or my machine just needs a clean re-install.

[zealfire]

Hi, I updated from macOS 10.13 to macOS 10.14, Soundflower has no problem, but no sound at all.

So I examined with Apple's CAPlayThrough sample project, I routed system sound output to Soundflower(2ch), I found that the input contents from Soundflower(2ch) are all zero, so the output contents are all zero too, thus no sound.

Before updates, Soundflower works very well.

The same issue happening for me too, after the update soundflower seems to have stopped working.

[Feli7]

Same Issue here. Running 10.14.

[mattingalls]

@Feli7 and @zealfire: sorry its not working. just so i can confirm everything, can you try this: 1) open Audio MIDI Setup 2) select "Soundflower (2ch)", and check to see that all 3 sliders are up and no mute buttons are enabled. 3) click on the gear icon on the bottom and select "Use this device for sound output" 4) open a file (constant loud is best) in QuickTime Player and start playing it (you should hear no sound as it will be sending it to Soundflower!) 5) select "New Audio Recording" in the File menu 6) a new "Audio Recording" window should appear, next to the record button, click on the little arrow and a popup menu should appear where you can select "Soundflower (2ch)" 7) if you see the level meters moving, Soundflower is working! if not, you can record some if you want to verify. once recording is over, go back to Audio MIDI Setup and change back the default output to your usual device. if the new recording is silent, that indeed means Soundflower isn't working.

let me know where the problem appears and we can troubleshoot from there

[meshonline]

Hello mattingalls, Everything is okay when I test following your steps, QuickTime can record from Soundflower (2ch and 64ch), Soundflower is working. The problem is, when I play with other apps via Soundflower, just no sound. Maybe macOS 10.14 Mojave has unknown features to prevent the apps from getting data from Soundflower.

[zealfire]

@mattingalls I can hear the recording from QuickTime player, also unlike issue faced by @meshonline I can see the input contents from Soundflower(2ch) fluctuating. I think the problem is when trying to hear audio from other app using Soundflower as a medium.

FYI, in my case, I am using WebRTC to listen to the audio.

[Feli7]

@mattingalls Hi guys, like @meshonline and @zealfire I was trying something else than a quicktime recording. I would like to route the audio streaming from Qobuz player to a AU Parametric EQ (configuring through Au Lab from Apple and rerouting all that to my USB external Audio card. When I'm selecting the streaming from Soundflower 2ch in the Au Lab app, the level meters don't and no sound is produced.

[hmedia1]

same also, using both 2.0b2, and building from XCode and manually signing & loading kext...

Device is present, but no audio. Levels are up, no mutes. Rebooted a bunch of times. It's only on 10.14 that it doesn't work.

[meshonline]

Hello mattingalls, Everything is okay when I test following your steps, QuickTime can record from Soundflower (2ch and 64ch), Soundflower is working. The problem is, when I play with other apps via Soundflower, just no sound. Maybe macOS 10.14 Mojave has unknown features to prevent the apps from getting data from Soundflower.

在 2018年10月22日，上午6:04，Matt Ingalls notifications@github.com 写道：

@Feli7 https://github.com/Feli7 and @zealfire https://github.com/zealfire: sorry its not working. just so i can confirm everything, can you try this:

open Audio MIDI Setup select "Soundflower (2ch)" click on the gear icon on the bottom and select "Use this device for sound output" open a file (constant loud is best) in QuickTime Player and start playing it (you should hear no sound) select "New Audio Recording" in the File menu a new "Audio Recording" window should appear, next to the record button, click on the little arrow and a popup menu should appear where you can select "Soundflower (2ch)" if you see the level meters moving, Soundflower is working. you can record some if you want to verify. once recording is over, go back to Audio MIDI Setup and change back the default output to your usual device. let me know where the problem appears

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RogueAmoeba/Soundflower-Original/issues/86#issuecomment-431708259, or mute the thread https://github.com/notifications/unsubscribe-auth/ANM5w8Gkvl8FrTZj-zKgIAKz5b1qOACNks5unO9xgaJpZM4XMHsd.

[mattingalls]

well if that QuickTime test works, then you have confirmed that Soundflower works. The problem is probably with your other apps (or how you are configuring them). AULab and CAPlayThrough are so old i would not be surprised there are problems. -- Also there's that added security stuff in Mojave to force users to allow use of the microphone (perhaps that means any audio input? )-- that could be the problem?

[meshonline]

I have noticed that QuickTime had prompted a window to request using the microphone, I checked Security & Privacy->Privacy->Microphone, QuickTime was there, maybe any apps want to use audio input should request as QuickTime does. The good thing is, Soundflower works.

在 2018年10月23日，上午1:56，Matt Ingalls notifications@github.com 写道：

well if that QuickTime test works, then you have confirmed that Soundflower works. The problem is probably with your other apps (or how you are configuring them). AULab and CAPlayThrough are so old i would not be surprised there are problems. -- Also there's also that added security stuff in Mojave to force users to allow use of the microphone (perhaps that means any audio input? )-- that could be the problem?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RogueAmoeba/Soundflower-Original/issues/86#issuecomment-431915514, or mute the thread https://github.com/notifications/unsubscribe-auth/ANM5wzjZABVUgsfNSW55PAk1zevr-K8-ks5ungbbgaJpZM4XMHsd.

[hmedia1]

Hello mattingalls, Everything is okay when I test following your steps, QuickTime can record from Soundflower (2ch and 64ch), Soundflower is working. The problem is, when I play with other apps via Soundflower, just no sound. Maybe macOS 10.14 Mojave has unknown features to prevent the apps from getting data from Soundflower. …

Seems this fixed it for Logic Pro X anyway ..

System Preferences -> Security & Privacy -> Privacy Tab -> Microphone -> Tick required app.

This seems to make Soundflower 2ch and 64ch work in Logic. Thanks for that.

Not sure how to get AULab into that list though. Any ideas ?

[meshonline]

Got it, I modified the CAPlayThrough project from Apple, it works now. The steps:

1. Add 'Privacy - Microphone Usage Description' item to Info.plist.
2. Add the following code before the app uses any audio input devices.

   #include <AVFoundation/AVFoundation.h>
   ......
   // check if the methods exist.
   if ([AVCaptureDevice respondsToSelector:@selector(authorizationStatusForMediaType:)] &&
   [AVCaptureDevice respondsToSelector:@selector(requestAccessForMediaType: completionHandler:)]) {
   // first time.
   if ([AVCaptureDevice authorizationStatusForMediaType:AVMediaTypeAudio] == AVAuthorizationStatusNotDetermined) {
       // prompt a window, let the user decide whether deny or accept the request.
       [AVCaptureDevice requestAccessForMediaType:AVMediaTypeAudio completionHandler:^(BOOL granted) {
           // do nothing here.
       }];
   }
   }

3. Add AVFoundation framework and Foundation framework.
4. Build and run.

The code will add the app to System Preferences -> Security & Privacy -> Privacy Tab -> Microphone, and enable it automatically.

[pagaille]

Had the same problem with AU Lab not working and indeed its related to the app being refused the access to the Microphone - go figure. Solution : download another copy of AU Lab and launch it, it will ask to access the so called Microphone again. You may delete the downloaded copy afterwards, the one in Utilities will work from then. Copy of AU Lab can be found here : https://www.apple.com/ca/itunes/mastered-for-itunes/

[Feli7]

Thank you pagaille. This trick finally solved the mute audio problem. Now I can apply a parametric EQ to my audio stream. It's working flawlessly with Qobuz. So even if you don't use the microphone input it is mandatory to grant the permission in the privacy security setting tab.

[Feli7]

I've seen this suggestion elsewhere - I've been unsuccessful in getting it to work, with numerous versions of AULab, including the one at the link provided and the newest one available from developer downloads. Have tried selecting the actual Microphone, and the interface in question, running it from downloads, running it from Applications, deleting everything first, etc ... Have not seen a prompt or an unticked allow box in the mic preferences.

It took me a while with at least three versions of Au lab. It's the best to have two copies of AUL in the same folder so that it gets renamed. At a certain point Mojave asks if AUL can use the Mic and you are done.

[meshonline]

I've seen this suggestion elsewhere - I've been unsuccessful in getting it to work, with numerous versions of AULab, including the one at the link provided and the newest one available from developer downloads. Have tried selecting the actual Microphone, and the interface in question, running it from downloads, running it from Applications, deleting everything first, etc ... Have not seen a prompt or an unticked allow box in the mic preferences.

Ir took me a while with at least three versions of Au lab. It's the best to have two copies of AUL in the same folder so that it gets renamed. At a certain point Mojave asks if AUL can use the Mic and you are done.

Maybe when you rename the app, macOS will treat it as a new app, then macOS prompts the window to ask you whether accept or deny the usage of microphone?

I have tested with another Java app, when I build from source code again, it always prompts the window to ask me if I allow the app to use microphone.

So the trick is let macOS Mojave think that the app is a new app, rename the app may work?

[Feli7]

I've seen this suggestion elsewhere - I've been unsuccessful in getting it to work, with numerous versions of AULab, including the one at the link provided and the newest one available from developer downloads. Have tried selecting the actual Microphone, and the interface in question, running it from downloads, running it from Applications, deleting everything first, etc ... Have not seen a prompt or an unticked allow box in the mic preferences.

Ir took me a while with at least three versions of Au lab. It's the best to have two copies of AUL in the same folder so that it gets renamed. At a certain point Mojave asks if AUL can use the Mic and you are done.

Maybe when you rename the app, macOS will treat it as a new app, then macOS prompts the window to ask you whether accept or deny the usage of microphone?

I have tested with another Java app, when I build from source code again, it always prompts the window to ask me if I allow the app to use microphone.

So the trick is let macOS Mojave think that the app is a new app, rename the app may work?

I think so. Even if you don't need to use microphone input you must grant the access to the microphone in the privacy settings.

[pagaille]

So the trick is let macOS Mojave think that the app is a new app, rename the app may work?

My quick test doesn't seem to confirm this. Moreover, when right clicking and showing the target in finder, it still shows the downloaded one, tough I use the former in Application. More something like a bundle ID or whatever the name is.

[meshonline]

Yes, simply rename the app does not work, if we download the same app to the same directory, macOS will rename the app automatically, maybe this way works.

在 2018年10月31日，上午2:09，Matthieu notifications@github.com 写道：

So the trick is let macOS Mojave think that the app is a new app, rename the app may work?

My quick test doesn't seem to confirm this. Moreover, when right clicking and showing the target in finder, it still shows the downloaded one, tough I use the former in Application. More something like a bundle ID or whatever the name is.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RogueAmoeba/Soundflower-Original/issues/86#issuecomment-434407259, or mute the thread https://github.com/notifications/unsubscribe-auth/ANM5w_qDBdNdOju3ekRo8tmgvgz5P8e-ks5uqJXFgaJpZM4XMHsd.

[hmedia1]

By using an app (such as FFmpeg) to trigger the allow mic input for "Terminal.app", I was then able to launch my AULab preset by invoking like:

"/Applications/AU Lab.app/Contents/MacOS/AU Lab" MyPreset.trak &

And it works because of the allowance given to Terminal.app

The main problem is that to save "clickable" presets requires manually wrapping them one by one.

[kybernetyk]

FYI you don't need to play around with having 2 copies of an app and renaming it to trigger the prompt. Simply run tccutil reset Microphone in terminal to reset the microphone (really unlucky name as it applies to all audio input streams) permissions.

[hmedia1]

Doing that resets permission for all apps, but does not trigger the permission for AU Lab

[daddysound]

I have been using Au Lab with Soundflower for years . It does exactly what I want it to do. I updated to Mojave last week...It won't work any more. I downloaded the latest signed version 2.02B . still don't work, checked all the audio outputs...no luck. Only thing to do . Timemachine, and back to High Sierra; All ok . All these fixes in the discussion seem to be very complicated, Please let me know when we can use Soundflower and AU Lab as easily as before with Mojave, and I will update again .

[gervaisc911]

Hi, If it may help you, by doing the slider trick in Midi app worked for me. I use Mojave and Soundflower was not working before the Midi trick. See here https://www.mac-forums.com/music-audio-and-podcasting/340016-solved-tricky-soundflower-giving-audio-quicktime.html

[daddysound]

Thanks

Envoyé de mon iPhone

Le 4 janv. 2019 à 01:27, gervaisc911 notifications@github.com a écrit :

Hi, If it may help you, by doing the slider trick in Midi app worked for me. I use Mojave and Soundflower was not working before the Midi trick. See here https://www.mac-forums.com/music-audio-and-podcasting/340016-solved-tricky-soundflower-giving-audio-quicktime.html

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[2albion]

@Feli7 and @zealfire: sorry its not working. just so i can confirm everything, can you try this:

1. open Audio MIDI Setup
2. select "Soundflower (2ch)", and check to see that all 3 sliders are up and no mute buttons are enabled.
3. click on the gear icon on the bottom and select "Use this device for sound output"
4. open a file (constant loud is best) in QuickTime Player and start playing it (you should hear no sound as it will be sending it to Soundflower!)
5. select "New Audio Recording" in the File menu
6. a new "Audio Recording" window should appear, next to the record button, click on the little arrow and a popup menu should appear where you can select "Soundflower (2ch)"
7. if you see the level meters moving, Soundflower is working! if not, you can record some if you want to verify. once recording is over, go back to Audio MIDI Setup and change back the default output to your usual device. if the new recording is silent, that indeed means Soundflower isn't working.

let me know where the problem appears and we can troubleshoot from there

I've used Soundflower for years, but it doesn't work on Mojave. I've tried all of the above, but I DO hear sound in QuickTime although all the settings are correct. I've tried the slider reset I've also read about. I've uninstalled using the provided script, checked that files are gone from the Library, emptied the trash, rebooted and reinstalled repeatedly. No luck. Soundflower (2ch) is the output on Settings...Sound. I've tried monitoring via Audacity and it won't pick up Soundflower either, but will pick up the built-in mic just fine. It won't work with AU either. Any suggestions? Thanks.

[daddysound]

Hey I've use sound flower for ages, BUT with Mojave…it wouldn’t work any more. My setup is using Soundflower with AULab to make a global EQ for my iMac. Anyway after checking forums I got around the problem by doing a command « I » on the AULab application, and putting the app on « Lo-Res » try this with Quicktime ?

Le 24 janv. 2019 à 22:09, 2albion notifications@github.com a écrit :

@Feli7 https://github.com/Feli7 and @zealfire https://github.com/zealfire: sorry its not working. just so i can confirm everything, can you try this:

open Audio MIDI Setup select "Soundflower (2ch)", and check to see that all 3 sliders are up and no mute buttons are enabled. click on the gear icon on the bottom and select "Use this device for sound output" open a file (constant loud is best) in QuickTime Player and start playing it (you should hear no sound as it will be sending it to Soundflower!) select "New Audio Recording" in the File menu a new "Audio Recording" window should appear, next to the record button, click on the little arrow and a popup menu should appear where you can select "Soundflower (2ch)" if you see the level meters moving, Soundflower is working! if not, you can record some if you want to verify. once recording is over, go back to Audio MIDI Setup and change back the default output to your usual device. if the new recording is silent, that indeed means Soundflower isn't working. let me know where the problem appears and we can troubleshoot from there

I've used Soundflower for years, but it doesn't work on Mojave. I've tried all of the above, but I DO hear sound in QuickTime although all the settings are correct. I've tried the slider reset I've also read about. I've uninstalled, rebooted and reinstalled repeatedly. No luck. Soundflower (2ch) is the output on Settings...Sound. I've tried monitoring via Audacity and it won't pick up Soundflower either, but will pick up the built-in mic just fine. It won't work with AU either. Any suggestions? Thanks.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RogueAmoeba/Soundflower-Original/issues/86#issuecomment-457357603, or mute the thread https://github.com/notifications/unsubscribe-auth/ArQlbH1GcKDpM3J5h1ExCnxcIlA7I3OMks5vGiEagaJpZM4XMHsd.

[2albion]

Thanks for trying! Command-I didn't seem to do anything in AULab. I think Soundflower is busted, since it won't work with AULab, QuickTime or Audacity. I've routed sound from Mac mic to soundflower 2ch, but if I set an app's input to soundflower 2ch, there's no sound. Audio MIDI is not muted anywhere and all sliders are up. Other tips?

[johnwmcc]

Sorry to say I have the same problem on Mojave 10.14.2 trying to use Audacity 2.3.0.

In Microphone settings, Audacity shows up with a checkmark, but when set to Soundflower 2ch as input, there's no sound. And when I try to record using Soundflower 2ch via QuicktTime, still no sound on input channel in New Recording window.

PS. Maybe Soundflower didn't install fully? It appears in choices for input in Audacity and Quicktime, and in Audio Midi setup, but has never been visible in Applications. And I can't seem to uninstall it - ran the script, rebooted, but it is still there as possible inputs and outputs.

Any suggestions please?

PPS.

Maybe i didn't set it up right - when I try again, but in Audio Midi setup choose Soundflower 2ch input device as Output, it then DOES show up, with sound, in Audacity. So maybe it IS working after all?

[d1One]

Working great for me on Mojave 10.14.3 (18D42) however, every 5 to 10 mins i hear a small audio glitch, sounds like a buffer issue, anyone else? Any ideas?

[2albion]

PS. Maybe Soundflower didn't install fully? It appears in choices for input in Audacity and Quicktime, and in Audio Midi setup, but has never been visible in Applications. And I can't seem to uninstall it - ran the script, rebooted, but it is still there as possible inputs and outputs.

Same for me. I delete it using the uninstall script but it's still listed. Install goes fine. I check the files that are supposed to be deleted and they are. Still doesn't work with any application.

[mattingalls]

@d1One if you are using an app that just copies SF to a device without any drift correction (like AULab!) you probably will get a glitch. try using a multi-output aggregate device instead.

[mattingalls]

@2albion THE MOST RELIABLE WAY TO UNINSTALL

From the Finder, HIT Shift-Cmd-G and TYPE:

/Library/Extensions

Then inside that folder, look for a "Soundflower.kext" file. If there is one, DRAG it into the trash (you may be asked for the admin password)

REPEAT, typing in this folder path:

/System/Library/Extensions

RESTART your computer

[2albion]

Hi, Matt-- I've done this before and I've done it again. Soundflower successfully uninstalled. Still doesn't work. In Audacity, for example, I'm setting the Mac's output to Soundflower 2, then setting the input in Audacity to Soundflower 2, with the output on built-in speakers (with the sound turned all the way down to avoid feedback. No sound.

With AU, I can't get any sound with input set to SF2 or a multi-output device that includes SF2 or only has SF2.

Nothing is muted anywhere.

Thanks for your help on this!

[hmedia1]

Suggest this be marked closed - even if the unrelated troubleshooting chat continues.

This has nothing to do with Soundflower.

The fact that some apps work, and some don't is circumstantial, and this is completely related to Mojave's input audio security mechanism, and is app-dependent on how it works.

[2albion]

Not sure what you mean, hmedia1.

If you mean the problem is understandable if soundflower works with some apps and not others because Mojave may be blocking some apps, then that’s incorrect in my case — soundflower works with no apps whatsoever.

If you mean soundflower is blocked by Mojave’s security, then I think that’s a soundflower problem.

Or do you mean something else?

[hmedia1]

Not sure what you mean, hmedia1.

If you mean the problem is understandable if soundflower works with some apps and not others because Mojave may be blocking some apps, then that’s incorrect in my case — soundflower works with no apps whatsoever.

If you mean soundflower is blocked by Mojave’s security, then I think that’s a soundflower problem.

Or do you mean something else?

In both cases, it's not a soundflower specific issue.

In the first case - it's completely a local issue at your end. Most people on this thread, myself included, simply needed to realize how Mojave's hardened runtime affects our workflow with any coreaudio IO, be it some hardware device, or soundflower, and have isolated the issue to an unsupported app not fully compliant with Mojave, or otherwise found workarounds. If you are getting no audio in any app, then that's a different issue to what we're all having, and given that you're the only one, clearly shows it's not a matter of "soundflower doesn't work on Mojave"

In the second case - it's not soundflower that's blocked, rather an explicit trust has not been granted to the app that accesses the soundflower device.

[hmedia1]

Hi, Matt-- I've done this before and I've done it again. Soundflower successfully uninstalled. Still doesn't work. In Audacity, for example, I'm setting the Mac's output to Soundflower 2, then setting the input in Audacity to Soundflower 2, with the output on built-in speakers (with the sound turned all the way down to avoid feedback. No sound.

With AU, I can't get any sound with input set to SF2 or a multi-output device that includes SF2 or only has SF2.

Nothing is muted anywhere.

Thanks for your help on this!

Here's a few general things - I know some of it you've checked in your case but I'm adding it all for the sake of completeness. Thing is - Multichannel interfaces are one of those things where you really need to have all your ducks lined up in a row for it to work;

• Check that unloading the kext (that you think it is) removes the device from Audio MIDI Setup, and loading it causes it to appear again.

• Check that the sample rate is set correctly for the application - In some cases the app will force this, in others, especially hardware connections, everything like suffer great pain if set incorrectly.

• Check everything is loaded fresh: Quit all apps, go to Terminal and sudo killall coreaudiod

• Verify that the app you're trying to use (you say they all aren't working, so perhaps just try Quicktime or something that has been known to work) has asked for permission to use the Microphone or "accept input". Check this in System Preferences -> Security & Privacy -> Privacy -> Microphone

• If the app that's not working is not listed in the step above, try from terminal again: sudo tccutil reset Microphone and start again.

• Check that you can at least record sound using the computer microphone at this point. If you can't - there's something much crappier going on. Maybe a launchdaemon has been forced off, or some rubbish kernel extensions have been installed. Wiping it clean is a good prospect since there's no good reason to not be able to record the microphone after doing the above.

• For any app, (Quicktime for this example), you want to see this:

  

• If this is where you're not getting past, a simple trick to allow any Application launched directly from Terminal access to audio input, is to open Quicktime from Terminal, and go to File -> New Audio Recording. Once you've done this, you can then launch any app (such as AU Lab, or Audacity and it would use the same permission. This is a debugging step or an emergency workaround.

• Set the system default sound output to soundflower(2ch)
• Check the volume is up

• Start playing an audio file from Finder or iTunes

• I was able to get Audacity to trigger the input. But only using the latest version, and only after doing a sudo tccutil reset Microphone :

• Double check nothing is muted:

• Obviously there's the odd occasion where we miss the most basic thing because we've been chasing our tail with everything else, but obviously check that soundflower isn't just fully working but not selected as an input (i.e. maybe the app reverted back to a previous setting in the meantime).

Hopefully apple will make the process of connecting audio input to apps (both compliant or not) a little bit easier in future versions of Mojave.

[AmnonSkladman]

I'm actually having the exact same issue. Followed literally every single step here using my MacBook Pro and I still can't get AU Lab and Soundflower to work together - no sound comes out in any app. :s EDIT: Only when I try to use AU Lab and Soundflower. Otherwise, sound works fine.

[mattingalls]

UA Lab needs to be updated to use the new microphone security apple put in place

[KCDalbey]

Im a voice actor, installed Soundflower on my MacBook Pro running Mojave 10.14. It worked to record a streaming audio I needed but now I can't get audio from my USB connected audio interface. I can only get internal speakers to work, but my Audient ID14 now has no monitor capability even though I can see that it is getting signal. In Sound prefs/output I have chosen Audient ID14 but that does not work. I ran the uninstall script from 2.02b I believe is the pkg, and it said "Done!" no errors and removed the Soundflower entries from Sound output and input preferences but still no sound even after 2 reboots. Please help.

[KCDalbey]

Never mind. I uninstalled the mixer app, and rebooted and now my monitor is back. Go figure. I guess I complained after 1 too few reboots.