I thought I would share what I experienced. It's not a question. We have solved the problem. I am sure that the old media server hounds know about this. I did not do. Hope this saves you some time in the future.
Problem: my customers. The Shoutcast list disappeared, but their provider did not. (Shoutcast has lists for many stations as a convenience. My clients were: http://yp.shoutcast.com/sbin/tunein-station.pls?id=3012xxx, and then he left! Their station did not.
We left several URLs provided to us by the station, and none of them played through our player. Each .pls, .ram file had the same URL (see note) - something like this:
http://74.53.186.162:9082/
How did we solve the problem?
There is a listening link on the Shoutcast console page above. It refers to a URL with the extension .pls. It also shows the sampling frequency, the number of current listeners, etc. The url worked.
What made this interesting was that the file located at this URL was actually a .pls text file with the original URL (something like http://74.53.186.162:9082/)!
What did I find out?
- Shoutcast servers know which client is accessing their data. I would suggest that this is true for IceCast servers. How do I know? Circular URL URL. This means that your player first parses text files in the same way that your browser looks at the mime type.
- The media player classes you use in your code can be really dumb. Theyre sensitive to mime type, bit rate, extension names, etc.
- .pls , .
- IP- , -. , .
. .pls,.ram .. - , URL- . . URL- txt , Shoutcast, , . ( - URL- . .)