mopsafety.blogg.se

Virtual audio cable teamspeak 3
Virtual audio cable teamspeak 3




virtual audio cable teamspeak 3 virtual audio cable teamspeak 3

So it would seem to me that Mumble is not respecting the audio output device settings.

virtual audio cable teamspeak 3

I then changed the "default device" (in Win7) to "Line 2" and Mumble audio was restored in both my speakers and the live stream feed. I then changed the "default communication device" (in Win7) to "Line 2", still no audio in speakers or live stream feed.

virtual audio cable teamspeak 3

So in my tests, even though the Mumble audio output device was set to "Line 2" but I changed the "default device" settings in Win7 to "Line 3", Mumble started outputting to Line 3 anyways. Sure as **** when I did this Mumble was no longer in the live stream audio, AND could not longer be heard over the speakers. I left the output setting in Mumble to VAC "Line 2" but changed the default device and default communication device to "Line 3" (a VAC line NOT in use, and NOT re-routed to my speakers). So then I decided to attempt further testing on Mumble since Mumble already seemed to be the direct culprit of not being able to obtain the desired results. Again, the audio from TS3 successfully did not play in my live stream audio feed, and only over my speakers as desired. So I again tested with TS3, setting TS3 output as VAC "Line 2", GW2 to output VAC "Line 1", and OBS audio input as VAC "Line 1". Luckily, at least for testing purposes, Guild Wars 2 does! Though as I mentioned, implicitly setting output/input devices on all these programs still failed, I could still hear the Mumble audio in the live stream audio feed. Again, I could STILL hear Mumble in my live stream audio! Not to mention this would not be optimal as most games don't allow you to implicitly configure their sound output device.

VIRTUAL AUDIO CABLE TEAMSPEAK 3 SOFTWARE

So again I set up Mumble to "output" to VAC "Line 2", a game to output to VAC "Line 1", and the audio input for Open Broadcaster Software to VAC "Line 1". Seeing as I prefer Mumble over TS3 (former teamspeak veteran going back to TS1, until I found out about Mumble) I would much rather have to do this, that rely on "defaults". So I figured okay, I will implicitly tell each and every program what input/output devices to use, instead of defaults. I didn't even have to change any input or output devices within all of the programs to get it to successfully exclude TS3 from the "live stream audio" segment. With all programs set to use "default device" as input/output VAC, TS3, Open Broadcaster Software, and a game to stream it worked just fine. I even re-installed TS3 (teamspeak 3) to test for desired functionality. With this exact set up I should be able to hear everything over my speakers, but Mumble should be excluded from the live stream. Both Line 1 and Line 2 'repeat' to my actual speakers so I hear everything. I set Open Broadcaster Software to take audio (for the live stream) from Line 1, I set Mumble to output device = Line 2. I set Line 1 as the default device, I set Line 2 as the default communication device. I set up VAC to have 2 virtual audio cables (at a minimum for the following purposes). So I set up Mumble, VAC (virtual audio cable), Open Broadcaster Software, and a program to stream (specifically Guild Wars 2, MineCraft, Perfect World, Counter Strike, etc.). So my overall goal is live streaming while excluding audio from Mumble in the live stream. Okay so here is my exact problem, and I have pinpointed that it seems to specifically be Mumble (at fault) and Mumble only that I have this problem with.






Virtual audio cable teamspeak 3