Using an Xbox Media Remote with My TV Player
A media remote reaches most of the app and cannot reach all of it. The gap is the two triggers, and on a large catalogue that is the gap you will feel.
A media remote is a better living-room input than a controller for most of what this app does. It is smaller, it holds a charge for months rather than for 2 or 3 days, it has a D-pad that a thumb finds without looking, and nobody has to move a controller off the sofa to sit down.
It also cannot reach everything. This article says which parts.
How the console app sees a remote
It does not, particularly. The app handles gamepad virtual keys, and the console presents a media remote's navigation and action buttons as those same keys. A D-pad press is a D-pad press whether it came from a thumbstick, a controller D-pad or a remote, which is why there is no separate remote mode and no pairing step inside the app. Pair the remote to the console the normal way and it works.
The mapping that follows from this:
Remote App action
-----------------------------------------------
D-pad Move focus
OK / Select A: watch, open, resume
Back B: back, or app navigation
Menu Menu: options, or re-sort
View View: categories, all groups, refresh
That covers 4 of the 6 action buttons the app uses, plus all 4 directions. Most of the app lives there.
What a remote cannot reach
Three things, and one of them matters.
The trivial one is X and Y. A media remote has no X or Y key, so 2 actions lose their direct binding: the favorite toggle and global search. Search is still reachable through app navigation, and favorites can be managed from any other device on the account, so this is an inconvenience rather than a wall.
The second is the shoulder buttons. Volume, mute and channel up and down sit on the bumpers on the console, and a remote's own volume keys do not replace them.
The one that matters is the triggers. Letter jump is bound to LT and RT, seeking within a stream is bound to them too, and a remote has no triggers at all. On a playlist of 50 channels you will never notice. On a real catalogue you will notice immediately, because the numbers are not close: crossing a 373 row category list with a paging button takes 42 presses, and walking every initial of the same list with the triggers takes 20. In a 4,000 title grid the gap is wider still.
So the pattern that works is the remote for watching and the controller for the occasional expedition into a large catalogue. Most evenings are watching.
Reading the bar with a remote in your hand
The hint bar names buttons by their controller glyph, including LB/RB and LT/RT. That turns out to be useful rather than confusing when you are holding a remote: anything the bar advertises as LT/RT is a thing your remote cannot do, and anything it advertises as A, B, Menu or View is a thing it can.
One more consequence. I went looking for a system media transport controls handler in the app, because a remote's dedicated play, pause and stop keys ought to go somewhere, and I could not find one: the app registers none, so those keys are not separately interpreted. Transport control on the console runs through the on-screen transport layer, reached with A. If your remote's play key does nothing in the app, that is why, and A on the transport layer is the equivalent.
When the remote is the right choice
For a household where the console is mainly a TV, a remote is the better default input, and the reason is not really about buttons. A controller signals "someone is playing" and a remote signals "someone is watching", and the second is what you want the box under the TV to be.
Set the app up so the expeditions are rare and the remote is enough. Favorites do most of that work, and they sync, so an evening spent favouriting channels in the Windows app pays off on every console session afterwards. Custom groups do the rest. Both are managed from the web console or the Windows app rather than on the console itself, which is the same split that applies to sources and profiles.
For the full button map, including everything a controller adds, driving My TV Player with an Xbox controller goes screen by screen.
What this article measured22 claims, each with the evidence behind it
| Claim | Evidence | Counted |
|---|---|---|
| The console app handles input as gamepad virtual keys. Any device the console presents as those keys drives the app identically; the app does not know which physical accessory sent them. | n = 1 | Aug 31, 2026 |
| The app registers no system media transport controls handler, so a remote's dedicated play, pause and stop keys are not separately interpreted by the app. | n = 1 | Aug 31, 2026 |
| Letter jump is bound to the left and right triggers, which a media remote does not have. It is advertised only on alphabetically sorted surfaces. | n = 1 | Aug 31, 2026 |
| Without letter jump, crossing a 373 row category list takes 42 presses of a paging button, against 20 trigger presses to walk every initial in the same list. | n = 1 | Aug 31, 2026 |
| The console has no pointer and hover affordances are disabled, so every control is reached by directional focus. That is what makes a remote's directional pad a complete input for navigation. | n = 1 | Sep 1, 2026 |
| The controller map is the same on both heads, shared through one bindings helper in the core, so what a remote can reach is decided by the map rather than by the platform. | n = 1 | Sep 1, 2026 |
| Volume and mute sit on the shoulder buttons on the console rather than on arrow keys, and channel up and down do too, which a remote's own volume keys do not replace. | n = 2 | Sep 1, 2026 |
| Seeking within a stream is bound to the triggers on the console, which is a second thing a remote without triggers cannot reach directly. | n = 1 | Sep 1, 2026 |
| Back and confirm map to the two face buttons a remote does have, so the two most common actions are always reachable. | n = 2 | Sep 1, 2026 |
| Switching profile is reached through the Menu button rather than a chord, so it stays available on a device with fewer buttons. | n = 1 | Sep 1, 2026 |
| The hint bar is a specified 72 effective-pixel component using canonical button colours, present on every screen, which is what makes it a reliable guide to what your device can reach. | n = 1 | Sep 1, 2026 |
| Favorites and custom groups are account state that syncs, so the browsing a remote is bad at can be done once on another device. | n = 2 | Sep 1, 2026 |
| Manual channel order syncs as well, so the handful of channels a household actually watches can be pinned to the top from a machine with a keyboard. | n = 1 | Aug 16, 2026 |
| A production source in our sample carried roughly 77,842 titles across about 444 categories, which is why traversal cost matters at all on a device with fewer buttons. | n = 1 | Sep 1, 2026 |
| The letter-jump hint appears only where a list is actually alphabetical, so the bar never promises a jump that the ordering could not honour. | n = 1 | Sep 1, 2026 |
| Search offers type filters beside its on-screen keyboard specifically as a browse fallback for someone who does not want to type, which suits a remote. | n = 1 | Sep 1, 2026 |
| The console is a single full-screen view with no second window, so a remote never has to move focus between windows. | n = 1 | Sep 1, 2026 |
| The player's transport controls are a layer reached with the confirm button, which is how a remote drives playback without dedicated media keys. | n = 1 | Sep 1, 2026 |
| The console shows fewer items per row than the desktop at every surface, which reduces how far a directional pad has to travel. | n = 5 | Sep 1, 2026 |
| Hint sets are generated per focus zone rather than per screen, so what your device can reach changes as focus moves and the bar reports it each time. | n = 1 | Sep 1, 2026 |
| A hint is shown only where the button is actually handled, which is what makes the bar a reliable inventory rather than an aspirational one. | n = 1 | Sep 1, 2026 |
| The hint bar names button labels including LB/RB and LT/RT, so a reader with a remote can see directly which advertised actions have no key on their device. | n = 1 | Aug 31, 2026 |