Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: RDZ on December 16, 2016, 03:21:06 am

Title: Stream do not function with Chrome v.55
Post by: RDZ on December 16, 2016, 03:21:06 am

Hi, in panel control of http://dreamsiteradiocp3.com:2199/login/index.php is not possible listen music with Chrome v.55 (and v.56 and v.57).
This problem is also on my website, as streaming seems it does not run with this chrome update, V.55 and later.
How can you fix?

Title: Re: Stream do not function with Chrome v.55
Post by: DrO on December 16, 2016, 05:16:00 am

It's due to a change that Chrome made in v55 which affects using the 1.x DNAS.

This post details a bit more about the reason why and which DNAS versions are affected, etc - http://forums.broadcastingworld.com/showthread.php?15313-Google-Chrome-VER-55-is-not-support-shoutcast-V1&p=95634&viewfull=1#post95634

-dro

Title: Re: Stream do not function with Chrome v.55
Post by: RDZ on December 16, 2016, 06:00:48 am

Ok, but is possible update server to SHOUTcast v.2 so as to avoid the problem?

Title: Re: Stream do not function with Chrome v.55
Post by: Roger on December 16, 2016, 01:33:54 pm

Quote from: RDZ on December 16, 2016, 06:00:48 am

Ok, but is possible update server to SHOUTcast v.2 so as to avoid the problem?

Not automatically I'm afraid, you would need to delete your current station and create a new one.

An alternative is to enable Centova Cast's port 80 proxy.

http://www.centova.com/en/faq/cast3/information/does_centova_cast_include_a_proxy_for_streaming_on_port_80

Title: Re: Stream do not function with Chrome v.55
Post by: Mr_NightRyder on January 13, 2017, 06:58:05 am

@Roger this really isn't an acceptable option as not all of us a port 80 proxy is a viable option.  Please see the patched version of shoutcast: http://saynotolinux.com/shoutcast/ it was posted on the chromium update here @ https://bugs.chromium.org/p/chromium/issues/detail?id=669800

Title: Re: Stream do not function with Chrome v.55
Post by: DrO on January 13, 2017, 09:08:02 am

You could also say that hacking up an old DNAS binary isn't an acceptable option either seeing as it was clear under AOL (and then post sale) that v1 support was / had ended respectively and if things broke, the only options were to either move to v2 (yes I know all of the reasons why people won't - not helped by the current owners handling of things with v2.5+ that annoy me).

I get why people want to keep using v1 (despite it having these issues and not working nicely with HTML5, etc, etc) but such patching which should only be a temporary measure are unlikely to be viewed as that by those resolute  on only ever using v1 (not helped that there's more than enough hacked v1 DNAS instances already out there before all of this).

Anyhoo, that's just my thoughts on the matter so probably best ignored :)

-dro