View Full Version : Streaming on port 80
Eddie Knight
24th July 2007, 14:05
Hello everyone! Are there any plans to offer streaming on port 80?
Meanwhile I have to use http://www.playerflash.net/ to listen to EVE Radio but that player caches the stream, closes the connection after some time and plays the cached version until you start it again. It's really annoying :(
Does anyone know about other players that can do the same thing?
Danmor
24th July 2007, 19:12
Are you behind a Router/Firewall/Proxy, that blocks ports other than 80?
Eddie Knight
26th July 2007, 05:46
Unfortunately, yes. I've tried other solutions, such as IceCast (couldn't set it up properly for some reason) and HTTP Tunnel (the free version disconnects every couple of minutes). They are all too much hassle to use and I tought it shouldn't be such a bad thing for GRN to stream on 80 since, the users that will use that stream would've already used the 8000 stream if they could.
Heck, I don't even want a broadband stream, as long as I can listen to EVE Radio :)
Danmor
26th July 2007, 12:56
Hmm... I'm not aware of any plans to stream on port 80 (But usually nobody tells me anything, so there still is hope ;) ).
If you are behind a proxy, you could try to supply your player with the proxy's address.
If you are behind a firewall ... no idea, sorry.
Perhaps we could put one of those flash player thingies onto the websites sometime in the future.
And perhaps we should move this thread to: Gaming Radio Network > Technical Support
Tempest
26th July 2007, 13:04
Providing a player such as winamp with your proxy server details works most of the time, I would suggest trying that.
Ross
26th July 2007, 19:44
Hi Eddie Knight,
I'm afraid we don't have any plans to start streaming on port 80. The reason is, we use Shoutcast to distribute our live audio to listeners. It is set to stream on port 8000 (The default, recognised port for steaming Shoutcast media). If we were to steam on an additional port, this would require the broadcasting DJ to stream to two seperate Shoutcast instances. What this means is, the DJ would be using double the upload bandwidth (So 256Kbps rather than 128kbps). Generally 256Kbps is the limit of most of our DJs upstream bandwidth, which would result in skips and buffering for our listeners.
The other option would be to stop streaming on port 8000 and stream on port 80 only. This, however, can cause connection problems for end users depending on their computer and ISPs configurations. So this is not a viable option.
I hope this helps you to understand why we are currently unable to offer a port 80 stream.
qgazq
26th July 2007, 23:05
I agree really there shouldn't be any need to stream on port 80,
for 99.9% of people there is a way around proxies etc.
Also currently there is a web server on the broadcast machines so it couldn't be done without setting new ips up or routing etc which wouldn't be trivial.
However as for the DJs needing double bandwidth that isn't necessarily true.
As they would be the same bandwidth the port 80 server could just be set to relay from the main one.
Then the only extra bandwidth would be loopback on the server.
But the extra setup, server load etc I can't imagine it is worth it for the 1 or 2 listeners it would help.
Sorry caller.
BTW I'm not part of staff - all views are my own etc
QGazQ
vBulletin® v3.7.2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.