list2blog for the nettime-l and nettime-ann mailing lists
Two freeflux list2blog relays for the nettime-l and nettime-ann mailing lists:
http://nettime.freeflux.net
http://nettime-ann.freeflux.net
Two freeflux list2blog relays for the nettime-l and nettime-ann mailing lists:
http://nettime.freeflux.net
http://nettime-ann.freeflux.net
Relaying Deep Mix Moscow Radio mini howto
By popular demand, a little howto for setting up a stream relay for Deepmix Moscow Radio:
Deepmix is using Nullsofts shoutcast server for streaming. I first tested relaying with icecast2, and it worked perfectly fine - including propper meta informations about the stream etc. Thanks to the recommendations from the deepmix guys and due to the fact of yet no experience with a shoutcast server, the desicion was made in favour for the shoutcast variant.
The procedure is fairly simple:
1) Download the shoutcast server from here
2) After unpacking, there should be a sc_serv binary, and a sc_serv.conf
3) Download the Deepmix intro jingle from here
4) Edit sc_serv.conf. Here is my sc_serv.conf - every directive is described.
Now you're ready for relaying, but you won't be allowed to fetch the deepmix stream unless the ip of your box is added to the list of permitted relayers (Request here).
5) cd to the shoutcast dir and execute sc_serv
Once the stream is up and running, deepmix will take care of the listeners that get assigned to your relay.
The shoutcast admin interface can be found at http://yourhost:<shoutcast-port>/. The same url applies for pointing your player to the stream.
My relay runs for a week now, and the listener queue is almost constantly full. The shoutcast server doesn't needs much CPU (avg. 0.3%), but about 2-3MB Ram per listener - and of course bandwidth.
Deepmix is using Nullsofts shoutcast server for streaming. I first tested relaying with icecast2, and it worked perfectly fine - including propper meta informations about the stream etc. Thanks to the recommendations from the deepmix guys and due to the fact of yet no experience with a shoutcast server, the desicion was made in favour for the shoutcast variant.
The procedure is fairly simple:
1) Download the shoutcast server from here
2) After unpacking, there should be a sc_serv binary, and a sc_serv.conf
3) Download the Deepmix intro jingle from here
4) Edit sc_serv.conf. Here is my sc_serv.conf - every directive is described.
Now you're ready for relaying, but you won't be allowed to fetch the deepmix stream unless the ip of your box is added to the list of permitted relayers (Request here).
5) cd to the shoutcast dir and execute sc_serv
Once the stream is up and running, deepmix will take care of the listeners that get assigned to your relay.
The shoutcast admin interface can be found at http://yourhost:<shoutcast-port>/. The same url applies for pointing your player to the stream.
My relay runs for a week now, and the listener queue is almost constantly full. The shoutcast server doesn't needs much CPU (avg. 0.3%), but about 2-3MB Ram per listener - and of course bandwidth.
deepmix moscow radio in need of bandwidth
Deepmix Moscow Radio - one of the finest idm netradios IMHO - is in need of bandwidth.
Huge western traffic caused Russian internet service providers interest in earning big bucks. We have received an invoice, which is just not possible for us to cover.
One possible way to solve the problem is to mirror their stream. If someone with a server and some bandwidth likes to mirror it for some listeners, don't hesitate to the deepmix crew.
My humble relay for about 10 listeners is accessible here: http://relay.var.cc:8128/listen.pls
1-3/3
