A setup that survives updates

The thing that ends most Linux streaming setups is not a missing feature. It is an update on a Tuesday that changes something small, discovered at 19:55 on a Wednesday.

Everything in this chapter is about making that impossible rather than unlikely.

Choose a distribution for boredom

For a machine you go live on, the useful property is not being current. It is being predictable.

• A stable release — Fedora, Ubuntu LTS, Debian, or any of the steady ones — changes on a schedule you can see coming. This is the right default for a streaming machine.
• A rolling release — Arch and its relatives — gives you the newest PipeWire, driver and OBS, which occasionally matters for very new hardware. It also means a kernel or driver update can land the afternoon of your stream.

Rolling is completely viable if, and only if, you follow the rule below.

Never update on stream day

This is the whole chapter in one line, and it costs nothing.

Pick a day that is not a stream day, update then, and reboot and test before you close the laptop. If an update breaks something, you now have days to fix it instead of forty minutes and rising panic.

The corollary: do not install "one quick thing" an hour before going live. Every streamer learns this once, usually publicly.

Back up the four things that matter

None of these are large, and all of them take real time to rebuild:

• Your OBS scene collections and profiles. Export them from OBS itself — Scene Collection → Export, Profile → Export — and keep the files somewhere that is not this machine.
• Your audio routing. Your Crossfade configuration, or your saved patchbay, or at minimum the paragraph you wrote describing how sound gets from each application to each destination.
• Your plugin list. A text file naming which plugins you use, and which packaging route they came from. Rebuilding from memory is where the evening goes.
• Your fonts and overlay assets, if your scenes reference local files.

Do this once now, then again whenever you change something meaningfully. A scene collection export is a few kilobytes and has saved more streams than any other item in this path.

The five-minute pre-stream check

Run this after any update, and ideally before every stream:

1. Open OBS and look at the preview. Every source live, nothing black.
2. Speak, and watch the meters — microphone present, at the right level.
3. Play a second of music and confirm it is in your headphones and not on the stream mix.
4. Start a ten-second local recording, stop it, and open the file. Picture and sound, all tracks.
5. Glance at the OBS statistics once you are live: no dropped frames, no encode lag.

That sequence catches essentially everything that a Linux update can quietly change, in less time than it takes to pick a title.

When it breaks mid-stream

It will happen once. Have a plan rather than an improvisation:

• Have a break scene on a hotkey, with a still frame and a muted microphone. Switch to it first, fix second.
• Know your restart order. Restarting the audio server is one command; restarting OBS is quick; restarting the session is not. Try them in that order.
• Keep a phone or second device with your channel open, so you can tell people what is happening from outside the broken machine.
• Then end early if you need to. "Something's broken, I'll sort it and be back Thursday" is a completely normal stream ending, and pushing through a broken setup produces an hour nobody enjoys.

The honest summary of this path

Linux streaming asks for one weekend of setup and a small ongoing discipline about updates. In exchange you get an audio stack nobody else has, a machine that does not interrupt you, and full visibility into what your system is actually doing.

If you got here and you are running it: you now know more about how your own stream works than most people ever will, which is worth something on the day something goes wrong.

That is the end of this path. If a chapter here was wrong, outdated, or thin — this is fast-moving ground — say so in the Discord. The date at the top of each chapter is a promise that somebody is still reading them.