AA Signature UPnP Renderer and Media Server

We developed AA Signature UPnP Renderer and Media Server for Windows-based computers from ground-up, by audiophile for audiophiles worldwide. Download for trial is available now. Price will be announced soon.

Our Motivation

We love JPLAY for iOS so much, but we cannot find UPnP renderers and UPnP media servers for Windows which meet our high standard of faithful audio reproduction. We decided to develop these on our own for purists.

Abstraction

AA Signature UPnP Renderer and Media Server are written in C and C++. The renderer codes are highly optimized without any polling but event-driven. Both are light-weight and compact. They run as Windows services and start automatically without requiring Windows login. Setups for renderer and server done via JPLAY iOS configuration page. First time installation requires remote login into the music server.

Why Windows? The world’s best music server from Netherland uses Windows, an O/S supported and maintained by a huge software company unlike many versions of Linux, not all maintained properly.

How The Renderer Is Different?

  • What bit-depth to use when playing music, either always use the max or a fixed bit-depth supported by DAC or automatically select based on the source.
  • DAC capability probing done once during first-time DAC connection and setup.
  • Works with and without manufacturer-supplied USB DAC driver. User to listen and select which one sounds better.
  • Hot plugging and unplugging of USB DAC supported. User preferences saved and recalled during hot plug.
  • When DAC is offline or requires first time setup, the renderer adds [No DAC] or [Setup DAC] to its name.
  • Huge buffers supporting large files playback.
  • Target latency can be set.
  • Render options using WASAPI or WDM-KS. We prefer WDM-KS.
  • Supporting OpenHome is an optional feature. This works with local files when using BubbleDS or BubbleUPnP controller in OpenHome mode, i.e. controller can be offline while renderer continues playing.

What’s Special About The Media Server?

  • Use file:// instead of http:// for local files, supported by JPLAY controller. This means local files are treated as local files. Works only when Server and Renderer running on the same machine.
  • We developed workaround for other UPnP controllers so that renderer can detect if local files are to be played. Works only when Server and Renderer running on the same machine.
  • For WAV files with correct folder structure (Artist / Album / nn – Track Name.wav) but without ID3 tags, the server will derive and create the tags (optional feature). This happens when CDs were ripped using EAC or CUERipper.
AA Signature Network Renderer and Media Server
How your music reaches the DAC

You choose music on a tablet or phone. The media server finds it, and the renderer plays it, both on one Audio PC, which is wired to your network (no Wi-Fi) and connected to your DAC by USB. For music stored on the Audio PC, the renderer and the server work together directly, inside the PC. Inside the renderer, the part that talks to your tablet and the part that plays the audio are kept apart, so network activity never runs alongside the audio.

Wired LANinternet streaming, both ways

UPnP over the networkthe controller app: Wi-Fi to the router, then wired LAN to the Audio PC

Inside the rendererfront end to engine, and through the engine

Renderer and server, directthe renderer asks for a file, the server returns the music file

To the USB DACWDM-KS or WASAPI exclusive, over USB

Cores and priorities

On a 4-core music PC, each part gets its own place. Pinning is a setting on the setup page; the priorities always apply.

Core 0Windows

Left to Windows and its drivers. Nothing of ours runs here.

Core 1Renderer front end and media server

Low priority, below normal.

Core 2Audio engine

Stream reader and decoder at normal priority, working well ahead of the DAC.

Core 3Output thread, alone

Windows “Pro Audio” priority, at its highest level, while the DAC is playing.

The media server

It scans your music folders, reads each track’s tags and cover art, and lets the UPnP Controller browse and search the library. For music on the same PC, the server and the renderer work together directly for local playback. Every file is served exactly as it is on disk. Nothing is converted.

The renderer’s two halves

The UPnP front end handles everything your control app asks for: what to play, the playlist, volume and what is playing now. The audio engine is a separate process that only fetches, decodes and plays. A busy control app or a setup page left open never runs alongside the audio.

The audio path

  1. The stream reader fetches the track into the stream buffer, well ahead of playback: from the media server for music on this PC, or over the wired LAN for internet streams.
  2. The decoder turns it into audio samples in the output buffer.
  3. The output thread sends them to the DAC with exclusive use of the device, bit-perfect, by one of two methods chosen on the setup page. WDM-KS (kernel streaming) talks straight to the DAC’s driver with no Windows audio in between. WASAPI exclusive is Windows’ own exclusive mode, with no mixing and no resampling.
  4. The next track is decoded before the current one ends, for gapless playback.

First Time Setup

Go to our Download page, download and install the suite for 14-day free trial.

User Manual is under development.