-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doesn't capture new Teams and doesn't detect Spotify #262
Comments
YOu sure you didn't use OBS's native BETA capture instead of plugin? I know the native beta seems to be case sensitive with proces description while the plugin isn't. |
100% sure |
OK. Then only thing I can suggest is that check in OBS audio settings that you're on stereo, not on mustichannel mode. Plugin doesn't natively handle multichannels. |
Thanks for the suggestion but it really seems like it is a problem with the new version of teams that has to do something differently which would require an update. I have used the same setting before - and yes I am on stereo |
What's the situation with this module anyway - is it still maintained ? Would be a better idea to maybe post issues on BETA version under OBS repo ? |
@gusio hi gusio, I have the same problem as you. I have a demo program (non-OBS) to collect the sound played by Teams. The problem is that I can't collect the sound played by Teams. I don't know if Teams has any special Settings. Can you tell me how you changed the Teams or computer system Settings to solve this problem? Thank you very much. |
As for the latest versions of OBS, there's application audio capture option now on the source's options itself and this was the deal which overran the need of the plugin. |
ok, The essence of the problem is the manner in which ActivateAudioInterfaceAsync get teams play the sound, it should be have a special broadcast teams logic, and other software is different. |
Thanks for looking into it. Is there something that can be done about it ? Are there any new releases planned ? |
I think it was 'always' there - it was named BETA but iirc it had limited functionality compared to this one |
I've seen the two recent issues about the plugin not working but they are not specifying much so i am not sure that what happens to me is the same thing.
in my case i have two following issues:
The new Teams app is not getting captured anymore. the version i am using is:
I am on Windows 10, 22H2 (19045.3803). I tested it with foobar and spotify and it captures the audio correctly. I have added both Teams executables to the list - ms-teams.exe and msedgewebview2.exe - with no luck.
Spotify doesn't get detected so i have to add it manually instead of using the drop-down menu. My Spotify version is:
I also noticed that the plugin seems to be case-sensitive - when i chose spotify.exe it wouldn't capture anything, it only started working when i typed in the correct process name - Spotify.exe
Would it be possible to implement the case agnostic behavior when detecting the executables (Windows itself doesn't care about it, unlike linux) ?
The text was updated successfully, but these errors were encountered: