Dark Souls 3 Gameplay No Commentary Solo Run

Recording a Clean Dark Souls 3 Solo Run Without Narration

Most people overcomplicate this. You don't need expensive gear or a studio setup. You just need OBS, a clean capture, and a way to suppress audio clutter. Here is how I do it, what goes wrong, and how to fix it without losing your mind. I film my runs at 1080p60 using OBS Studio on a Windows machine. The game outputs audio through my speakers and mic simultaneously, which creates a mess if you are not careful. The trick is to route your desktop audio as a separate track in OBS and then mute the microphone channel entirely before you even start recording. If you skip that step, you end up with the game sounds bleeding into whatever your mic picks up, and fixing it in post is a waste of time.

Dark Souls 3 Gameplay No Commentary Solo Run

The basic workflow starts with getting the game to run in a dedicated window. I use borderless windowed mode at native resolution, then capture only that window in OBS rather than capturing the whole screen. This keeps the file size smaller and makes it easier to frame the shot. Add a scene with just the game feed, a single audio source set to desktop output, and you are already ahead of most beginners. One thing I learned the hard way: Dark Souls 3 does not respect Windows volume normalization. When you pull aggro from multiple enemies and the combat music spikes, your recorded audio levels jump instantly. I used to miss entire boss dialogue cuts because the waveform peaked and clipped. The workaround is to add a compressor filter in OBS on the audio track and set the threshold around -12 dB with a ratio of 4:1. That evens out the spikes without sounding processed. Test it first with a challenging fight like Slave Knight Gael before committing to a full run. File management matters more than people admit. A single full solo run through Dark Souls 3 without cuts runs roughly 6 to 8 hours at 1080p60, which translates to about 40 to 70 gigabytes of raw footage depending on your bitrate settings. I recommend starting at 25000 kbps for the encoder and using the x264 slow preset if your CPU can handle it. The encoding takes longer, but the compression artifacts disappear during fast camera swings and particle-heavy fights, which happen constantly in the later areas.

Another counter-intuitive detail most guides miss: the game saves automatically when you sit at a bonfire, and those transitions sometimes trigger a frame hitch on certain hardware configurations. If you are capturing directly and your bitrate is already maxed out, that hitch can cause a dropped frame or two right when you need it most. I solved this by disabling hardware acceleration in the game settings and using a dedicated GPU for encoding while the game runs on the primary card. It cuts frame drops during those moments to nearly zero. Audio mixing in post is where most people mess up. The game itself mixes music, sound effects, and ambient noise at fixed relative levels, but streaming services often normalize audio differently. When I upload a run, I run it through a loudness normalizer set to -14 LUFS, which is standard for YouTube. That brings everything into a consistent range without making the quiet exploration sections in areas like Lothric Castle unhearable. If you skip this step, viewers will click off during the calmer moments because the mix feels uneven. There are real limitations to this approach. Running OBS alongside the game on the same GPU introduces minor input latency, which matters if you are doing anything skill-testing or speedrun-related. For a casual solo run, it is negligible, but I have noticed a half-second delay in dodge timing when the GPU load crosses 85 percent during heavy areas like Archdragon Peak. If you notice your character reacting slower than usual, drop the OBS encoding preset one notch or increase the game’s frame limit slightly to give the GPU headroom.

For tools, OBS is free and covers everything needed. If you prefer something simpler, Streamlabs Desktop works the same way but adds more overhead. Avoid any third-party audio enhancers or noise gate plugins unless you know exactly what they do. They tend to introduce artifacts that sound fine at first but become obvious on repeat listens. Keep it clean, keep it simple, and let the game sound do the work. The final edit should strip nothing essential. Some people cut out bonfire rests and traversal to shorten the video, but that changes the pacing in a way that defeats the purpose of a no commentary run. The point is to let the atmosphere breathe. If a segment drags, trim the edges, not the middle. A well-structured full run sits comfortably between 4 and 6 hours when edited properly, depending on how many attempts you include for tough bosses like Soul of Cinder or Pontiff Sulyvhan. I once spent three hours debugging why my recorded audio had a faint hum underneath the game soundtrack. Turns out it was a ground loop from my audio interface, not OBS at all. Swapped the USB cable and the issue disappeared. Worth mentioning because troubleshooting audio problems eats more time than the actual recording process if you are not careful.