Two ways to run a sphere, and how to choose
Synchronous means a PC or media server drives the screen in real time over a cable, always on. Asynchronous means a small player inside the base holds the content and plays it on a schedule, with nothing else switched on. Most spheres in malls, lobbies and stations run asynchronous, because nobody wants a Windows machine in a plant room that gets rebooted by the cleaner.
Synchronous still wins when the content is interactive, when several screens have to stay frame-locked to each other, or when someone changes the content daily and needs to see it on screen immediately.
The player carries the screen configuration
Worth being clear about, because it is where most of the confusion starts: the player does not need specially warped video. The sphere's geometry — the mapping, the cabinet arrangement, the rotation of each band — lives in the screen configuration, stored on the sending side or in the player itself depending on the hardware. Your content stays a normal flat file at the canvas resolution.
A 2 m sphere at P2.5 is roughly 800 000 pixels. A 1080p H.264 file at 12 to 16 Mbps is more than enough. We have been handed 80 Mbps 4:4:4 masters for a screen that cannot resolve the difference; they simply stutter on a player with a modest decoder, and the fault gets reported as a screen problem.
Schedules drift, and it is almost always the clock
A player without a time source will drift. Two seconds a day is ordinary. Over a season that is minutes, and the 09:00 opening becomes 09:07 — which is reported to us as 'the screen is late', never as a clock problem. Some players take time from the network, some from a phone app, some only from the PC that configured them. Pick one source, write it down, and check the clock at every service visit.
The second most common schedule fault is a gap in the playlist. If the schedule ends at 22:00 and nothing is assigned to the overnight window, the screen goes black, and at 10 pm on a Saturday that reads as a failure.
The three calls we actually get
The Wi-Fi password changed and nobody updated the player, so remote updates stopped. Someone switched the player off at the wall instead of using its shutdown, and the playlist came back empty. And the USB stick used for content was reformatted by a Windows machine that wanted to scan it, after which the player ignored the stick and the content 'vanished'.
All three are preventable with the same three habits: a fixed IP or a DHCP reservation, a labelled shutdown procedure taped inside the access panel, and content pushed over the network wherever the site has any network at all.
What to leave on site
One sheet of paper with the player's address, the login, the schedule logic, the canvas resolution and the name of whoever can push a new file. Plus a spare stick, already formatted, holding the current content.
We write that sheet for every install and laminate it inside the base. The calls that still come are almost always from a site where the sheet has gone missing, which tells you something about how much of support is really documentation.

