Bring multiple media sources into Odyssey

One player, separate connections

A home library and a television service solve different needs. Odyssey can bring supported connections into one app without replacing the services behind them. Each connection still needs a working address, appropriate credentials and permission to its content.

For example, connect Jellyfin for your own films and an authorised Xtream service for Live TV. Check a known film and a currently available channel separately. A successful catalogue refresh is not proof that a particular stream is playable.

Choose the connection that matches the service

Xtream uses its provider connection details. An M3U source uses a playlist address. Plex connects a personal library. Jellyfin, Emby and Silo have service-specific requirements; Silo uses its Jellyfin-compatible connection.

The website groups Jellyfin, Emby and Silo under Media server. The native app has individual choices. The media-server guide explains the exact fields and why the web and native sign-in flows differ.

Profiles control what appears

A source can be connected to a managed setup while remaining unavailable to a particular profile. Check the intended profile before treating missing content as a failed connection. Protected changes may require the appropriate owner approval.

Odyssey is intended for adults aged 18 and over. Profile controls organise access within that intended use; they do not grant rights to another person’s library or remove a provider restriction.

Check each feature separately

Ordinary playback support is not the same as support for Channel Studio. In the documented build, Channel Studio accepts compatible Plex, Jellyfin and Emby libraries, with Silo through compatibility mode. Xtream playback does not make Xtream a Channel Studio preparation source.

Home DVR is another service-dependent workflow. It requires a connected recording service and applicable permissions. A source appearing in search does not establish that it can be recorded or shared.

Keep source changes deliberate

Give connections recognisable names and test one before adding several more. When replacing a source, saved Channel Studio bindings may still refer to its previous identity. Use the reconnection guide before rebuilding channels.

A management code connects devices to a managed setup, but do not assume every device preference or every provider credential automatically syncs. See what management-code sync covers, and confirm reachability from each device.

Common questions

Does connecting a source merge my subscriptions?

No. Your services keep their own access rules, credentials and subscriptions.

Will every connected source work with every feature?

No. Playback, Channel Studio, recording and sharing each have their own compatibility and permission requirements.