Is there a direct mp3 stream URL?

[Roberto Rivera]

I'd like to use the standard HTML5 <audio> structure to stream. However I have to provide an mp3 stream. Any help would be appreciated.

 

[Support]

Hi Robert,

Here is the url that you require: us2.internet-radio.com:8085;

Its important that it has the semicolon at the end of the address.

 

[Roberto Rivera]

Perfect! I had to add a forward slash "/" between 8085 and the semi-colon ";", and add the "http://" at the beginning for it to work as expected. Testing in all browsers now.

However I'm noticing that the web proxy link isn't working.
http://45.79.186.124/stream/tobieapb.pls

 

[Support]

Oh ok, that's interesting. But we are pleased that this works for you now all the same.

We shall take a look into the web proxy link for you and get back to you.

 

[Support]

http://45.79.186.124/stream/tobieapb.pls works now.

 

[Roberto Rivera]

Thanks!

Also, maybe it might have been an error on my part. Was trying to use the TuneIn URL for the web proxy (ending in ".pls") in the html5 AUDIO tag. This is the URL I'm using:
http://45.79.186.124/proxy/tobieapb?mp=/; You can see it working here: http://www.radiopaz810.com (player on the bottom, at right).

Hypothetical, if all my listener are connected through the proxy, does that affect quality, uptime, or connectivity?

 

[Roberto Rivera]

IMPORTANT:

If you're using the html5 AUDIO element/tag and you're not making it autoplay, use preload="none" attribute.

I put 2 AUDIO elements, in a single page. One for the regular stream, and the other one was for the Web Proxy stream. I noticed that they would both connect, and I could see the both in my active Listeners page. They even had the same connection duration. This is bad, as even if the user isn't listening, he will consume bandwidth. And in this case, (in which I had 2 in the same page) it would consume TWICE the bandwidth.

#WordOfCaution

 

[Support]

Thanks!

No problem

Hypothetical, if all my listener are connected through the proxy, does that affect quality, uptime, or connectivity?

No, not at all.

IMPORTANT:

If you're using the html5 AUDIO element/tag and you're not making it autoplay, use preload="none" attribute.

I put 2 AUDIO elements, in a single page. One for the regular stream, and the other one was for the Web Proxy stream. I noticed that they would both connect, and I could see the both in my active Listeners page. They even had the same connection duration. This is bad, as even if the user isn't listening, he will consume bandwidth. And in this case, (in which I had 2 in the same page) it would consume TWICE the bandwidth.

#WordOfCaution

Thanks for the words of advice. Hopefully that will be useful to know for some other people as well.