Home
XtreamUIPro

Setup guide

Museums & Cultural Centres setup guide

Configure the platform as the video service of a museum or cultural centre: gallery screens on the local network, a members' library, activation codes sold at the desk, and live openings.

These guides map an industry's concepts onto the objects the platform has today (bouquets, lines, packages, partner accounts, nodes, the API). They are conceptual mappings, not industry-specific features, and a partner account is a delegated account, not an isolated tenant.

Conceptual mapping

Nothing in the panel is called a gallery or a member. The table says which object plays which role; the chapters below set them up in that order.

In your industryOn the platformWhere in the panel
Exhibition film and archiveVOD catalogue: movies and series with seasons and episodes, categories and metadataMovies and Series, or the VOD ingest job
Opening or lecture broadcastLive channel: a stream with its sources, EPG and output formatsStreams → add a live stream (source URL or RTMP push)
Gallery or members' collectionBouquet: a named set of channels, films or series that a package grantsBouquets, from Streams and Movies / Series
Visitor or member accessLine: one access with its package, bouquets, expiry, connection limit and outputsLines → add, or activation codes, or the Reseller API
Membership periodExpiry date of the line, renewed by a package, a credit or the APIThe line's expiry date and the package's duration
Devices per memberMax connections of the line: how many devices may watch at onceThe line's max connections

Prerequisites

What to have before installing.

  1. A server in the building (Ubuntu 22.04 or 24.04), the installer, and the gallery network that the screens and the members' devices will use.
  2. The exhibition film, the archive recordings you hold the rights to, an encoder for the lecture hall, and the screens or media players for the galleries.
  3. The licence key and, if the building has no internet, the offline activation procedure; and a decision on who at the desk sells memberships.

Infrastructure deployment

The server in the building, activated on site.

  1. Run the installer on the server and set the playback base URL to the address the gallery network reaches.
  2. Activate the licence key offline from the panel; after activation the service runs on the local network without the internet.
  3. Add the exhibition film under Movies and the lecture-hall feed under Streams, and check them in the web player.
  4. For a second site or a large public programme, enrol a node from Servers; the panel installs it over SSH and routes that site's viewers to it.

Content organisation

Galleries, archive and members' collections.

  1. Create categories per exhibition and per year, and a series for a lecture cycle with one episode per talk.
  2. Create one bouquet for the gallery screens and one for the members' library of talks and archive film.
  3. Create a package for the galleries and one per kind of membership, each granting its bouquets; the membership package's duration is the membership period.
  4. Add posters and short descriptions to every movie so the library reads well in the player.

Partner (reseller) configuration

The desk and the shop as delegated accounts.

  1. Create a group with permissions limited to lines and activation codes, and no access to the catalogue or the servers.
  2. Add the desk, or the shop, as a reseller with that group, the membership packages and a credit balance.
  3. A cultural centre that runs several venues can add a reseller per venue, each selling memberships from its own balance.

Visitor and member access configuration

Screens and members on lines.

  1. Create one line per gallery screen under Lines → add with the gallery package, and bind it to the screen's address when the network gives fixed addresses.
  2. Create activation codes at the desk for each membership sold; the member enters the code in the player and the line starts.
  3. Set max connections per membership to the number of devices a member may use, typically two.
  4. Hand the member the player app, an M3U playlist or the web player address, whichever fits their device.

Exhibition film and archive

The library on demand.

  1. Upload the exhibition film and the digitised archive as movies, or ingest them with the VOD ingest job into the media root.
  2. Add TMDB metadata where it exists, and write the title and description yourself for the rest.
  3. Keep the archive that is not for the public in the members' bouquet only, and check what each package sees with a test line.

Openings and lectures

An event as a live channel.

  1. Add a live stream for the lecture hall's encoder (RTMP push) and place it in the members' bouquet, or in the gallery bouquet for an opening shown on the screens.
  2. Enable catch-up so a member who arrives late can rewind, and upload the recording to the library afterwards.
  3. Test the encoder and the stream before the event with a test line, on the same network the audience will use.

Membership expiry and renewal

The membership as the line's validity.

  1. A line expires at the end of its package's period; a renewal at the desk adds another period.
  2. Disable a line when a membership is cancelled; activation codes that were never used stay unused until they are redeemed.
  3. Subscribe the shop or the membership system to the webhooks to see lines that are about to expire or already expired.

Integration with the shop or membership system

Systems sell the access; the player plays.

  1. Create a Reseller API key for the shop or the membership system; it calls create_line, renew_line and disable_line, with a request id on each write.
  2. Use a commerce connector when memberships are sold online; any other system uses the Reseller API and webhooks.
  3. There is no single sign-on for viewers: a member signs in to the player with the line's credentials or the activation code.

Security considerations

Keep the collections where they belong.

  1. Keep the gallery network separate from the visitors' network, and serve any public access behind a reverse proxy with TLS and TRUSTED_PROXIES set.
  2. Two-factor sign-in for every panel account; the desk gets a permission group limited to lines and codes.
  3. Signed and expiring playback links, a connection limit per membership, and address binding for the gallery screens.
  4. Enable the encrypted database backup with an off-site copy, and use the audit log to review changes of lines and catalogue.

Troubleshooting

The usual first checks.

  1. A gallery screen is black: check that its line is enabled and not expired, the screen's address binding, and that the server is reachable on the gallery network.
  2. A member's code does not work: check that the code was not redeemed already and that the package it opens is still assigned to the desk.
  3. Licence activation fails offline: check the activation file against the licence key and the clock of the server.
  4. The live opening stutters: check the encoder's bitrate against the uplink and the stream's status under Streams.