Shoutcast Streams do not work in IE

[Anthony]

Hi,

I have an issue with Shoutcast streams, I have a stream playing within firefox but the same player does not work in IE, now I know the first thing you will say is it it the flash fall back but if I change the stream to a static file, say the example m4a file, it plays fine and I am using IE10.

Below is the player, any help would be great as I am so nearly there and have styled the player within Firefox.

    $("#jquery_jplayer_1").jPlayer({
        swfPath: "http://www.jplayer.org/latest/js/Jplayer.swf",
        ready: function () {
        $(this).jPlayer("setMedia", {
        mp3: "http://******:****/;stream/1" })
        .jPlayer("play");;
        },
        supplied: "mp3"
    });

[Mark Panaghiston]

A likely cause would be the mime type. Shoutcast streams often have the content type setup incorrectly... Maybe because it is not giving any content type at all, and using ICY Headers. IE10 and IE9 are strict with the content type and will not play it unless it is correct... I think IE9 tried to play media if there was no mime type at all, but not sure about ie10. The W3C spec has changed to allow the application/ocet-stream type as a "suck it and see" mime type, but not sure if IE10 implemented that... The correct mime type should be being used by yur server.

Also, see the streaming demo. It might help if you do not want a paused stream to download and then resume from when paused.
http://www.jplayer.org/latest/demo-08/

[Anthony]

Hi Mark,

Thanks for your response, I have tried this player now with several streams and cannot get any to work within IE, as the stream works with other players and I cannot get other streams to work with this player I am more convinced that this is due to a configuration problem rather than a server issue specific to my setup.
Any help would be great and a working example of a shoutcast stream that does work in Internet explorer would be greatly received as I may be able to spot the difference as it were.

Many thanks,
Anthony

[Anthony]

Hi,

Is anyone able to show me a link to a working jPlayer that can play a shoutcast stream within internet explorer, I still have lots of peoples examples, not of which work within IE as a shoutcast player. If it is possible I would love to use the player before I have to resign to purchasing a flash player.

Many thanks,

On Monday, April 22, 2013 5:51:54 PM UTC+1, Mark Panaghiston wrote:

[Mark Panaghiston]

I've had IE10 working with shoutcast and icecast mp3 streams.

The demo uses an icecast stream with mp3:
http://www.jplayer.org/latest/demo-08/

Give a link to your development area and maybe I can help you further.

For example:
Some people do not think a DOCTYPE is important and then complain that other HTML does not work. IE would assume you wrote your webpage about 15 years ago and use ghetto mode. (Quirks mode)
Some people think that a DOCTYPE is valid anywhere in the page, the spec says the 1st line and IE has always been rather strict on this, ignoring it anywhere else.

[Anthony]

Hi Mark,

I have emailed you a link to the site, please let me know if you do not receive, any help with this would be great as I cannot get any shoutcast stream to work with the player.

Kind regards,
Anthony

[Rob Dawson]

I've checked my site with Firefox 23 today out of curiosity, and that is exhibiting the same behavior now as IE as described in this thread, whereas Firefox 20 works.
'HTTP "Content-Type" of "text/plain" is not supported. Load of media resource http://MYURL:8000/stream/1/ failed.

This maybe down to improvements in Firefox 23's native handling of html5 audio data via Windows media foundation API (?), and not falling back to Flash, which, works in all cases.

If I use the demo-08 with the ICE stream, it works as expected in all browsers, But if I replace the stream URL in demo-08 with a Shoutcast V2 stream, it will spit out the above error.
Adding a ; in the stream URL makes no difference.
Is Shoutcast sending incorrect information? I 'm not knowledgeable enough to know if configuring mime-types for shoutcast V2 is something that can be done, if it is, please enlighten me :)

On Monday, 22 April 2013 17:44:36 UTC+1, Anthony wrote:

[Rob Dawson]

Addition...
The Shoutcast V2 server logs show the stream has a registered  Mime-type. wither or not it actually spits out that info in the stream is unknown to me.

2013-04-30 15:09:11	I	msg:[YP2] Connecting to yp.shoutcast.com
2013-04-30 15:09:11	I	msg:[SRC 127.0.0.1:36331 sid=1] stream configuration complete. [
type=SHOUTcast 2
mimeType=audio/mpeg
maxPayloadSize=16377
avgBitrate=128000
maxBitrate=128000
desiredBufferSize=320
minimumBufferSize=0
icyName=
icyGenre=Drum and Bass
icyURL=http://
icyPub=1

[Rob Dawson]

Ok, I've raised this issue over at winamp/shoutcast,   http://forums.winamp.com/showthread.php?t=360426
and got the following information

it's probably not paying attention to what the stream is providing (though am surprised it's trying to provide a v2 style stream when i'd have really expected a HTML5 player to get a v1 style stream) as it's not getting a main HTTP header instead of the ICY header that it's getting i.e. HTTP/1.1 200 OK vs ICY 200 OK

i remember looking into making streams able to provide a HTTP header instead of a ICY (opt-in via another param) but i don't think i ever got it finished off properly even in the internal builds).

all i can tell from the brief bit of details is jplayer is managing to get at least initially provided a stream from the DNAS. it is however getting a v2 style stream and not a v1 style stream - that can only happen if the client requesting it has added some specific values to it's user-agent (which it may be doing incorrectly unless they do support v2 style streams and then i don't know at all).

the default from the v2 DNAS is a v1 style stream if it is in doubt so jplayer seems to be setting what is needed to be considered a compatible v2 style stream.

so maybe it's jplayer then not being able to cope with the v2 style stream when it expects a v1 style format of the audio data. hence causing it to not play.

then again, the v2 DNAS isn't properly setup to cope with HTML5 players or providing a more compatible HTTP header instead of the age old ICY header so it could also be at fault.

So........where to go from here?

[Mark Panaghiston]

@Rob: Ultimately, all jPlayer does is slap a <audio> element on the page and set the src to the stream url you gave it. So it is the browser that is having the problems.

Firefox is strict with the MIME type (content-type). It is not alone, Internet Explorer 9 and 10 are also strict, as is Opera. The webkit browsers do not appear to care what the Mime type is last time I checked. The strict browsers refuse to play the audio in their native HTML unless the Mime type is valid.

Since Shoutcast does not always give the HTTP header information, as they guy said... It gives the ICY headers. As the guy also said, it is due to the user agent, which jPlayer has no control over... I believe you can frig your own user agent if you want to, but that is in the browser setting and you cannot frig it on the web page... (Least I assume you can't as it very probably a security issue.)

Anywayz.. all i wanted to say was that the HTML player just uses an audio element and does not do anything fancy with it... Yes, it does a lot of stuff with the media API to see what is supported and handles the GUI with the events and so on, but the browser deals with the audio element and how it requests the media and whether it rejects it or not.

[Rob Dawson]

Ah, Ok, cheers for the explanation, I think I understand the situation a little better now,
Situation is due to all server access being on one port I guess (?), so the server knows if to send the stream, or the admin interface depending on what is sending the request to the server... 
Either way, I'll have to do some more digging for a solution.
Thanks Mark.

[Stephen Phillips]

I have had this same problem with my player, it was working fine for the past month playing a shoutcast audio stream, and then for no reason at all it suddenly stopped and started reporting "HTTP "Content-Type" of "text/plain" is not supported. Load of media resource http://xxx.xxx.xxx.xxx:8000/;stream/1" its really weird, I had it working on laptop, ipad and iphone perfectly, changed nothing, updated nothing, and then for no reason at all it just changed to this error message? Confused the hell out of me!

[croconmedia]

Situation is now, that Shoutcast Streams seem to not work any longer with IE 9x+ and Firefox 22+.

Shoutcast is the most used audio stream service by radio stations and DJ's worldwide.

We coded Flash Audio Players that are able to deal with those streams without any problem, that works fine with ICY headers.

Is there any chance to get an update soon for JPlayer to have shoutcast streams working or is the official statement, that the problem isn't JPlayer ?

Thanks in advanc.

[Gino Côté]

May be we can have a option to be played with flash?

I don't know if this could help