Reference

The reference describes the five resources and how their pods talk to each other:

• Players are the units of equipment, and Plays are the runs of media on them.
• Remotes are the controllers, and Keymaps map their buttons.
• MediaPreferences holds the cluster’s default languages.
• The media bus is the MQTT contract for everything that happens while media plays: reports, commands, button presses, and state.
• The media API captures what a Player shows and plays right now, as its screen, its sound, or both in one stream.
• Render node capabilities describes the media.liken.sh devices that state what each GPU can decode, encode, and scale.

Each resource page lists the resource’s fields, then its topics and payloads under “On the bus”. MediaPreferences has no topics: the operator reads its values into a Play’s pod when it creates the pod. The bus page gives the rules for the whole topic tree.

• Players
• Plays
• Remotes
• Keymaps
• MediaPreferences
• The media bus
• The media API
• Routes
• Render node capabilities
• Metrics