Skip to content

General Information

C. Rubin edited this page Jan 8, 2020 · 1 revision

Table of Contents


What is a UPnP MediaRenderer and how does it work?

  • A UPnP MediaRenderer is a device that is able to play (render) media content when connected with a UPnP Control Point application.
  • The Control Point sends the URL of the media resource to the MediaRenderer (also known as casting), which then loads and plays the media content.
  • All the loading and buffering of the content are handled by the MediaRenderer device.
  • The Control Point also acts as a remote control, allowing users to control the media playback on the MediaRenderer from the Control Point application.
  • If you have a "Smart TV", chances are it can be used as a MediaRenderer device.

What about UPnP Media Servers and UPnP Clients? How are they different from a MediaRenderer?

  • A UPnP Media Server is like a media file server that shares its media content to UPnP Clients on the network.
  • A Client can connect to a Media Server, browse the files and select whichever media file to play on the Client's device.
  • A MediaRenderer has no browsing ability, and can only play media files that are specified by a Control Point. However, a Control Point can specify the MediaRenderer to play media files from a Media Server.

DLNA? Chromecast? Airplay? Miracast? This is so confusing.

  • Yes, my child. Yes it is.
  • DLNA is a specification derived from UPnP that allows sharing of media content between DLNA-certified devices. While the UPnP protocol covers basically any type of network device, DLNA focuses on media devices, adding functions such as DRM protection that were absent in UPnP.
    • Although pure UPnP devices and pure DLNA devices are technically not compatible with each other, most consumer devices that support one would support the other, some even calling the two equivalent.
    • As such, most control point apps that support DLNA supports UPnP, and by proxy, CherryRenderer.
  • Chromecast (also known as Google Cast) and Airplay are proprietary protocols developed by Google and Apple respectively. In very oversimplification terms, the two serves the same purpose as DLNA and UPnP AV with the added "proprietary-ness".
    • No, CherryRenderer does not support Google Cast or Airplay.
  • Miracast is a standard that allows users to mirror their screens to a remote device wirelessly. While Miracast has its benefits, it is not the most ideal choice for sharing media content as it mirrors the device's entire screen.
    • No, CherryRenderer does not support Miracast.

Why was CherryRenderer created?

  • I was introduced to UPnP casting from an Android Anime app called AnYme. While casting to a TV or Raspberry Pi running Kodi was fine, I wanted a way to cast to PC.
  • A quick Google search showed almost nothing that just worked as a MediaRenderer. Popular video players like VLC only works as a UPnP client, while the only other solutions were to install huge bundled software such as Kodi on my PC, which was overkill for just wanting a MediaRenderer implementation.
  • A small group of the AnYme community also wanted a way to watch via the app on their PC, most of which had to resort to screen mirroring or emulators.