chrome screensharing very bad quality

[Gabriel T]

Hello
since a recent update (sorry i cant tell you which), the screensharing (which was working perfectly with the recent extension update) is now of very bad quality. My first though was it was related to my bandwidth, but if using FF the quality is perfect like before.
did somebody noticed the same behavior ?
using windows 10, 1920*1080, chrome 66
here is my js for publishing:

Spoiler: js

var constraints = {
audio: false,
video: {
width: parseInt(window.screen.width),
height: parseInt(window.screen.height),
maxWidth: parseInt(window.screen.width),
maxHeight: parseInt(window.screen.height),
frameRate: parseInt(5),
type: "screen"
}
};

thanks !

 

[Max]

Hello
H.264 codec is used by default.
Try VP8

You can either configure VP8 for client-side and for particular stream.
Or configure for server-side for all streams.

1. On client side.
Add option stripCodecs
https://github.com/flashphoner/flashphoner_client/blob/wcs_api-2.0/src/flashphoner-core.js#L1245
Example:

session.createStream({name:"stream1",stripCodecs:"h264,H264"});

2. On server side in flashphoner.properties

codecs=opus,alaw,ulaw,g729,speex16,g722,mpeg4-generic,telephone-event,vp8,h264,flv,mpv

 

[Gabriel T]

okay, swithching to vp8 server side solved the pb. many thanks !

 

[Gabriel T]

ha, but if i use stripcodec i have the following error:

Spoiler: error log

07:50:54,189 ERROR MediaHandler - API-ASYNC-pool-23-thread-6 publishStream exception
com.flashphoner.media.J.A: No codecs found
at com.flashphoner.server.client.handler.wcs4.media.MediaHandlerUtils.setRemoteSDP(Unknown Source)
at com.flashphoner.server.client.handler.wcs4.media.MediaHandlerUtils.createMediaSession(Unknown Source)
at com.flashphoner.server.client.handler.wcs4.media.MediaHandler.publishStream(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.flashphoner.server.client.handler.HandlerUtils.lambda$processThroughREST$0(Unknown Source)
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

[Gabriel T]

by the way there are still endless flow of errors in the logs when sharing screen (from chrome latest version at least):

Spoiler: logs

10:56:36,667 WARN ControlPacket - RTP-pool-28-thread-15 Rtcp innerBlocks - 00; type not found - cf
10:56:36,667 ERROR ControlPacketDecoder - RTP-pool-28-thread-15 Failed to decode control packet

 

[Max]

ha, but if i use stripcodec i have the following error

Reproduced. Thanks.
We have issued case WCS-1229 related stripCodecs option.
We will inform once we have any progress on this task.

 

[Max]

by the way there are still endless flow of errors in the logs when sharing screen (from chrome latest version at least):

It was reproduced too. Internal case WCS-1206. Will let you know once we have any progress here.

 

[Max]

WCS-1206 issue (redundant messages in server log when sharing screen) has been fixed in WCS v. 5.2.586.