We have provided the constraints we used, but those constraints work for the implementation of the getScreenConstraints function that we have, as indicated here. There is no information about the implementation of that function, or how the extension that the applicant is using is working. For that reason, it was indicated that the constraints that are being used should be checked in the call to adapter.js

Once again, the constraints that we are using in Chrome are

"{
  "audio":false,
  "video":{
    "mandatory": { 
      "chromeMediaSource":"desktop",
      "chromeMediaSourceId":"p15ar+Gm/05Q7JnilMEPCQ==",
      "maxHeight":1080,
      "maxWidth":1920,
      "maxFrameRate":10
    },
    "optional":[]
  }
}"

Remember to provide the appropriate values as needed.

These constraints are only valid for Chrome, as FF adheres to the W3c standard. The function getScreenConstraints is in charge of providing one set of constraints or the other. That function must be implemented by the applicant.

Please note that this is not particular to Kurento, but to getUserMedia.

Dear accelerator,
can you check with the applicant, please?
BR

Comment by amaestrini@create-net.org :

Dear,
I forward you an update from the applicant:

*************************
File attached.

For some reason the height is 480:

Caller origin: https://test.uxpro.be
Caller process id: 10924
Audio Constraints
Video Constraints {width:

, deviceId:

, mediaStreamSource: {exact: ["desktop"]}}

cname:pVzbrHdEzhEyyC7H
msid:liRBAIjtsWwNF3cnXaEwbpVppNqXNYcxhsJr
0fdde59b-a4b8-4fbd-8a72-b1b7a28526d0
mslabel:liRBAIjtsWwNF3cnXaEwbpVppNqXNYcxhsJr
label:0fdde59b-a4b8-4fbd-8a72-b1b7a28526d0
timestamp 9/13/2016, 8:33:31 PM
bytesSent 12456436
codecImplementationName libvpx
mediaType video
packetsLost 0
packetsSent 12876
ssrc 145731705
transportId Channel-video-1
googAdaptationChanges 0
googAvgEncodeMs 2
googBandwidthLimitedResolution false
googCodecName VP8
googCpuLimitedResolution false
googEncodeUsagePercent 5
googFirsReceived 3
googFrameHeightInput 480
googFrameHeightSent 480
googFrameRateInput 20
googFrameRateSent 20
googFrameWidthInput 768
googFrameWidthSent 768
googNacksReceived 3
googPlisReceived 0
googRtt 24
googTrackId 0fdde59b-a4b8-4fbd-8a72-b1b7a28526d0
googViewLimitedResolution false

*************************

On Tue, Sep 13, 2016 at 4:29 PM, Help-Coaches-Desk <
coaches-help-desk-jira@fi-ware.org> wrote:

>
>

Dear expert,
I forwarded your reply to the applicant
BR

Resolution of the screen share stream is completely dependant on PeerConnection constraints within the browser. Kurento Media Server is just receiving whatever is sent by browser with no capacity to affect frame size.

Please, perform a test using provided constraints and report back the WebRTC internals in PDF format.