coma Scope about coma HOT 3 OPEN

fedons

So, how does it choose what to play? Also, does the stream go "through" the app or is it just a "remote control" (like with grooveshark)?

So how do the rest of you feel about fedons questions? As well as you fedons. Should we increase the scope to allow track selection?

Also should all the playback be done within coma it's self? It might simplify things to delegate playback to the different sources since most of them already have that functionality.

The things to consider for this are:

Delegating playback to the source

1. We don't have to write our own playback code.
2. We will have to write browser extensions for all the different sources to manipulate their web interfaces.
3. Will we stick with one supported browser or write extensions for a few? PhantomJS is unfortunately out because it doesn't support Flash.
4. Using browser extensions will make the playback "code" much more portable across platforms.

Centralising the playback within coma

1. We will have to learn FFMPEG. There is a Go wrapper, but I doubt it abstracts much of the pain away.
2. We will have to use some form of native playback for local files, though this could be delegated again to something like mplayer.
3. Internal playback means less dependencies e.g. a browser. This will allow coma to be installed on headless servers.
4. Internal playback means we will have to use the API's of the different remote sources, this will limit the sources we can use, but could simplify the implementation of the source API.

from coma.

I also like the second option more. But does grooveshark let you stream their music from a 3rd party app?

Spotify has got this: https://developer.spotify.com/technologies/libspotify/, but it only works with premium accounts.

from coma.

That sounds like a ticket (#4) to me :)

from coma.