joint Posted December 12, 2016 Share Posted December 12, 2016 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 Joint Radio www.jointil.com | Get Our Joint Radio Apps | Visit Our Facebook Page Link to comment Share on other sites More sharing options...
johny c Posted December 12, 2016 Share Posted December 12, 2016 (edited) Yes you are right , just updated and now the streams stuffed Thats a big stuffup by Google. Edited December 12, 2016 by johny c RAG-FM 107.7 Raglan New Zealand & ragfm.com ........"Top Music Top of the Dial" Click HERE to listen to the RAG-FM radio stream Link to comment Share on other sites More sharing options...
GKIye Posted December 14, 2016 Share Posted December 14, 2016 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/; Visit and listen @ BW ! Link to comment Share on other sites More sharing options...
joint Posted December 14, 2016 Author Share Posted December 14, 2016 (edited) Is this a valid IP Port ? I even can't connect to the stream by using Winamp These links are examples... Edited December 22, 2016 by joint Joint Radio www.jointil.com | Get Our Joint Radio Apps | Visit Our Facebook Page Link to comment Share on other sites More sharing options...
johny c Posted December 14, 2016 Share Posted December 14, 2016 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. RAG-FM 107.7 Raglan New Zealand & ragfm.com ........"Top Music Top of the Dial" Click HERE to listen to the RAG-FM radio stream Link to comment Share on other sites More sharing options...
voiceoverwizard Posted December 15, 2016 Share Posted December 15, 2016 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.... http://vowizard.com/ http://seanwisner.com/ http://cheapvoiceguy.com/ http://radioimagingwizard.com/ http://cheapradioimaging.com/ Link to comment Share on other sites More sharing options...
joint Posted December 15, 2016 Author Share Posted December 15, 2016 For more info: https://productforums.google.com/forum/#!topic/chrome/bhjjSbjfN50 Joint Radio www.jointil.com | Get Our Joint Radio Apps | Visit Our Facebook Page Link to comment Share on other sites More sharing options...
DrO Posted December 16, 2016 Share Posted December 16, 2016 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 1 Link to comment Share on other sites More sharing options...
kuato Posted January 1, 2017 Share Posted January 1, 2017 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. Link to comment Share on other sites More sharing options...
shoutcaststreaming Posted January 1, 2017 Share Posted January 1, 2017 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 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now