There have been some people that have asked how I have all my video inputs setup for streaming. I recently updated my setup so I thought I’d make a post explaining everything. Let’s get right down to it, here is a diagram of my current setup. Look it over and we will start to go over it in more detail.
The goal of this setup is to be able to stream/record any console activity, as well as to be able view it on the television all without needing to swap any cables. I also want the ability to use the television as a third monitor for my PC if needed as well.
I recently purchased a HDMI switch. This one was nice because it comes with a remote that easily lets us switch between any of the inputs. We start by plugging both consoles and the video card into the HDMI Switch.
The output of the switch will run to the HDMI Splitter. I have the 1×2 version. Something about this particular splitter that we will need to make a note about. This one will strip HDCP from all inputs. This is important because we want to be able to record video! Some splitters will not strip this out and will act as a passthru, you want to avoid these if your goal is to be able to record the video from the consoles. The next step in the setup is running a cable from the splitter to the television and then into the video capture card in the PC.
This setup works out great. I can fire up either console and use the remote to change the TV to the right input. The streaming software will pickup the consoles or third pc monitor as expected too. Really nice having this all setup finally and not needing to swap cables. Previously I would have to change out the console cable straight into the splitter, and swap cables to get the third monitor option working.
Things not noted in the diagram are the cable box that also runs to the television as well as my camera for streaming, which is just a 1080 Logitech USB webcam.
As always, any comments or questions about the article, feel free to reach out to @Nicarras on Twitter!
This tutorial is a variation on a previous tutorial, the difference being using VB Cable and the tools located at their website. The theory is the same as the last tutorial, but I have been meaning to write up a new one since I switched to using these tools instead of VAC.
The advantages to me so far from VAC to VB Cable are ease of use as well as less issues. When using VAC I would run into instances where the extra audio cables would start performing badly or just crashing. I could also get random BSODs as well. I reached out to a few people and they said it had to do with how the timing of the audio channels interacted with the CPU timing. I didn’t dig that far into it. Just know that if you are having similar issues that I have had no issues whatsoever with VB Cables.
ed. I have an updated article for this setup as I’ve moved to VB Cables, check it out! http://nicarras.com/vb-cable-setup-streaming/
In this article I will show you how to use Virtual Audio Cables to solve a common problem when streaming to a site like Twitch. There are times where you may have multiple sound sources, and you only want certain ones to go to your stream. There also may be instances where you want certain sound streams merged together so that they can all hear each other. We will go over how to stream game audio to your stream, but not stream your Mumble/VOIP as well.
This is where the Virtual Audio Cables come into play. We will use them to separate the different sound sources. There is a handy program, VAC, that will install the Virtual Audio Cable drivers for you and the other tools required to set this up. For this example we will install two new VAC’s.
In this image you set the amount of cables you need in the top left, and that is really all the configuration we need to do here. From here now open the playback devices menu, you can quickly find this by right clicking on the volume icon in your systray.
In the first image you can see the two new lines that we installed. For this example I made Line 2 the default device. This means all apps will use this Line by default unless otherwise specified. This means things like web pages, music applications/streaming services, etc. I set my headset as the default communication device so Windows knows which device to use because I have multiples available in my system. I recommend setting all your settings explicitly, so you do not have to question where anything is sending its audio.
Now log into your game of choice, in this example I used World of Warcraft. Head to the sound settings and select Line 1. Now to setup Mumble.
Here we set Mumble to directly use my headset, by default Mumble is typically set to use the Default Windows device. Set this directly to the device you use for listening and recording. Now we setup our streaming app, in this case OBS. Note: To see these menus, you may need to check the advanced checkbox towards the bottom of the window if you have not already done so.
In OBS we configure the Audio to be streamed to just be what is playing over Line 1. We then set the recording device directly to what we are using. Now we are going to put this all together using the Audio Repeater software that is also installed when you install VAC.
This is what the Audio Repeater interface looks like. Launch the MME version not the Kernel version of the tool. This application is basically a bunch of software mixing boards. We are going to use multiple instances of this Audio Repeater app to accomplish what we want to put on our stream. Now this is where you start to have some freedom in how you want to configure this, let’s review some example configurations.
- Send only game audio to your stream. Mumble will go to your headset, but will not be transmitted to your stream. Also, other applications will go to your headphones, and not your stream.
- Send game audio, and other applications to your stream. Mumble will only go to your headset.
Let go over how you would setup the Audio Repeaters for these two examples.
1 – Audio Repeater: Wave In – Line 1, Wave Out – Headset/Speakers
1 – Audio Repeater: Wave In – Line 2, Wave Out – Headset/Speakers
This separates the audio into two distinct channels. Line 1 is configured to be picked up by OBS, and is now also setup to be sent to your headset/speakers. This allows your stream, and yourself to hear Line 1 (game audio). We already manually configured Mumble to be set directly to our headset/speakers. Line 2 will be other audio on your system, and it is now output to your headset/speakers.
1 – Audio Repeater: Wave In – Line 1, Wave Out – Headset/Speakers
1 – Audio Repeater: Wave In – Line 2, Wave Out – Line 1
This configuration shows how you can easily flip things if you want to stream the audio from a music app or a video, etc. These applications will all use Line 2 because we set it as the default device. We leverage this repeater to merge it with Line 1, and now our stream and we can hear it.
Microphone configuration. This really depends on the user. I’ve tried it two different ways. One, a push to talk for each application. One button to talk to stream, one button to talk to Mumble. You could also configure it so you PTT to send to Mumble, and regular talking over the Mic goes to your stream. That is really up to your preferences, and hopefully if you are reading this you know how to set that up how you prefer.
For Questions/Comments, message me on Twitter @Nicarras.