New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 804953 link

Starred by 1 user
Status: WontFix
Owner:
█ x...@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Cc:
mfo...@chromium.org
m...@chromium.org
mlamouri@chromium.org
taku...@chromium.org
powerb@chromium.org
tguilbert@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Media Remoting is not starting when it should via fullscreen transition

Project Member Reported by dbbrooks@chromium.org, Jan 23 2018 
Chrome Version: 64.0.3282.99
OS: Win 10
MR: 6417.1211.0.0

Media Remoting worked, then I switched to casting to a new device. Since then, I cannot get Media Remoting to start. I've tried multiple Cast sessions, closed the tab. I haven't restarted Chrome though.


What steps will reproduce the problem?
(1) Play a vimeo.com video (I usually use any video from the music section)
(2) Cast the tab to a Chromecast device and verify the Remoting setting is enabled.
(3) Click on the fullscreen button on the video

What is the expected result? Media Remoting is triggered

What happens instead? Media Remoting doesn't start.


Feedback report: http://feedback/#/Report/84968949334

Comment 1 by dbbrooks@chromium.org, Jan 23 2018 

It looks like this might be expected. Specific videos on Vimeo.com don't start remoting while others do.

These don't:
- https://vimeo.com/251675095
- https://vimeo.com/251215162

This one does:
- https://vimeo.com/250416006

Is this expected?

Comment 2 by mfo...@chromium.org, Jan 23 2018

Owner: x...@chromium.org
Status: Assigned (was: Untriaged)
It may be expected depending on the videos and the target device - they might have multichannel sound, 60 fps, vp9, etc.

When you say "switched the casting to a new device," did you completely stop the Cast session and start on a new device, or did you switch devices mid-session?

Can you show xjz@ and pull up chrome://media-internals to find out the codec/specs of the video segments that won't remote?

Comment 3 by mfo...@chromium.org, Jan 23 2018 

This video (for example) has a 4k stream.

https://vimeo.com/251215162

Comment 4 by x...@chromium.org, Jan 23 2018 

For this video, media remoting wasn't triggered because it wasn't reported as dominant (>85%) in the viewport even when fullscreen button was clicked.

https://vimeo.com/251675095

Comment 5 by mfo...@chromium.org, Jan 23 2018 

If we don't account for letterboxing/pillarboxing in the "dominance" calculation we will never remote fullscreen 9:16, 4:3, 3:4 etc video on 16:9 displays, which doesn't seem right.

Comment 6 by dbbrooks@chromium.org, Jan 23 2018 

Maybe we can change the title to reflect focusing on comment #5? I don't think it had anything to do with how I was casting or switching tabs as Xianjun mentioned the reasons for not remoting the specific videos I referenced.

Comment 7 by x...@chromium.org, Jan 23 2018 

The "dominant" calculation seems need to be changed. Opened a new bug to track this issue: crbug.com/805094.

Comment 8 by x...@chromium.org, Jan 23 2018

Status: WontFix (was: Assigned)
►

Sign in to add a comment