Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mopidy – Server which can play music from multiple sources

docs.mopidy.com

Post reply on HN
Print view View original

11–20 of 36 posts

Re: Mopidy – Server which can play music from multiple sources

#11

Post by adamcik »

xzel wrote: post #9

Looks like I have a new weekend project. If the dev or someone who has used this heavily is lurking here: I couldn't find this in the documentation but is it possible to setup multiple local sources? Would I just setup mopidy on all of those computers? Is there a way to stream them into a single library so I don't have to connect to all of the sources every time I change clients? Thanks

Normally you would have one machine hooked up to your speakers and then use clients on the other ones to control the central music server.

In the longer run I keep wanting to get https://github.com/mopidy/mopidy/issues/408 solved, basically having a main server and then audio only servers for true multiroom.

Re: Mopidy – Server which can play music from multiple sources

#12

Post by adamcik »

dktbs wrote: post #5
drdaeman wrote: post #3

Curious. Does anyone know whenever it plays only locally or can stream it further (like to a desktop computer or phone)? If so, it could be plain awesome. I'm imagining a server in closet that aggregates music collections from various sources and provides uniform interface to play it anywhere network-accessible.

yes, you can access it remotely. mopidy is an MPD server, so any platform that has a compatible MPD client should be able to access it. The docs list a lot of the available clients and their compatibility with mopidy: http://docs.mopidy.com/en/latest/#clients

You can control mopidy remotely, but not yet stream to remote clients.

Re: Mopidy – Server which can play music from multiple sources

#14

Post by pekk »

dktbs wrote: post #5
drdaeman wrote: post #3

Curious. Does anyone know whenever it plays only locally or can stream it further (like to a desktop computer or phone)? If so, it could be plain awesome. I'm imagining a server in closet that aggregates music collections from various sources and provides uniform interface to play it anywhere network-accessible.

yes, you can access it remotely. mopidy is an MPD server, so any platform that has a compatible MPD client should be able to access it. The docs list a lot of the available clients and their compatibility with mopidy: http://docs.mopidy.com/en/latest/#clients

Mopidy is lacking some important features of mpd itself

Re: Mopidy – Server which can play music from multiple sources

#16

Post by mplewis »

Mopidy is a fantastic piece of software. I once wrote a Node.js server to provide a public web interface to a single shared playlist, put it on a Pi, and hooked it up to an amplifier.

https://github.com/mplewis/accentor

I might come back to this project later—the docs are pretty lacking, but the software works!

Re: Mopidy – Server which can play music from multiple sources

#18

Post by jwise0 »

adamcik wrote: post #8
drdaeman wrote: post #3

Curious. Does anyone know whenever it plays only locally or can stream it further (like to a desktop computer or phone)? If so, it could be plain awesome. I'm imagining a server in closet that aggregates music collections from various sources and provides uniform interface to play it anywhere network-accessible.

We still have a few blockers for proper streaming support. But we are slowly but surely getting closer to have something like that working. https://github.com/mopidy/mopidy/issues?labels=EOS&state=ope...

The use case that I'd be really excited about -- and something that I have been strongly considering hacking MPD to do -- would not be an icecast stream to my phone, but for my phone to have its own Mopidy or MPD instance.

Right now, at work, I simply NFS mount my home music library, and then sync my mpd tag cache over periodically. This works while I'm in one location, at work, but would not work on my cell phone; I don't have a network protocol that would survive it, and MPD has no real support for high-latency filesystems (it doesn't know to go fetching the next file in advance, nor does it know to go cache a few megabytes -- or the next few songs -- in case the data link goes away).

Mopidy's extension support is pretty exciting, then! It seems like it should be relatively possible to concoct a 'mopidy.remote' extension that knows how to do these things, and the corresponding server-side for a Mopidy instance running at home.

Have you folks thought of this sort of use case? Am I about to reinvent the wheel?

Re: Mopidy – Server which can play music from multiple sources

#19

Post by rakoo »

adamcik wrote: post #10
rakoo wrote: post #2

I am both happy to see such a useful software and saddened to see that it's reimplementing tomahawk [0] from scratch. Let's see where it all leads! [0] http://www.tomahawk-player.org/ .

Part of the reason for having started mopidy was that we wanted something MPD like, but with Spotify support, which at the time was not reasonable to integrate directly. Now we've evolved quite a bit since then and are now at a stage where we are modular music server, where the MPD frontend is just one of many possible ways of talking to our server. Additionally everything is an extension, so we don't end up like som…

Actually tomahawk's logic was based off of playdar[0], which is a "Music content resolver", what mopidy seems to be. I'm not close to the project, but it seems like playdar focused too much on the server and lacked a really good ui. They started from scratch with Tomahawk, and now are based on a UI.

[0] http://www.playdar.org/

Re: Mopidy – Server which can play music from multiple sources

#20

Post by rakoo »

stingraycharles wrote: post #4
rakoo wrote: post #2

I am both happy to see such a useful software and saddened to see that it's reimplementing tomahawk [0] from scratch. Let's see where it all leads! [0] http://www.tomahawk-player.org/ .

I'm unfamiliar with both. How do they compare, and which would you recommend?

I'm also not completely familiar with tomahawk, although I have read quite a bit about it.

Tomahawk is a UI that has a standard "music player" behaviour. The sources are plugged in (they're called resolvers[0]), so that the core remains more or less the same.

AFAIU, mopidy acts a middle-man between sources (installed as plugins) and uis. It's more or less what playdar [1] (the ancestor of tomahawk) was, at least functionnally.

[0] https://github.com/tomahawk-player/tomahawk-resolvers [1] http://www.playdar.org/

Post reply on HN