One OBS signal, several streaming targets
Aitum Multistream adds extra outputs to OBS. That lets you feed, for example, Twitch, YouTube, and your own RTMP server from one OBS instance.
Mobile IRL stream → Relay / OBS → Main output
├→ Twitch
├→ YouTube
└→ TikTok / own RTMP targetContents
1. Direct multistreaming or a relay service?
Aitum Multistream sends each configured output directly from the OBS PC. That saves an external distribution service, but it needs enough local upload and, depending on your settings, extra encoder power. A relay or restreamer server, on the other hand, can take a single OBS uplink and distribute it on the server side. How to build such a server is in the restreamer guide. Bitrate & quality in an IRL stream explains what bitrate and quality mean.
| Option | Upside | Keep in mind |
|---|---|---|
| Aitum direct | full control in OBS | bitrates add up in the upload |
| Relay/restreamer | only one uplink from OBS | maintain the server and forwarding |
| Platform service | simple distribution | cost, account linking, privacy |
2. Installing Aitum Multistream
- Close OBS and back up your scene collection and profile.
- Open the official Aitum Multistream page.
- Download the current package for Windows, macOS, or Linux and install it.
- Start OBS and show the Multistream/Output dock through Docks.
- With a current OBS 32 version, check that the plugin loaded without errors.
More official project pages: Aitum Multistream on the OBS forum and GitHub releases and source code.
3. Calculating upload and encoder load
With separate direct outputs, video, audio, and protocol data all add up. Two streams at 6 Mbit/s each need more than just 12 Mbit/s: you also need headroom for audio and fluctuation. Plan at least 20 percent headroom, and more for production use.
Example:
Twitch 6.0 Mbit/s
YouTube 8.0 Mbit/s
Audio/overhead/headroom
Stable upload needed: well over 14 Mbit/sAdd up the bitrates of all direct outputs. On top of that come audio, protocol overhead, and headroom. It's best to measure your upload at the time of day you'll be streaming.
If all targets use the same resolution, codec, and bitrate, one encoder can be shared, depending on your Aitum/OBS configuration. Different formats or bitrates can need additional hardware encoder sessions.
4. Setting up streaming targets safely
- In the Aitum output dock, add a new target.
- Choose a predefined service or enter the platform's official RTMP/RTMPS address.
- Copy your personal stream key straight from the live dashboard.
- Set encoder, resolution, FPS, bitrate, audio, and keyframe interval to match the platform.
- Give the target a clear name and test it on its own first.
- Only after successful individual tests, start several outputs together.
5. Combining Aitum Multistream with Vertical
The normal 16:9 canvas can feed Twitch or YouTube, for example, while a 9:16 canvas is used for TikTok or a vertical YouTube output. Scenes, overlays, and audio have to be checked separately for each format.
6. Testing, monitoring, and troubleshooting
- Check each target on its own with a private or unlisted test.
- In the OBS stats, check for frames skipped due to rendering or encoding.
- Watch network drops and your actual upload.
- Test all targets together for at least 20 minutes.
- Check audio, scene changes, and the end of the stream separately on each platform.
If a target doesn't start, check the server address, stream key, and platform authorization first. If it stutters, reduce the total bitrate or move distribution to a relay/restreamer server. How to monitor the whole chain while you're out is covered in Checking your stream on the go. If a target drops out, the emergency plan helps. The Aitum Help Centre offers help too.
Quick checklist before going live
- You measured your upload and planned the total bitrate with headroom.
- Each target is tested on its own, and the stream key is visible nowhere.
- You checked the skipped frames in the OBS stats.
- You know the fallback route through a relay/restreamer server in case it stutters.
7. Common questions about Aitum Multistream
Does Aitum Multistream stabilize my cellular connection?
No. The plugin distributes the finished signal from the OBS PC to several targets. The path from the IRL streamer to the relay or to OBS doesn't get any better. That's what bonding and a suitable relay path are for, see SRTLA & Bonding.
How much upload do I need for two targets?
The bitrates of the direct outputs add up. In this page's example that's 6.0 and 8.0 Mbit/s, 14 Mbit/s together. On top of that come audio, overhead, and headroom. Plan at least 20 percent buffer and test with your real connection.
Direct with Aitum or through a relay/restreamer server?
Direct means full control in OBS. In return, you load the upload and, depending on your settings, the encoder several times over. A server only needs one uplink from OBS, but it needs maintenance. A platform service is simple, but brings cost, account linking, and privacy questions.
Can I share one encoder across all targets?
Depending on your Aitum and OBS configuration, that's possible if resolution, codec, and bitrate are the same for all targets. Different formats or bitrates can need additional hardware encoder sessions. Check the OBS stats to see how heavily the PC is loaded.
What if a target doesn't start?
First check the server address, stream key, and platform authorization. Start the target on its own before you run several outputs together. If it stutters, lower the total bitrate or move the distribution to a relay/restreamer server.
Privacy and platform accounts
The Aitum websites and downloads are external offerings and are not embedded on IRL4YOU. When you use the plugin, stream data and credentials are sent to the platforms or RTMP targets you choose yourself. Their privacy terms and your OBS/Aitum configuration apply.
Thanks to the Aitum team
Thanks to the developers and contributors for Aitum Multistream and the publicly accessible project resources. This IRL4YOU page is an independent practical guide and not official Aitum documentation.