Results 1 to 4 of 4
  1. #1
    shoutcaststreaming's Avatar
    Title
    Premium Member
    Join Date
    Sep 2008
    Location
    Los Angeles, California
    Posts
    782
    Rep Power
    28

    CHROME to allow SHOUTcast v1

    After tens of thousands of complaints to Google, they are finally relenting and will allow SHOUTcast v1 to function once again.

    https://bugs.chromium.org/p/chromium...id=669800#c103
    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

  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
    All I can say is what a bunch of pricks at google.
    Now they do this after many of us have gone to the trouble to change our streams over to Shoutcast ver2.
    I bet Im not the only one whos unhappy about them wasting our time.
    I for one will never use google chrome again and would never advise people to use it.

    ........"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,996
    Rep Power
    68
    So true Johny !

    I made even a topic about it :
    http://forums.broadcastingworld.com/...-Listeners-etc
    Quote Originally Posted by johny c View Post
    All I can say is what a bunch of pricks at google.
    Now they do this after many of us have gone to the trouble to change our streams over to Shoutcast ver2.
    I bet Im not the only one whos unhappy about them wasting our time.
    I for one will never use google chrome again and would never advise people to use it.
    Visit and listen @ BW !



  4. #4

    Title
    Junior Broadcaster
    Join Date
    Jul 2014
    Location
    UK
    Posts
    35
    Rep Power
    6
    So they're temporarily re-enabling the code that was disabled / removed as a stop gap for one formal release, then removing that again in the next formal release but adding in a checking hack to allow things to work after the reversion of the reversion. Them dropping a legacy HTTP method makes sense and as the v1 DNAS uses a non-standard format (HTTP-like) then it's no wonder that anything based on Chrome was being treated as the oldest format and so this was just an issue that was waiting to arise.

    I fully get that most people only want to use the v1 DNAS but having that end up leading to compatibility hacks within browsers to allow the streams to work is just bonkers imho.

    I also know that v2 DNAS is a pain to setup (due to the authhash / account sign-up aspects now enforced by the current owners - though signing-up for other services is deemed fine so I've never understood the dual standards) but I'd rather just run v2.4.7 in private mode (that way the current owners can't do anything to you) and register the stream directly with other relevant Directory services as needed (there's no point in using the SHOUTcast Directory due to the irrelevance of it as there's no way there is a legitimate 70k+ listings).

    If anything I'm more surprised that there wasn't just a bigger shift over to using Icecast / alternatives (as has been the general trend over the last few years).

    Anyhoo, just my 2p worth
    -dro

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
  •