Open gusio opened 6 months ago
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.
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
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 ?
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:
1) 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.
2) 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) ?