Can we replace shiva/vlc for mpd?

[tulku]

We could write a sort of mpd client which listens to commands through rabbit queues.
It has the advantage that the same process (easily installable program) can manage the indexing, browsing and playback.

There is a good mpd python client library that we could use:
https://github.com/Mic92/python-mpd2

[alecu]

+1 to replacing shiva and vlc.
and +1 to use mpd for this!

On Mon, Jun 24, 2013 at 10:48 PM, tulku notifications@github.com wrote:

We could write a sort of mpd client which listens to commands through
rabbit queues.
It has the advantage that the same process (easily installable program)
can manage the indexing, browsing and playback.

There is a good mpd python client library that we could use:
https://github.com/Mic92/python-mpd2

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5
.

[fjcapdevila]

+1 to use mpd.

[xcancerberox]

+1 to use mpd.

[dmascialino]

+1

[jairot]

+1 to this, but i don't think that we should modify the data path. So let's replace Shiva and VLC but keep flask as the only one talking to rabbitMQ

[alecu]

On Tue, Jun 25, 2013 at 1:20 PM, Jairo Trad notifications@github.com wrote:

+1 to this, but i don't think that we should modify the data path. So let's replace Shiva and VLC but keep flask as the only one talking to rabbitMQ

Right, but who will listen from RabbitMQ? So far we've not managed to
have the flask process reading from rabbit (afaik). That's why
@tulku's proposal to have a new process reading from rabbit and
talking to mpd sounds reasonable to me.

[jairot]

Ok, I know understand what you want to do. Let's do it!

[vdg0]

I start with this in a new branch: dev. :-)

I will continue, I hope.

[tulku]

That's great!

The best way to continue is that everyone who whats to commit something
should fork the current repo in github, work on the fork (committing to a
named branch, like "mpd" and then pull request to the main repo.

On Thu, Jun 27, 2013 at 1:05 AM, Mariano Verdú notifications@github.comwrote:

I start with this in a new branch: dev. :-)

I will continue, I hope.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-20096174
.

[tulku]

Ah, Mati... Don't forget the tests :)

On Thu, Jun 27, 2013 at 9:25 AM, Lucas Chiesa lucas.chiesa@gmail.comwrote:

That's great!

The best way to continue is that everyone who whats to commit something
should fork the current repo in github, work on the fork (committing to a
named branch, like "mpd" and then pull request to the main repo.

On Thu, Jun 27, 2013 at 1:05 AM, Mariano Verdú notifications@github.comwrote:

I start with this in a new branch: dev. :-)

I will continue, I hope.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-20096174
.

[vdg0]

Done, i remove the "dev" branch in this repo, and then I fork, renaming dev to mpd.