Several issues found in Desktop Capture during Screen Sharing

[Qiusheng Jiang]

I am using chrome.desktopCapture.chooseDesktopMedia API in my Chrome App.

Here are several issues:

1, Not able to select which screen to be shared if user has multiple monitors.

When select option "screen", it is a video with all screens merged.

Do you have any plan to enhance this API to allow the user to choose which screen to share?

2, Chrome looses the track when captured Window is minimized.

Presenter selects a window to be shared and he is able to move the window around without interrupting the sharing.

But if the presenter minimizes the window then restore it, Chrome can't capture that window any more. The video stops at the last picture before it's minimized.

3, The captured video stays at its original resolution, regardless user resizes the window.

Presenter selects a window to be shared. In case the window size was originally very small, let's say 320*240, the video's resolution is set to 320*240.

Later the presenter increase the window size to be like 1280*800, the video's resolution is still at 320*240.

Vice versa, if the window size was originally very large (1920*1200) at the time it's be picked, the video's resolution keeps the same size even though the window size is decreased. It's wasting resources.

I tried to pass in the media constraints but without any luck.

                constraints.video = {

                    mandatory: {

                        chromeMediaSource: "desktop",

                        chromeMediaSourceId: id,

                        maxWidth: 1920,

                        maxHeight: 1200,

                        minWidth: 640,   // min settings have no effect

                        minHeight: 480

                    }

                };

Please let me know if I am missing something, or you are planning to fix them. Thanks!

[Vikas]

some answers inline 

On Thursday, October 17, 2013 2:21:36 PM UTC-7, Qiusheng Jiang wrote:

I am using chrome.desktopCapture.chooseDesktopMedia API in my Chrome App.

Here are several issues:

1, Not able to select which screen to be shared if user has multiple monitors.

When select option "screen", it is a video with all screens merged.

Do you have any plan to enhance this API to allow the user to choose which screen to share?

Thanks for feedback, not sure if there is an existing issue on this, but you can file in chromium tracker with appropriate details. 

2, Chrome looses the track when captured Window is minimized.

Presenter selects a window to be shared and he is able to move the window around without interrupting the sharing.

But if the presenter minimizes the window then restore it, Chrome can't capture that window any more. The video stops at the last picture before it's minimized.

I think this is similar to http://crbug.com/288205, what version you tested with, have you tried in chrome dev or canary?

3, The captured video stays at its original resolution, regardless user resizes the window.

Presenter selects a window to be shared. In case the window size was originally very small, let's say 320*240, the video's resolution is set to 320*240.

Later the presenter increase the window size to be like 1280*800, the video's resolution is still at 320*240.

Vice versa, if the window size was originally very large (1920*1200) at the time it's be picked, the video's resolution keeps the same size even though the window size is decreased. It's wasting resources.

This might be similar to http://crbug.com/289759 though the description of bug doesn't make that apparent. Have you tried testing in chrome dev or canary? If it still doesn't work, maybe post with details to the associated bugs.

[Qiusheng Jiang]

I have Version 32.0.1671.4 dev-m Aura SyzyASan (latest today), and none of the 3 issues are fixed.

I also installed today's (10/18/2013) Canary build, and it can't open any page. Is this issue already reported?

[Qiusheng Jiang]

The canary build is fixed now and I've also tested on this build: Version 32.0.1671.4 dev-m Aura SyzyASan

The 3 issues are still there.

On Thursday, October 17, 2013 8:32:07 PM UTC-4, Vikas wrote:

[Vikas]

Hi,

Thanks for the feedback, it would be good to add your test results to the issues. 

/Vikas

[Qiusheng Jiang]

I have opened new issues since the one you mentioned is closed.

#1: https://code.google.com/p/chromium/issues/detail?id=309025

#2 & #3: https://code.google.com/p/chromium/issues/detail?id=309129