Add a DLNA Media Server (DMS) frontend

[jodal]

We could expose the Mopidy library to DLNA players/renderers if we add a DLNA Media Server (DMS) frontend. This would allow modern TVs and other DLNA compatible players to play music served by Mopidy.

Coherence is a Python implementation of DLNA, and may help us implementing this.

Note: This issue does not concern Mopidy playing music stored on other DLNA Media Servers, like a NAS on your local network. For that feature, see #230.

[ruudud]

Maybe Brisa (discovered through http://www.gossamer-threads.com/lists/maemo/developers/49708?do=post_view_threaded) can provide something to this.
It is an UPnP Framework in Python with an WSGI interface.

[adamcik]

https://live.gnome.org/Rygel via GI might also be an option.

[jodal]

Rygel looks like a nice solution. I haven't considered integrating using GI, but through D-Bus, as I see that Rygel can do "Export of media hierarchies provided by external applications through implementation of D-Bus MediaServer spec".

We would need to support the D-Bus MediaServer2 spec. The technical part of the implementation would be very similar to the D-Bus MPRIS spec we already support. The MediaServer2 spec is oriented around a hierarchy of media containers and items, and optionally search. In other words, it should map well to Mopidy as we can expose Spotify playlists as containers and have searches in a "magic" Spotify container result in full Spotify searches.

Two things we need to keep in mind/consider:

1. Any folder hierarchy model in Mopidy should support triggering events:
   • on folders when folders/items within are added/modified/deleted, and
   • on folders when the folder is modified/deleted.
2. We should probably port our DBus code from python-dbus to GDBus before extending it. According to http://www.freedesktop.org/wiki/Software/DBusBindings, GDBus may be used through GI.

[jodal]

@skagappa has started working on a proof of concept of this at: https://github.com/skaggapa/mopidy/commits/feature/mediaserver2

[jodal]

We don't currently find it very interesting to:

• expose Mopidy's library to other DLNA devices, or
• let other DLNA devices control Mopidy.

However, letting Mopidy play music from DLNA libraries may be a nice extension.

[0xcaff]

I believe a DLNA renderer connecting to a mopidy server and playing the PCM which would typically come out the speakers would be interesting because most consumers don't have their big speakers hooked up to their PC but their entertainment center which consists of gaming consoles, BluRay players and Smart TVs, all of which probably have DLNA capabilities. This would allow you to keep your speakers hooked up to your Media Center and have your server offsite, like in your basement.

[Blackskyliner]

👍

[jodal]

https://github.com/tkem/mopidy-dleyna lets Mopidy play music from DLNA servers, like a NAS.

[Blackskyliner]

But sadly not the other way around. As in what the core idea this ticket was about.

[tkem]

@Blackskyliner: true, mopidy-dleyna is a backend.

[liamw9534]

Worth taking a look at
http://www.digitaltrends.com/home-theater/wireless-speaker-buying-guide/
for an overview of the different technologies being used.

I don't personally have any DLNA speakers but messed around a lot with
Bluetooth speakers which work very well....as long as you don't mind a
slightly restricted range.

I would like to get hold of a pair of WiFi speakers to see how they
work....I hear that many of them are using WiFi Direct now because it
offers a dedicated wireless link allowing much higher audio sample
resolutions to be achieved. There is also AirPlay (which I think
PulseAudio supports).

On 1 July 2015 at 19:40, Martin Charles notifications@github.com wrote:

I believe a DLNA renderer connecting to a mopidy server and playing the
PCM which would typically come out the speakers would be interesting
because most consumers don't have their big speakers hooked up to their PC
but their entertainment center which consists of gaming consoles, bluray
players and Smart TVs, all of wihch probally have DLNA capabilities. This
would allow you to keep your speakers hooked up to your Media Center and
have your server offsite, like in your basement.

—
Reply to this email directly or view it on GitHub
#52 (comment).

[0xcaff]

Its not just speakers. Many TVs and BluRay players support DLNA streaming. It would nice if we could stream audio (video too?) to it of what mopidy is playing.

[gerroon]

+1 pretty please

[jedi7]

Hi, this feature request is useful to send media to AV receiver for playing, right? It will be very good. Is someone working on it?

[da-anda]

I am surprised that mopidy doesn't have a DLNA/upnp backend and also would very welcome it. Until then I will have to look for alternatives for mopidy

[kingosticks]

It does have a DLNA backend called Mopidy-DLeyna, this is already mentioned above. This issue was regarding a DLNA frontend, there's more up to date info at https://docs.mopidy.com/en/latest/upnp/ which may suit your usecase if you want to use Mopidy as a renderer alongside some upnp controller you have.

[da-anda]

I know it can act as renderer, but since mopidy is a music server, it would make more sense if it could act as UPNP/DLNA server so that you can browse and play music from your mopidy library on any home AV gear and radios. At least all the docs I found only indicate that using rygel it will only act as renderer.

Might stick to Jellyfin for now to share my music library to UPNP devices

[kingosticks]

OK, thanks, it is clearer what you mean. I see where you are coming from and I don't disagree it would be good to have but it's worth keeping in mind that in the DLNA sense, Mopidy is (currently) more a DLNA Renderer than a DLNA Media Server. I think what makes the most sense depends what side you are looking from; there are many sides!

This is another good reason we should implement support for a HTTP streaming audio output, I had forgotten this usecase and the lack of HTTP streaming is a blocker here (as far as I can see).