PDA

View Full Version : Google Chrome VER 55 is not support shoutcast V1



joint
12-12-2016, 09:56 AM
All radio station who use Shoutcast server V1
Are not supported Google Chrome VER 55

That is all the formats of these streams do not work from now

for example:
http://192.168.1.1:9986/;stream.mp3
http://192.168.1.1:9986/;stream/1
http://192.168.1.1:9986/;

FireFox & Microsoft Edge There is no problem with them

Shai

johny c
12-12-2016, 09:16 PM
Yes you are right , just updated and now the streams stuffed
Thats a big stuffup by Google.

GKIye
12-14-2016, 03:17 AM
Is this a valid IP Port ?
I even can't connect to the stream by using Winamp


http://192.168.1.1:9986/;stream.mp3
http://192.168.1.1:9986/;stream/1
http://192.168.1.1:9986/;

joint
12-14-2016, 05:59 AM
Is this a valid IP Port ?
I even can't connect to the stream by using Winamp

These links are examples...

johny c
12-14-2016, 06:30 PM
Even your Listen live links will not work in the the new Chrome ver 55 update Philippe, I checked mine in Broadcasting World, Tunein and Shoutcast and the streams dont play. On the Google Chrome site they have now listed this is a bug.

voiceoverwizard
12-15-2016, 01:15 AM
I've had to use the M3U to listen via Windows Media Player....
Who'd have thunk there'd be a day when Microsoft would save the day from Google....

joint
12-15-2016, 05:54 AM
For more info:

https://productforums.google.com/forum/#!topic/chrome/bhjjSbjfN50

DrO
12-15-2016, 11:10 PM
Reading through things, hopefully some of what I'm about to post will be helpful...


The key problem is that the 1.x (and 2.0x) DNAS don't provide a true HTTP response (it's HTTP-like but is prefixed with ICY instead of HTTP) and the change that Chrome has made means that those 'ICY' responses now fail to be handled as an older HTTP version (0.9 in this case).


Looking at the https://bugs.chromium.org/p/chromium/issues/detail?id=669800#c6 some have either hex-edited the DNAS (which could cause issues if you don't trust the source of the 1.x DNAS - not that that's mattered too much with hacked versions floating around for years)
or
you can apply the Chrome tweak for Http09OnNonDefaultPortsEnabled but that itself may cause issues and is client dependent (which isn't the best solution going).


The 2.4x and newer DNAS shouldn't be affected as I'd changed them to send the HTTP identifier instead of the ICY identifier (which was needed anyway to improve HTML5 playback).


The 2.2x DNAS requires the icy=http parameter on the listener request url to have the HTTP compatible version provided.


For any other DNAS version (1.x or 2.0x), it's basically either try to edit the binary or use a different solution if moving to the 2.x DNAS isn't an option (bites tongue) or see if Chrome will do like Firefox, etc do and just automatically treat anything identified as ICY as HTTP (which tbh would be reasonable option due to the impact that this otherwise sensible change has caused).

-dro

kuato
01-01-2017, 02:24 PM
Hello people, I'm having this problem on a shoutcast v2 server. "SHOUTcast Server v2.0.0.29/posix(linux x64) (http://www.shoutcast.com/)" port 8000, can't play the stream on the last chrome but firefox is playing it with no problem.

shoutcaststreaming
01-01-2017, 03:38 PM
That's an old version of SHOUTcast version 2. The newest version is 2.4.7.xxx. You should update to the latest version.