My Twitch Live Coding Setup. This article is an updated review of… | by Suz Hinton | Medium


My ideal setup would use one of those ultra-Wide monitors so that I have more room in the non-capture zone, but this is fine for now. A girl can dream, and maybe even budget for a new monitor soon.

I’m going to list the important video and output settings that I have found success with below.

Video settings

  • Base (Canvas) Resolution: 2560x1440
  • Output (Scaled) Resolution: 1280x720
  • Downscale Filter: Bicubic (16 samples)
  • Common FPS Values: 30

Output settings

  • Encoder: x264 (but checked ‘enforce streaming service encoder settings’)
  • Do not rescale output
  • Rate Control: CBR (Twitch performs better with consistent vs. variable)
  • Bitrate: 2000
  • Keyframe interval: 0
  • CPU usage: veryfast
  • Profile: main
  • Tune: (none)

So why the low output resolution and bitrate, I hear you ask? The answer is very blunt — your stream is not about you, it’s about your viewers. Some of your viewers do not have blazing fast, modern internet connections to watch you in crisp high resolution. I was born and raised in Australia, so I am painfully aware of this and remember waiting 20 minutes just to finish pushing code to a remote SVN service. As long as they can read your code on your video feed, you’re good. Keep things as low as possible in order to prevent buffering delays and intermittent dropped frames on your side as well. Your viewers will thank you by sticking around and returning each stream.


This one is going to get complicated. I am streaming on macOS, which introduces some snags when working with audio sources in OBS. If you use Windows to stream — feel free to disregard this entire section.

The TLDR is: if you want music and other desktop sounds to play on your stream, use Soundflower for a really pared back solution to get started with. Soundflower will allow you to use a virtual device to route your desktop sounds to. OBS can then use the Soundflower device as an audio source.

I personally have a more comprehensive setup, where I route audio to several virtual devices in order to use OBS as an audio mixer for my needs. It is entirely optional, please do not feel that this is at all necessary.

I use Loopback, which is an audio routing tool that uses software only to help you move audio through virtual devices from various sources. I use two virtual devices in Loopback; one for my music (iTunes), and another for the sound effects I sometimes play on my stream.

The music related device pipes the music playing from iTunes into a virtual device I call ‘Twitch Music’. Here is a screengrab of what it looks like in Loopback:

The sound effect related device captures sounds from my Chrome browser windows (Streamlabs alert sounds are the main thing I’m trying to capture) and is also a simple ‘pass-thru’ — it’ll accept any input audio you give to it. I cover how I play my sound effects via this pass-thru in the automation section of this post later on. However, here is a screengrab of what it looks like in Loopback:

In OBS I set up an audio source for each of these virtual devices, including Soundflower. Soundflower is capturing the remaining sound that isn’t music or a sound effect (such as error sounds from my computer programs, etc).

Here is a screengrab of the audio settings in OBS:

Setting up these sources separately allows me to control each one individually, just like a mixer in real life. I can individually adjust the volume of my mic, music, sound effects, and misc. desktop sounds at will, which is really handy to have as a feature when streaming.

Here’s the mixer interface in OBS to show you what I mean:

Last but not least — all of this does not help me to also hear what I need to hear while streaming. I do not want to hear the music, but I do want to hear computer error sounds, and also Streamlabs follow and subscription alerts which help me to notice them and call them out. This is where I use the Audio MIDI Setup application (built into macOS) to solve this problem. I create a multi-output device, and check the boxes to include the audio sources I do want to hear. Just before I stream, I switch to this multi-output device as the output source for my laptop’s audio. This routes the helpful sounds to me, and filters out the sounds I do not want. I call this device ‘Twitch Personal’ so that I remember it’s for my own local use.

If you want to conduct remote video calls with fellow programmers to “pair” with them on your stream, you will absolutely need to do this, or you won’t be able to hear them speaking (only your viewers will hear them).

Here’s what my multi-output device looks like:


I randomly source royalty free, creative commons licensed music from sites such as Free Music Archive and Bandcamp. There are services out there like Pretzel Rocks, but I want a specific music type for my channel that other streaming music resources don’t offer.

I use iTunes to play the music on stream because it supports AppleScript, and I have written scripts that automate the music and the song identification.