screen sharing is very laggy with bad framerate

[Jacob S]

Hi all, I need some help figuring out why my screen sharing attempts ( using the Video Room plugin  ) are very laggy with bad frame rate, no matter what screenshareFrameRate and bitrate I try.

I am using windows 10 with chrome 60.

I have some experience with the Streaming plugin and with it I get much better framerate and a smoother stream.

is this a problem with webrtc chrome screen capture ? is there any configuration I can try ?

Thanks

[Jacob S]

Looking in chrome://webrtc-internals/ I can see that googFrameRateSent is very low compared to googFrameRateInput.

But when I try to do webrtc peer to peer ( not using janus.js ) , the googFrameRateSent is very high, any idea what could be the difference ?

I also seems that when there is allot of movement the frame rate goes down ( maybe speed encoding issue ? )

[Mirko Brankovic]

on the creation of room you have set the upper limit of bitrate, if not, you got default. Try to increase that.

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janus+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jacob S]

You were correct increasing bitrate very much did fix the framerate, is this because vp8 max-quantization, is the encoder dropping frames in order to meet the minimum quality demands ?

Can this be changed via api ?

To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janu...@googlegroups.com.

[Lorenzo Miniero]

Il giorno lunedì 18 settembre 2017 07:39:44 UTC+2, Jacob S ha scritto:

You were correct increasing bitrate very much did fix the framerate, is this because vp8 max-quantization, is the encoder dropping frames in order to meet the minimum quality demands ?

Can this be changed via api ?

None of those aspects are exposed via JavaScript, and we most definitely can't change anything. We don't do transcoding either, so what you see is what the browser encodes.

L.

[Jacob S]

isn't  x-google-max-quantization the parameter for that ?

[Lorenzo Miniero]

No idea, I never cared much for browser-specific settings, as janus.js is meant to be browser agnostic.

L.

[Mirko Brankovic]

i'm not sure either.

I guess it depends on the constraints that your plugin is sending to getUserMedia() after the chrome.desktopCapture.chooseDesktopMedia() returns the ID.

maxWidth minWidth ,....

But I guess by default Browsers are expecting high resolution for screen share to be able to work properly, high peaking to 3-4 mbps in high screen changes

To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janus+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Regards,

Mirko