My TV Player and MyIPTV Player: what is actually different

MyIPTV Player is the app most Xbox owners found first, because for a long time it was the only one. It is a reasonable piece of software, and this article is not an attempt to tell you otherwise.

We built a different thing. The difference is not a feature list. It is one decision about where a playlist lives.

What both do#

Both read the playlist you supply. Both take M3U and XMLTV guide data, both play HLS and MPEG-TS, both run on Windows and Xbox, and neither supplies any channels. Its Store listing says so; our product documentation makes the same statement a non-negotiable rule that must appear on the website, the About screen and the store listing.

If your requirement is "play my M3U on an Xbox with a guide", both do that, and the simpler one is free to install.

The one real difference#

MyIPTV Player is a device application. Your playlist is configured on the device, and the same playlist on a second device is configured again there. Store licensing lets you install it on several devices signed in to one account, but that distributes the application, not the setup.

Ours is an account application. Sources, profiles, favorites, channel order and resume points live on the account, and a device reads them. The console's own sources screen describes itself as read-only, synced from the web console, because that is what it is. 13 kinds of account state travel that way, from favorites and watchlist to parental locks and multiview presets.

                        MyIPTV Player        My TV Player
playlist lives on       the device           the account
second device           configure again      already there
console sign-in         n/a                  pairing code + QR
favorites, resume       per device           synced
profiles and PIN        PIN protection       profiles, PIN, kid mode

Everything else worth comparing follows from that choice, in both directions.

What the account model buys#

No typing on a console. Sign-in is a pairing code and a QR: the console shows an 8 character code, polls every 3 to 30 seconds, and signs itself in when you enter that code on a device with a keyboard. You never enter a portal URL, a username or a password on a controller. If you have ever typed a 60 character URL with a thumbstick, this is the difference the whole design exists for.

One setup, every screen. Favourite a channel on a laptop and it is favourited on the console. Reorder your channel list once. Stop a film on one device and resume it on another. Watch-later entries are stored without reference to a source, so they survive changing provider entirely.

Profiles that mean something. Per-person continue-watching, per-profile guide and language settings, and parental controls: a PIN, kid profiles, bedtime windows and daily limits, enforced on the console and configured elsewhere. The PIN is hashed at 100,000 iterations with a random salt, never stored as text.

What the account model costs#

It is a service. A device application is not.

You sign in. There is an account. Configuration happens somewhere other than the device you are watching on, and if you only ever use one device, that indirection is overhead with no benefit. A single-console household with one playlist and no interest in profiles is better served by the simpler tool.

Where we have put the engineering#

Two areas, both invisible until something goes wrong.

Failure classification. We do not have one notion of "not working". Playback faults are classified into 9 kinds, each with its own verdict window before it is declared: 4 seconds for a network stall, 6 for a starved demuxer, and 4 each for a stalled picture or a total freeze. One of them can only be caught by looking at pixels, because a stream feeding black advances every counter normally. When rebuffering repeats, the player raises its own caching floor by 1000 milliseconds per verdict up to 5000 rather than asking you to find a setting. The buffering checklist covers what that looks like from the outside.

Multiview that counts. Six geometries from 2 to 9 tiles, and the layout reads your source's connection allowance before it assigns a tile rather than starting streams the portal will refuse. Ask for 9 tiles on a 2 connection line and the picker stops offering channels at 2, with a reason, instead of showing you 7 identical errors. Multiview has the detail.

Where we are behind#

On the console specifically, and worth saying before you switch.

Catch-up has no console page yet. HDR output and audio passthrough are not emitted on the console build, for reasons upstream of us that are still your problem if you own an HDR television. And 7 management destinations on the console are placeholder screens, which is a design decision and also, undeniably, a smaller app on that platform.

Then one that is not console-specific, included because a comparison listing only our advantages is not worth reading: our desktop memory profile is not where we want it. A 12 minute browse session ended at 918 MB against a 400 MB budget, and the growth was in native rather than managed memory. That is open work.

If any of those is the feature you came for, we do not have it there today. 4K and HDR on Xbox and catch-up on Xbox are the specifics.

Choosing#

One device, one playlist, no profiles, and you want the shortest path: the simpler application is a good answer and has been one for years.

Several devices, or several people, or you are tired of configuring the same playlist twice: that is the problem we built for.

Everything in this article about the other application comes from its Microsoft Store listing rather than from our testing, and I could not find a readable copy of that page in this session; what is here came from summaries of it. Check the listing yourself before deciding. It is the authority on what the other app does, not us.