bpa wrote:
> I haven't seen any metadata transmitted in these URL which can identify
> the stream or what is playing. If is the case then the station name will
> have to be "hard coded" in some own to be associated with a specific
> URL. This is never a good solution.
Yeah, that is indeed a bit grim.
It's interesting to note that the world service feed, which takes rather
a different pattern, /does/ (according to ffprobe) have a metadata
channel:
Code:
--------------------
Program 0
Metadata:
variant_bitrate : 64000
Stream #0:0: Audio: aac (HE-AAC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo,
fltp, 65 kb/s
Metadata:
variant_bitrate : 64000
Stream #0:1: Data: timed_id3 (ID3 / 0x20334449)
Metadata:
variant_bitrate : 64000
--------------------
I haven't looked to see what's in that ID3 stream, but it's odd that the
national networks' feeds don't appear to have it. Maybe the World
Service is staying a bit more old-school!
The iPhone app fetches some JSON objects both to provide human-readable
station names and to update its now playing information. There's a
mapping from the station-id part of the streaming URIs to station name
in the first of those, and the URI of the second is straightforwardly
derivable from the stream URI too. So it looks good for putting
something reasonably robust together.
Happy to share logs of what I see the iPhone app doing with my network
when it tunes in to a station to any interested parties, but of course
don't want to spam this forum with big web proxy logs or JSON files!
------------------------------------------------------------------------
gallafent's Profile: http://forums.slimdevices.com/member.php?userid=64018
View this thread: http://forums.slimdevices.com/showthread.php?t=53229
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
