Work out why a video will not play

Start with the failure you can observe

Note what happens before changing settings: does the video never start, play sound without a picture, stop at a repeatable point, buffer intermittently or fail only when cast? Also note whether one title, one source or everything is affected.

These observations help narrow the problem. They do not establish a cause by themselves. A spinning indicator is not proof of a slow internet connection, and a working poster is not proof of a working stream.

Run a small controlled comparison

1. Confirm the intended title and, for a series, the exact episode. Check that your profile is allowed to play it.
2. Read the player's error. The Odyssey player can show Stream unavailable and Choose Another Source.
3. If offered, choose another authorised source for the same title. Record whether that version starts.
4. Try one other title from the original source. Avoid opening many parallel streams while testing.
5. Check Settings → Sources → Provider Health for a source failure or stale successful refresh.
6. If the fault occurs while casting, test playback locally on the sender before repeating the receiver connection.

Keep the tests comparable. Changing source, audio track, network and device simultaneously may make playback work while leaving the real cause unknown.

Use the result to choose the next check

One file fails but another title from that source plays: investigate the affected file, edition, stream URL or its compatibility. A service-wide outage becomes less likely, but is not ruled out entirely.

All titles from one source fail: check the source's connection, account access and current service availability. If you also manage the media server, check that it can serve a known authorised file from its own interface.

Local playback works but casting fails: receiver format support, preparation and network reachability become the next checks. Casting may rely on Odyssey staying open.

Multi-View fails while one channel works: reduce the layout and check the provider's simultaneous-stream allowance and device resource messages.

Investigate interruptions without assuming a fix

Compare whether interruptions happen at the same timestamp or at varying moments. A repeatable failure can point towards a particular part of a file or stream; irregular interruptions can involve network or service delivery. Neither observation is a diagnosis on its own.

Try a stable permitted network connection and stop unnecessary simultaneous streams. Reopen the same title and observe it long enough to compare with the original symptom. Do not describe a one-minute successful test as proof that a long-running fault is fixed.

Hide Progress Bar in Playback settings only hides the loading presentation. It does not change how the stream loads, so it is not a buffering remedy.

A source-specific failure

A film fails immediately with Stream unavailable. A second film from the same server plays, and an alternative authorised version of the first film also plays. Record the failing edition, the error and the fact that the other two tests worked.

That is much more useful than “nothing works”. It supports investigation of the original file or playback route while leaving the actual cause open. Keep the original configuration intact until you know which change is needed.

Gather evidence safely

Settings → Advanced → Open Diagnostics exposes diagnostic information. Provider Health also offers Export Support Summary; iPhone, iPad and Mac can provide Copy Source Summary. These tools are subject to applicable settings protection.

Remote diagnostics are a separate opt-in setting, Share remote diagnostics. You can still describe a problem without turning it on. Before sending screenshots or copied text, review it and remove management codes, passwords, access tokens and complete private stream addresses.

When to contact support

Contact support when the error persists after a small, documented comparison, or when the same valid source behaves differently in a repeatable way across devices. Include app version, device, operating system, time, source type and the exact steps.

Should I reinstall first? Usually preserve the evidence and account context first. A reinstall is not a diagnosis and can add setup work.

Has this guide fixed performance? It provides checks. Only a successful repeat test of the affected workflow can support a claim that your particular issue has improved.