Hello!
I am fairly new to this, but I downloaded the 64 bit about 3 weeks ago and I absolutely love it. The only thing is I have run into a few bumps in the road.
1. I play quite a bit of Valorant, and have made an audio source for that which works for my stream, where I can mute and unmute it on my stream. However, for some reason, the Voice-chat for in-game Valorant seems to not be registered to the Valorant audio. I tried trying to connect another application (possibly trying to see if there was a separate audio output I could create) but unfortunately there was nothing. I deleted and created the audio output again as well as making sure my Valorant in game audio was being sent to the create output. I am not sure if that is just a bug, or I am missing something... but if anyone has any ideas let me know!! Also sidenote, the voice chat for any other game works perfectly with the separate audio output.
That's because Valorant's communications happens on a completely separate process, one without a window, which is what this release of the plugin is supposed to address. Instead of enumerating windows, it apparently walks process trees, looking for processes which are emitting audio so the plugin can capture it.
Someone here who plays Valorant will have to help you as I do not play it myself given its insanely overzealous anti-cheat software, Vanguard.
2. When I am streaming, you cannot hear my alerts go off. I was looking back at my stream from the other night and noticed you could not hear the alerts audio, however while I was live I was able to hear it all. It is confusing because I tried to connect an additional audio output but am not sure what would be the correct audio to connect it to. If there is something I am missing let me know.
Before I continue, two things:
1. This has nothing to do with the plugin.
2. You do not want to connect any audio pipeline endpoint that doesn't need connecting.
With that out of the way...
If I may venture a guess, your alerts are browser sources, right? In my experience, most users' alerts are, whether from Streamlabs, StreamElements, OWN3D, Rainmaker, or whatever, are browser sources.
That said, this situation has NOTHING at all to do with the plugin if you're using browser sources. The OBS-bundled browser source plugin can send its audio DIRECTLY into OBS Studio's workflow, so there is no need to use any audio pipeline endpoint (examples being virtual audio cables, VoiceMeeter inputs or outputs).
What you need to do is open the properties for your browser-sourced alert boxes and make sure there's a check/tick in the "Control audio through OBS" checkbox/tickbox. That way the browser engine in each instance can send its audio into OBS's mixer, which will give you a slider for that source.
Thank you again for creating the software though. Other than those 2 things I really like it and enjoy being able to listen to non-copyrighted music and stream at the same time lol!
Actually, only one of the issues described here involves the plugin. The other is in the default OBS installation.
Anyway, I hope this helps.
--Katt. =^.^=