|
|
Yes, the sample file is H264 (avc1), 1280x720 (16:9), 29 fps that Chromecast 1st and 2nd Gen. cannot play (supports only H.264 High Profile up to level 4.2 (1080p/60fps), but e.g. Chromecast with Google TV can play it (supports H.264 High Profile up to level 5.1 (4Kx2K/30fps) So we would really need to adjust the default auto-convert profiles per Google Cast device type, currently we use generic profile for all Google cast devices -- that can be customized by user manually then (per the device type) via the 'gear' button associated with player output. For 5.0: I fixed a delay (when the file to be played is unsupported) in build 2333 (reduced from 15 seconds to just several seconds) |
|
|
Another (and more universal) approach would be fallback to auto-convertion whenever we found that particular file is unsupported. |
|
|
The fallback is implemented in 2334 Tested on the Rusty's sample file and Chromecast v2 |
|
|
Tested 2334 and there are several issues: 1) The original restrepo file plays locally but always fails to play via the chromecast. This occurs whether the codec pack is installed or not! 2) The smurfs file plays locally and plays to the chromecast if the codec pack isn't installed, but fails to play to the chromecast (can't decode error) when the codec pack is installed! 3) The captain america file plays locally and sometimes plays to the chromecast, but sometimes returns an error (can't decode) even as it's playing on the chromecast! |
|
|
On further testing, there may be 2 issues here: 1) The Restrepo file is being converted to the wrong format for some reason (Ludek indicated that it's being sent to .avi despite the webm auto-conversion rule) 2) Initially, both Smurfs and Captain America cast correctly. But whenever there's an attempt to cast Restrepo, not only is there a decoding error, but the vhelper process _remains open_ consuming 45% of CPU horsepower even after the decoding error. Worse, each subsequent attempt to play Restrepo opens an additional vhelper process that fails to close, sometimes triggering a thermal shutdown! |
|
|
Here's the associated auto-conversion rule. auto-conversion_rule.png (30,542 bytes) |
|
|
Fixed in build 2335 |
|
|
Verified 2335: Tested the original usecase along with manual conversion to AVI. |
- Anonymous
