New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a DLNA Media Server (DMS) frontend #52

Closed
jodal opened this Issue Jan 19, 2011 · 14 comments

Comments

9 participants
@jodal
Member

jodal commented Jan 19, 2011

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

This comment has been minimized.

Contributor

ruudud commented May 25, 2011

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

This comment has been minimized.

Member

adamcik commented Sep 2, 2012

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

@jodal

This comment has been minimized.

Member

jodal commented Sep 2, 2012

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

This comment has been minimized.

Member

jodal commented Jan 21, 2013

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

@adamcik adamcik closed this Oct 4, 2013

@jodal

This comment has been minimized.

Member

jodal commented Oct 4, 2013

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

This comment has been minimized.

0xcaff commented Jul 1, 2015

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

This comment has been minimized.

Blackskyliner commented Aug 20, 2015

👍

@jodal

This comment has been minimized.

Member

jodal commented Aug 20, 2015

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

@Blackskyliner

This comment has been minimized.

Blackskyliner commented Aug 20, 2015

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

@tkem

This comment has been minimized.

Member

tkem commented Aug 20, 2015

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

@liamw9534

This comment has been minimized.

liamw9534 commented Aug 20, 2015

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

This comment has been minimized.

0xcaff commented Aug 20, 2015

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

This comment has been minimized.

gerroon commented Oct 20, 2017

+1 pretty please

@jedi7

This comment has been minimized.

jedi7 commented Sep 28, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment