Hi @streamlabs! Your fork of OBS is buggy and cannot use the Apple CoreAudio encoder, neither on Windows nor Mac, but instead always uses ffmpeg-aac, which means all your users are stuck with poor audio quality. The original OBS does not have this problem. Fix it maybe?
-
Show this thread
-
Another user already reported this bug to you, but instead of reading the user's logs, your staff provided some irrelevant advice, even though the logs provided clearly showed that the codec was successfully found, but initialization failed.https://howto.streamlabs.com/streamlabs-obs-9/coreaudio-encoder-couldn-t-find-available-bitrates-8871 …
1 reply 4 retweets 27 likesShow this thread -
I checked that the same thing happens on a Mac, and was about to send a report report on that site, but it requires YouTube or Twitch authentication (requesting WAY too many permissions) or one of a bunch of other services I don't have, and no plain email reg/login option. WTF?pic.twitter.com/dN3A9i9dFZ
3 replies 3 retweets 32 likesShow this thread -
So yeah
@streamlabs, since apparently you don't want to let me report bugs, and you don't pay proper attention to other users' reports either, you're getting a Twitter bug report. Let me know when it's fixed so I can stop telling dozens of DJs not to use your software :-)2 replies 5 retweets 44 likesShow this thread -
Replying to @marcan42
Hey there! We would appreciate investigating this further, but to collect the information we would need to submit a ticket/email. If you do not want to log in with our ticketing system you can send an email at support@streamlabs.com. Thanks!
1 reply 0 retweets 1 like
Hi! The user report that I linked already has all the relevant logs and information you need, so why don't you just reopen that? But really, all you need to know is that the CoreAudio AAC support does not work. At all. For anyone. It's simple.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.