IRL Commons This site is new and not complete. Something wrong? Let us know

The initiative

Open initiative for shared formats and open data around IRL and hybrid streaming.

Why we need better standards and interoperability 

The apps and devices work. Using them together is the hard part.

  • Moving between devices

    With open tools, moving a live stream from one device to another without it starting over still means connecting things by hand.

    What already does part of this: OBS, TVU Go, cloud production, IRL+'s Video Mixer

    OBS can switch between a desk and a phone feed. TVU Go advertises moving from desktop to IRL. Cloud production can take several inputs on the bigger plans. IRL+'s Video Mixer (in closed beta) puts several cameras and a phone feed into one picture on a BELABOX box.

  • Few maintainers

    Much of this depends on a few people, often working in their free time. You can sponsor them, write clear bug reports or send fixes.

  • Anyone can reuse open source

    That is the idea of open source, and it is also a risk. Moblin uses the MIT licence: anyone may build its code into a closed, paid app. BELABOX's encoder and control screen use the GPL, and srtla uses the AGPL. Whoever ships a changed copy of those has to share its source with the people who get it. None of these licences makes anyone send their fixes back. The licence decides whether changed copies stay open.

  • Everyone can build their own now

    With AI coding tools, it keeps getting easier to build your own app, overlay or relay. That's good for trying ideas. But it also means more small tools that do nearly the same thing. Each has its own setup and its own words for what's happening.

  • Passwords

    Some setups need several logins. A hotspot's admin page may still have its default password. Local pages may show "Not secure" warnings because of self-signed certificates. Streamers are busy, and passwords leak on stream. In a collab, streamers put their stream key into another streamer's server and trust that nobody goes live on their channel by accident after the collab.

  • Online services get attacked

    Shared servers can fail. They also face attacks, floods of traffic and break-in attempts, more and more of them automated. When a shared service is down, everyone who uses it is affected.

  • Each project on its own

    Each project has its own community, with its own chat, docs and issue tracker. So advice on the same questions is spread across all of them: which modem, which SIM, why did my stream drop. Even names collide: How to IRL lists two unrelated projects called OpenIRL. If the projects shared a few standards and what they learn, each could keep its own focus. Streamers could then mix and swap apps and devices without starting over.

Three ideas 

  1. Start with the streamer's day

    Plan from what a streamer does during the day, not from the tech and its features. The stream should move with you between your devices without starting over, and without chat looking at a waiting screen. One show below shows how.

    The tech shouldn't be the stressful part. While you're live, you get a clear message. You also get a fix that says what it costs you, like a few seconds of your "be right back" screen. The explanation can wait until after the stream.

  2. Make apps and devices work as one

    Existing projects already do the hard parts: Moblin for the iPhone, CeraLive for a backpack, Moblink for spare phones. Build on them instead of starting over, and send fixes back to those projects first.

    Setup should be secure without passwords to remember. For example, you pair a phone with a tap and a matching code.

  3. Shared standards

    Open, written standards for how apps and devices work together. For example: how a phone and a backpack pair, what "live", "be right back" and "private" mean, and how a stream moves from one device to the next.

    Any app, backpack or service can follow them. Then trying a new one is a small risk, and the people who make each part can build a business on it. The first drafts are on Open standards.

One show on any device 

Start at your desk or on your phone. When the backpack has started, the stream moves onto it without dropping. Your phone stays in the show as a camera, an extra connection and your remote. When you are home again, your PC takes the stream back the same way.

One show, carried by three devices in turn Time runs left to right. The top line is what viewers get: one unbroken stream. Below, the PC carries it first, then the phone, then the backpack, and at the end the PC again. Where two rows overlap, both devices send for a moment before the switch, marked 1, 2 and 3. After the second switch the phone keeps helping as a camera, a link and a remote. Viewers PC Phone Backpack 1 2 3
  1. 1 Desk to phone, for the walk out.
  2. 2 Phone to backpack, once it has started. The phone keeps helping.
  3. 3 Home again: back to the PC.

PC Phone Backpack

Viewers see one short transition at each switch.

Why apps need to share their status 

Each app and service reports only its own part. When a setup uses apps from different makers, none of them sees the whole chain.

One setup today

  1. Phone app:"Live".sending to your relay
  2. Relay:receiving.nothing to pass it to yet
  3. Cloud OBS:no answer yet.still starting
  4. Twitch:offline.no stream coming in

In this example, Moblin sends your picture to a relay. A relay is a service that receives your stream and passes it on. Then OBS on a cloud computer turns it into the show for Twitch and YouTube. You start the stream in Moblin, and it shows you're live. That's true: your phone is streaming to your relay. But the cloud OBS hasn't finished starting, so nothing reaches Twitch yet. Or OBS is running and taking your feed, but it still shows your starting scene. Or Twitch is fine, but the second feed to YouTube has stopped and you didn't notice.

Each app is right about its own part. Moblin can also connect to OBS's remote control and show OBS's scene and whether OBS is streaming. But it can't see every place OBS sends to, or a relay it doesn't run. So to find out what viewers actually get, the streamer may have to check several places. To do that, they have to understand the whole setup.

A full picture in one place

If each app reported what it's doing in the same words, your phone could collect those reports. It could then show you the real status, including where the stream stops.

Before the show reaches Twitch.
When only one destination is receiving.

Why it matters

This may be why many people buy a ready-made kit from one company. That company makes every part, so one screen can show you how it's going. Separate tools might each do their own job better. If open apps and devices used the same words for what's happening, they could have that one screen too.

What a streamer might want to see 

In both, the stream is still live on the platform.

In a tunnel, the phone says what viewers get, what was already done, and one fix with its cost.
With the privacy screen on, it says what viewers see instead of you.