Linked by Thom Holwerda on Mon 26th Aug 2013 16:24 UTC

Update: the functionality used by the application was reverse engineered and Google stated that it may change. Google has released a statement which acknowledges that playing local content will come back to ChromeCast once the API has stabilised. Storm in a teacup, apparently.

Heads up. Google's latest Chromecast update intentionally breaks AllCast. They disabled 'video_playback' support from the ChromeCast application.

Given that this is the second time they've purposefully removed/disabled[1] the ability to play media from external sources, it confirms some of my suspicions that I have had about the Chromecast developer program: the policy seems to be a heavy handed approach, where only approved content will be played through the device.

A company intentionally disabling cool stuff? Surely you jest.

Permalink for comment 570705
To read all comments associated with this story, please click here.
RE: The point?
by Neolander on Tue 27th Aug 2013 09:22 UTC in reply to "The point?"
Member since:

I never quite understood why people are suddenly so ecstatic over this Chromecast-thing. I mean, DLNA already allows for local streaming of content and the only thing Chromecast seems to bring to the table is allowing the user to make the thing play things from the Web, too. Is there something else? Wouldn't it be more-or-less the same thing if you just bought one of the cheap Android- or Linux-based sticks and wrote a Firefox-plugin that allows for remote-control of it?

Since DLNA-capable TVs are still relatively rare, I think Chromecast's main purpose could be to make your average TV capable of wireless streaming, which would be an interesting feat in itself.

However, it also seems Google chose to go the NIH route and come up with yet another new streaming protocol for the Chromecast, which is not so nice. Can someone more familiar with the issue confirm this ?

Edited 2013-08-27 09:30 UTC

Reply Parent Score: 3