Please check our OBS Studio 28 Plugin Compatibility page or this pinned obs-ndi Issue.
If the capture card itself works, then we will take note of this, but it will likely be low priority to address this.
Without an OBS log from a version where it worked and a version where there is an issue, we cannot look into this.
You can change the theme to any other available theme via Settings -> General -> General -> Theme. You can also check out custom themes in our Themes sub-forum, or create your own theme to suit your needs.
There is a build available, so that is how we marked it. Whether or not you consider it safe enough for your needs/use-case is up to you. If we marked it as "In Progress", there would be people telling us that it's "Available" because there's an Alpha build. For the purposes of our compatibility list, we decided that "Available" meant that "a build had been released by the maintainer". We may consider writing up some kind of key to describe each status.
This really sounds like it should be in the the Mac Support forum or in our Discord server in either #macos-support or #audio-support.
No.
This is more of a support question. Please either make your own thread in Mac Support or join our Discord server and ask in #macos-support or #audio-support.
Yes, I redirected you because those places are more appropriate for addressing your specific question, in my opinion. It would be best to have a single, well explained post of "what is wrong" with a single log showing when it worked and a single log showing when it does not work. I believe it is more likely that someone in the places that I've suggested will understand the problem than someone watching this thread.
No. The AMF encoder should always run on the GPU that you load OBS on. If you want to use the AMF encoder on a different GPU, you'll need to force Windows to run OBS on that GPU. It's almost always recommended to run OBS on the discrete GPU.
have you tried OBS Ninja & Electron Capture, so much better than NDI simply capturing audi from browser sources.
Please try in OBS Studio 28.0.1 or the latest 28.0.x available. If the issue still occurs, please check our open GitHub Issues for macOS opened after August 1, 2022 to see if there is an appropriate GitHub Issue already open to track this. If an appropriate GitHub Issue does not exist, consider opening one with detailed reproduction steps.
As far as I know, we pull this list from FFmpeg. The first part of the item is the codec name, the second part in parentheses is the codec's base name. In either case, this does not appear to be an issue new to OBS Studio 28, as it also appears in OBS Studio 27.2.4.
I am so far unable to reproduce this on Windows. Please try reproducing this in OBS without any third party plugins.
As stated in the patch notes and earlier in this thread, we had to revert that feature because it was breaking settings for non-webcam devices, such as capture cards. We will revisit it in a future release.
