Results 1 to 10 of 10
  1. #1
    joint's Avatar
    Title
    Junior Broadcaster
    Join Date
    Nov 2013
    Posts
    52
    Rep Power
    7

    Thumbs up Google Chrome VER 55 is not support shoutcast V1

    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

  2. #2
    johny c's Avatar
    Title
    Senior Broadcaster
    Join Date
    Sep 2008
    Location
    Raglan, New Zealand, New Zealand
    Posts
    1,199
    Rep Power
    39
    Yes you are right , just updated and now the streams stuffed
    Thats a big stuffup by Google.
    Last edited by johny c; 12-12-2016 at 11:19 PM.

    ........"Top Music Top of the Dial"
    Click HERE to listen to my radio stream
    Click HERE for Face Book



  3. #3
    GKIye's Avatar
    Title
    Moderator
    Join Date
    Nov 2008
    Location
    @ home
    Posts
    2,977
    Rep Power
    68
    Is this a valid IP Port ?
    I even can't connect to the stream by using Winamp
    Visit and listen @ BW !



  4. #4
    joint's Avatar
    Title
    Junior Broadcaster
    Join Date
    Nov 2013
    Posts
    52
    Rep Power
    7
    Quote Originally Posted by GKIye View Post
    Is this a valid IP Port ?
    I even can't connect to the stream by using Winamp
    These links are examples...
    Last edited by joint; 12-22-2016 at 10:00 AM.

  5. #5
    johny c's Avatar
    Title
    Senior Broadcaster
    Join Date
    Sep 2008
    Location
    Raglan, New Zealand, New Zealand
    Posts
    1,199
    Rep Power
    39
    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.

    ........"Top Music Top of the Dial"
    Click HERE to listen to my radio stream
    Click HERE for Face Book



  6. #6
    voiceoverwizard's Avatar
    Title
    Imaging Professional
    Join Date
    May 2009
    Location
    St Louis
    Posts
    44
    Rep Power
    10
    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....

  7. #7

  8. #8

    Title
    Junior Broadcaster
    Join Date
    Jul 2014
    Location
    UK
    Posts
    35
    Rep Power
    6
    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...l?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

  9. #9

    Title
    Junior Member
    Join Date
    Jan 2017
    Posts
    1
    Rep Power
    0
    Hello people, I'm having this problem on a shoutcast v2 server. "SHOUTcast Server v2.0.0.29/posix(linux x64)" port 8000, can't play the stream on the last chrome but firefox is playing it with no problem.

  10. #10
    shoutcaststreaming's Avatar
    Title
    Premium Member
    Join Date
    Sep 2008
    Location
    Los Angeles, California
    Posts
    779
    Rep Power
    28
    That's an old version of SHOUTcast version 2. The newest version is 2.4.7.xxx. You should update to the latest version.
    SCS - Dedicated Bandwidth Servers
    Shoutcast / Icecast / Windows Media
    Transcoding - Auto DJ - Mobile Radio - FLASH Players - Auto DJ
    Broadcasting World's Stream Host of the Month

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •