[Crito]

I believe there is something more nuanced going on with Chromecast "casting" performance.

Netflix is fast obviously because you are just telling the chromecast to stream netflix itself, not "casting" it to chromecast. Same goes with youtube.

However "casting" performance for me is even worse than the described .3fps on my Chromebook Pixel that isn't running ChromeOS. And my LAN is fast enough to use mplayer over ssh/x-forwarding... Trying chrome tab casting in Debian on a Chromebook Pixel burns the Pixel up, with it being very obvious that the Pixel is the bottleneck.

Trying to video encode the "cast" tab without using hardware support maybe? I'm not sure, I haven't really investigated it further.

[nkozyra]

I find the critique confusing, too, because I streamed a 1080p movie to my Chromecast by dragging it into Chrome and then casting from Chrome itself.

No problems. It played fine.

[Crito]

Is Chrome actually decoding the file then reencoding it / pushing raw video frames, or is it just streaming the file to the Chromecast? I suspect the later.

Maybe I'll try that myself later.

[Crito]

Tried it myself. Chrome plays the video fine itself. Trying to cast that tab to Chromecast has the CPU usage on the casting computer spike way up. This is not a network bandwidth issue.

Incidentally I've just discovered that my Roku can have local videos streamed to it from my S3. It works flawlessly.