Your phone becomes the remote

One switch makes your player a UPnP renderer and media server: pick music on your phone, hear it unconverted through the player's DAC and Infinity DSP. No account.

Three Things It Can Do

UPnP (or DLNA) lets devices on one Wi-Fi share music. Your player is a MediaRenderer (DLNA DMR-1.50) that plays and a MediaServer (DLNA DMS-1.50) that shares its library.

Play to the player

Pick a track on your phone; it plays on the player. The phone only sends the command: the player fetches and decodes, so it sounds exactly as usual.

Browse the player's library

Every track on the player, internal or card, appears in your app with covers, on the Library screen's sixteen shelves. Qobuz, Tidal and NAS entries are left out.

The queue lives on the player

With an OpenHome controller like BubbleUPnP, the player holds the queue (up to 2,000 tracks). Pocket the phone and the album plays on; the app stays in step.

Turn It On — Once

The renderer is off by default — the player advertises nothing on your network until you enable it.

1

Join the same Wi-Fi as your phone

Phone and player need the same network, band and guest/main side (on routers that split them). That's the most common reason a player goes missing. Switch Local Mode off; it pauses UPnP.

2

Settings › UPnP tile › switch on

Open Infinity Player › Settings, tap the UPnP tile in the network row at the top and turn the switch on. It shows the player's network name, e.g. Infinity Player (DX340MAX).

3

Leave Infinity Player running

The player answers on the network as long as Infinity Player is running. In Infinity Pure / Infinity OS mode the app is the device, so it is always ready.

Battery: while UPnP is on, Anantar's deep-sleep helper pauses so your phone can always find the player. No wake lock; Wi-Fi stays connected. Turn it off when done.

Pick a Controller App

No companion app needed: the player implements AVTransport:1, RenderingControl:1, ConnectionManager:1 and ContentDirectory:1, plus OpenHome Product, Playlist, Info, Time and Volume, so any UPnP controller works; start with these.

Android

BubbleUPnP Recommended OpenHome

The controller this feature is developed against. Via OpenHome the queue lives on the player: music plays on when the app closes. Free with ads; paid removes limits.

bubblesoftapps.com/bubbleupnp → · free + paid licence
mconnect Player Alternative

Simpler than BubbleUPnP: pick the player at the top, music below, press play. It speaks plain UPnP AV, so the queue stays on the phone.

conversdigital.com → · free + paid version

iPhone & iPad

mconnect Player Recommended

A long-established iOS UPnP controller from Convers Digital: finds the player, browses its library, sends music to it. mconnect Player Lite is free; mconnect Player is paid.

App Store → · free + paid version
Lumin Alternative OpenHome

Made for Lumin's streamers, but it drives any OpenHome renderer, this player included. The queue stays on the player, so closing the app doesn't stop the album.

luminmusic.com → · free

Windows

foobar2000 Recommended OpenHome

Free. Since 2.25 foobar2000 has UPnP renderer output built in; 2.25.10 added discovery of OpenHome devices like this player. Most direct if your library lives on the PC.

foobar2000.org → · free
JRiver Media Center Alternative

One program to manage a large library and drive the player. Paid, with a trial. Licences are per OS; the Master License covers Windows and macOS.

jriver.com → · paid, trial available

macOS

Audirvana Recommended

Audiophile playback for macOS. Set the player as the output device and Audirvana plays through it. Studio: subscription with Qobuz and Tidal. Origin: one-time licence, local files only.

audirvana.com → · paid, trial available
JRiver Media Center Alternative

The same program as the Windows entry, and a good choice if you already run it at home — but note the per-operating-system licensing above.

jriver.com → · paid, trial available

Third-party apps, not part of or endorsed by Anantar Ultimate; prices and features may change. Only BubbleUPnP on Android is tested first-hand; others follow the UPnP AV standard.

The Three Ways People Use It

Three arrangements, distinguished by which device holds the file and which device decodes it.

Your phone Control point taps only Infinity Player Media server your files Renderer plays it DAC pass-through — the audio never leaves the player

← swipe the diagram sideways

Case 1 — your own music, played on the player. Browse the player's library on your phone and press play. The phone returns the player's own address (http://<player-ip>:8912/media/<id>), so the file is read from storage and audio never touches the network.

Your phone Control point Infinity Player Media server music over Wi-Fi Speaker Renderer The player is the source; the sound comes out of the other device.

← swipe the diagram sideways

Case 2 — your collection, played somewhere else. The player serves your library to a network speaker, streamer or phone. Audio crosses Wi-Fi; Infinity DSP is not involved.

NAS · PC · phone Media server music over Wi-Fi Infinity Player Renderer Infinity DSP · DAC full quality applies Your headphones, your DAC, your tuning — with someone else's library.

← swipe the diagram sideways

Case 3 — music from elsewhere, played on the player. A NAS, computer or phone app sends a track; the player decodes it untouched through your amp card, DAC and Infinity DSP. DSD stays DSD, Hi-Res stays Hi-Res.

What Happens to the Audio

Nothing is resampled, re-encoded or mixed on the way in — the network path ends at the same decoder a local file uses.

Same engine, same DAC

A pushed track takes the same path as one tapped on screen: engine, DAC, filter, amp card and Infinity DSP. DSD Remaster and HRR are Infinity Pure only.

Nothing is re-encoded

ConnectionManager::GetProtocolInfo lists FLAC, DSF, DFF, WAV, L16, AIFF, ALAC/MP4, AAC, MP3, Ogg, Opus, APE, WavPack, WMA and the wildcard http-get:*:audio/*:*, so servers needn't convert. DSD plays natively.

Your own music takes the short road

Tracks already on the player are read straight from storage. Covers, browsing and commands still use Wi-Fi, but the audio never touches the network.

Gapless, and steady on a weak signal

Apps that send the next track early get seamless album transitions. If Wi-Fi stumbles mid-track, the transfer resumes from the exact byte, retrying for up to two minutes.

What the Player Puts on the Network

Every line below can be checked from your own machine: with the switch on, open http://<player-ip>:8912/desc.xml in a browser.

Show the full list
Devices published
MediaRenderer:1 and MediaServer:1 — two UUIDs, one friendly name (e.g. Infinity Player (DX340MAX))
DLNA profile
X_DLNADOC DMR-1.50 (renderer) · DMS-1.50 (server)
UPnP AV services
AVTransport:1 · RenderingControl:1 · ConnectionManager:1 on the renderer; ContentDirectory:1 · ConnectionManager:1 on the server
OpenHome services
Product:1 · Playlist:1 · Info:1 · Time:1 · Volume:1
Discovery
SSDP on 239.255.255.250:1900 — ssdp:alive every 10 minutes, CACHE-CONTROL max-age=1800, a new BOOTID.UPNP.ORG on every start, ssdp:byebye on stop
Eventing
GENA; subscription 60–3600 s, default 1800 s; LastChange on AVTransport and RenderingControl
Endpoints
http://<player-ip>:8912/desc.xml and /server.xml — port 8912 when it is free, otherwise a port the system assigns
Formats accepted
GetProtocolInfo returns audio/x-flac · audio/flac · audio/x-dsf · audio/dsf · audio/x-dsd · audio/dsd · audio/x-dff · audio/dff · audio/wav · audio/x-wav · audio/L16 · audio/x-aiff · audio/aiff · audio/mp4 · audio/x-m4a · audio/aac · audio/mpeg · audio/ogg · audio/opus · audio/x-ape · audio/x-wavpack · audio/x-ms-wma · audio/*
Serving its own files
HTTP/1.1 with byte ranges (206 Partial Content, Accept-Ranges: bytes) · transferMode.dlna.org: Streaming · contentFeatures.dlna.org: DLNA.ORG_OP=01
Incoming streams
Content-Type is read and the format resolved once before playback starts, so a server URL with no file extension is still decoded correctly
Network stall
the transfer is re-requested with Range: bytes=<sent>- and retried for up to 120 seconds
Library published
tracks backed by a readable file on the player only (internal memory and card); Qobuz, Tidal, SMB and network rows are excluded
Browse tree
16 containers mirroring the Library screen — Favourites, Albums, Singles, Artists, Playlists, Compilations, Hi-Res & format, Genres, Languages, Years, Awards, Dynamic range, Storage, Folders, AI Mixes, Recently played (last 200)
Search capabilities
dc:title, dc:creator, upnp:artist, upnp:album, upnp:genre, upnp:class — full-text title index plus artist and album names, at most 500 results
Sort capabilities
+dc:title, +upnp:artist, +upnp:album, +upnp:originalTrackNumber, +dc:date
Queue held on the player
OpenHome TracksMax = 2000; a plain UPnP AV controller supplies the current track and one next track only
Transcoding
none, in either direction
Security
none — UPnP defines no authentication. LAN only; nothing is reachable from the internet

Troubleshooting

Almost everything that goes wrong is a network problem. These are the ones that came up during development, and what to check for each.

The app cannot find my player

Check UPnP is on, the app running and both devices on the same Wi-Fi; AP/client isolation or a phone VPN blocks SSDP (239.255.255.250:1900). Pull to refresh or toggle the switch.

I see it, but nothing plays

Set the renderer to the player, not just the library, and check the player's volume. From a NAS, exotic containers fail: the audio/* wildcard means nothing is converted.

There are two entries with the same name

That's intentional: one is the library (media server), one the player (renderer). Apps list servers under "Library" or "Browse" and renderers under "Play to" or "Renderer".

The clock froze and the cover disappeared after the app restarted

A stale event subscription from before the app restarted. The player now advertises a fresh BOOTID.UPNP.ORG at every start so controllers re-subscribe; if it still happens, restart the controller app.

Does it drain the battery?

While UPnP is on, the deep-sleep helper pauses so the player stays findable; no wake lock is taken. Switch it off when finished and deep sleep returns immediately.

Does it work in Infinity Pure / Infinity OS mode?

Yes: renderer, media server and native DSD work in Android and Infinity Pure; DSD Remaster and HRR are Pure-only, as for local tracks. In Pure the player is always on the network.

It says "Paused — Local Mode has Wi-Fi off"

Local Mode is the offline setting: Wi-Fi and Bluetooth stay off, and UPnP, WiFi Transfer and Rsync pause. Switch it off in Settings and the player rejoins the network by itself.

Can I send an internet radio stream to it?

Yes. A live stream plays like any other track, just with no end and no next track. For stations you play often, the player's own Internet Radio screen is quicker.

Can anyone else on my Wi-Fi control it?

Yes: UPnP has no password, so anyone on your network can browse the player and send it music; nothing is reachable from the internet. On networks you don't control, leave it off.

Three Words the Apps Will Use

Three words do most of the work in these apps. Knowing them makes every settings screen on this page read the same way.

Media Server

The device that holds the music and lists it for others. It never makes a sound.

Your player, a NAS, or a PC sharing a folder.

Renderer

The device that plays the music — it fetches the file and drives the DAC. This is what "play to" means in the apps.

Your player, or a network speaker.

Control point

The app you tap. It pairs a server with a renderer, never touching the audio. OpenHome controllers can then close; plain UPnP AV ones must stay awake.

BubbleUPnP, mconnect Player, foobar2000, Audirvana.
You'll sometimes see these called "library" and "player"; the real names above make every app's settings screen clear at a glance.

Not running Infinity Player yet?

UPnP/DLNA ships in V12, at no cost, like the rest of Infinity Player. Install or update the module and the switch is in Settings.

⬇ Install Anantar Ultimate