Android chrome to chromecast

Search This thread

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
I can only invite you, again, to look at the actual casting API rather than rely on assumptions.

It's NOT the same as that last July and it absolutely, positively does recognize casting DRM content.

Start here -

https://groups.google.com/a/chromium.org/forum/m/#!topic/apps-dev/emlKA4C-c90

And then Google for what's happened since, along with Koush's commentaries.
Well lets see both the link you posted and Koush just today says CCast can do Mirroring....And no Miracast or direct Radio connection required.
So I'm not sure what your getting at here...


Did you even read the article to discover that Samsung is using a superset of DIAL and support by Sony, LG, and Panasonic TV sets is expected?


Yes who owns the DIAL patent and protocol? Samsung? Or Google? Will Samsung add proprietary functionality to their Box? Will current CCast or DIAL compatible products use any of those features?
Is Sony going to have Samsung make those boxes for them or are they just finding a better way to jump onto the DIAL bandwagon without the need for yet another box to plug in?

Still fail to see how any of that has to do with DRM...
 

EarlyMon

Senior Member
Jun 23, 2010
1,685
1,295
Well lets see both the link you posted and Koush just today says CCast can do Mirroring....And no Miracast or direct Radio connection required.
So I'm not sure what your getting at here...

I give up.

https://plus.google.com/app/basic/stream/z12weptwssfqidk5a04ccxsypuevhtcwgao

For those technically inclined, it will be interesting to see how he addresses the issues that he previously identified.

Such as - https://plus.google.com/110558071969009568835/posts/ch57ZKvqpYb - (Warning! DRM discussed there.)

Koush said:
The Android compositor allows you to mirror a display, and leave out any surfaces marked "secure"... it will not mirror any DRM'd surfaces.
http://developer.android.com/reference/android/view/SurfaceView.html#setSecure(boolean)

Ie, you'll see a black screen if you tried to mirror Netflix while only holding the CAPTURE_VIDEO_OUTPUT (vs CAPTURE_SECURE_VIDEO_OUTPUT). This API could have been exposed, and been DRM friendly, but it was not.

I've spent a lot of time in this code, and actually implemented my own variant of the Virtual Display API in 4.2 to get Airplay Mirroring working. My implementation was DRM friendly to boot. Suffice to say, I know what I'm talking about.
https://github.com/CyanogenMod/andr...mmit/858d67d29f30a0256014d7a318b3586db10d0bb0

So, present a legitimate reason why it wasn't made available. Go ahead. I'll wait here.


Yes who owns the DIAL patent and protocol? Samsung? Or Google? Will Samsung add proprietary functionality to their Box? Will current CCast or DIAL compatible products use any of those features?
Is Sony going to have Samsung make those boxes for them or are they just finding a better way to jump onto the DIAL bandwagon without the need for yet another box to plug in?

Still fail to see how any of that has to do with DRM...
The topic is screen mirroring, I mentioned that the Samsung SDK including it for their TVs was announced months ago, and despite the fact that I've linked to an article about a capability for new smart TVs and had to say that in a follow-up post, you still insist that I'm referring to some mystical box.

DIAL ownership has nothing to do with anything, but obviously I had no idea that Google owns the DIAL protocol, Netflix was never involved or you'd have told me, I must have thought that Samsung did because I'm so new here, and anyone making a superset of a protocol, or adding to a Google code base, is doing so for the first time in the history of the world.

Btw, you forgot to mention -

Samsung and Sony were both mentioned in the protocol’s specs. Mirer said that the companies helped a lot with practical feedback:

“Both Sony and Samsung generously invested some effort and their feedback really helped us tighten up the protocol and make it compatible with their existing software. We fully expect them to include DIAL in many of their products going forward.”

http://gigaom.com/2013/01/23/dial-open-airplay-competitor/

Maybe you can ask them about the box you want to insist that I was referring to.

You win, I give up here too.

I'm done playing horse, water, drink and jello, nail, tree with you on anything else to do with Chromecast.

Have a great day! :D
 
Last edited:

bhiga

Inactive Recognized Contributor
Oct 13, 2010
2,501
1,018

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
It's both good and bad from my POV...

Good that they are adding the CCast support but I would much rather see them get the browser to support Chrome Extensions as opposed to hardcoding the features we want (but can't have because you can't load extensions) into it.

I guess Chrome simply can't be VMed over Android.
 

EarlyMon

Senior Member
Jun 23, 2010
1,685
1,295
Right now it's supposedly good with embedded YouTubes but other HTML5 videos are unreliable. vGet doesn't do YouTubes because of TOS violations but it does do most everything else.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Tab casting from Chrome uses the host CPU to re-encode the video and stream it to the Chromecast on-the-fly. Tablet and phone CPUs don't have enough processing power. That's why there's no Chromecast extension for Chrome on your portable device.