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 570714
To read all comments associated with this story, please click here.
RE: The point?
by mistersoft on Tue 27th Aug 2013 11:57 UTC in reply to "The point?"
Member since:

or, if you can stomach approx double the cost of a chromecast stick, then just use twonkybeam with a WD TV Live or similar

and you don't even need to write the browser plugin.
Think they stopped developing the actual Twonkybeam browser plugin (but you can probably still find it somewhere)
or there's the iOS and android apps.

Reply Parent Score: 2