Radio station support about node-sonos-discovery

[jonathanKingston]

The example radio I was listening to was BBC radio 6.

[jishi]

Yes, it needs to differentiate the rendering between different services. Low priority though because it "works", but if you want to fix it, feel free to send a pull request.

Pointers: Try to identify if other music services has different views.
Radiostations is sort of a list, with different bit rates (that it seems to switch between somehow), make sure that this is considered when selecting the actual metadata.

[jonathanKingston]

@jishi thanks, I thought it was safer to add new keys than merge the meanings. I will do much further debugging. As you mention each station seems to do different things here.

[jishi]

Consider that the metadata (or trackinfo you might call it), is the same regardless if it is the http-api or the web-controller that interacts with it. It's preferable that the "info" is standardized and readable, but with a good distinction on how it may differentiate.

Because of that it might be preferable that when it's a radio station, the track name etc is the stationname (instead of uri which seems to be the case today), and album and artist maybe empty, and instead an optional "currently airing" or similar. That way it will interact better with different implementations (consider that someone requests info through the http-api in json-format and populates a display, for example).

[jonathanKingston]

@jishi let me know what you think, I tried it on quite a lot of different stations.

The parsing part probably could do with a bit of a refactor to have it in a function. I noticed the transportMeta also holds the playlist info too which could be used as part of this further refactor.

Certainly its a start to resolve this issue.

[jonathanKingston]

@jishi I fixed the merge conflicts here, not sure if you had any thoughts regarding this.

Fixed in:
#19