Have you ever gotten any replies?

@benjones1987 Thank you again for your reply. My case was a bit different: the method func stream(_ stream: SCStream, didStopWithError error: Error) {...} was never executed. I only saw the system error/warning (a yellow log in the console). Because of that, nothing in the didStopWithError method is called (I added some cleanup logic in case the OS fails the stream).

@benjones1987 Thank you for providing this information. So you mean the error stoppage is now get caught in the method func stream(_ stream: SCStream, didStopWithError error: Error) {...} in Sequoia?

I need screen recording permission for screenshot capture and other functionalities. Additionally, video capture will be available in the near future. It was working fine for months; is there a systematic change in the API? Could you please explain why this error occurs and whether I must resort to using Core Audio for capturing system audio?

Hi, is this issue being reviewed?

Here is the FB number FB16635064. Thank you for your time!

Before Enabling Voice Processing: <AVAudioFormat 0x600001a69180: 1 ch, 44100 Hz, Float32> After Enabling Voice Processing: <AVAudioFormat 0x600001a5bb10: 9 ch, 48000 Hz, Float32, deinterleaved> As you can see, enabling voice processing significantly alters the audio format of the input node. In my case, the channel count increased from 1 to 9, and the sample rate changed from 44100 Hz to 48000 Hz. This change is consistent with the behavior mentioned in the StackOverflow post.

I’ve further tested the issue and found some interesting observations regarding the behavior of AVAudioEngine when enabling voice processing. I came across this StackOverflow thread https://stackoverflow.com/questions/72953588/why-enabling-voice-processing-on-avaudioinputnode-changes-channels-count-on-its , which highlights a similar issue where enabling voice processing (setVoiceProcessingEnabled(true)) on the AVAudioInputNode changes the node’s audio format, specifically the channel count.

Thank you for your response. I can confirm that I am seeing the same logs as mentioned above with just the relevant code in a small test project. I was already testing the Voice Processing feature in a focused environment. Here is the link to my test project: https://github.com/esphoenixc/AEC-BUG-TEST Please let me know if you need further details or additional steps to reproduce the issue.