Search results

Good day. Please try to reproduce it with the default full screen desktop layout mixer_video_desktop_fullscreen=true and with the sample custom full screen layout. If the flickering is not reproduced, seems like this is your custom layout implementation issue, so review the code.

Good day. Seems like Firefox still can't publish a stream with aspect ratio 1:1, it even ignores aspectRatio: 1 constraint. So use Chrome to publish a square stream.

Yes, the clientBrowserVersion is used to detect a browser and then use a proper DTLS. That's because WCS initiates DTLS handshake, not browser (WCS sends Client hello), threfore the only way to predict a DTLS version supported is browser version. So you should keep this field untouch in backend...

Good day. Since build 5.2.1440, MKV container is supported for multiple stream recording. Please see details here: Multiple stream recording to one file with subsequent mixing

Good day. Seems like in failure case WCS waits for certificate chain from publisher, but does not receive it (missing a Server Hello packet). Please try to switch to TCP transport to prevent a packets loss. You can also collect a traffic dump and check if DTLS flow is correct: DTLS traffic

Добрый день. Пока что эта функция в iOS SDK не поддерживается. Создали тикет WCS-3614, отпишем по прогрессу.

Try to enable Multithreaded encoding while mixing multiple stream recordings by adding to /usr/local/FlashphonerWebCallServer/conf/offline_mixer.json file the following parameter: "multithreading": true This should make encoding a twice faster.

Good day. That's the bottleneck. One mixer requires 2 CPU cores (with default settings), so you should use at least 8 CPU / 16 Gb RAM.

VP8 codec is supported by all the modern browsers and OSes, so it can be played without transcoding. But you will need VP8 to H264 transcoding if you're republishing VP8 stream to a third party RTMP server or playing the stream as RTMP from WCS (because RTMP supports only H264) or if you're...

We raised the ticket WCS-3613 to investigate the issue. But it may take a time, we'll inform you about progress. A possible workarounds: 1. Do not use 320x240 resolution in Firefox (for example, use 320x180 if it works) 2. Or use VP8 codec You can also try to enable a strict jitter buffer to...

Received the dump, waiting for your feedback about the settings.

You can reduce websocket unanswered pings count: keep_alive.probes=1 In this case, WCS should detect a network disconnection after 10 seconds. note that it can get a false positive on unstable networks.

We checked the report. Unfortunately, it contains no traffic dump, so we can't reproduce the issue on our test servers, we only can to analyze the logs. Seems like Firefox does not send key frames while publishing 320x240. Please enable periodic key frame request in server settings...

Seems like you're using software encoder for H264 (see 1 at your screenshot). In this case, you shoul set ultrafast preset (2) to prevent B-frames in published stream What resolution do you publish (Video tab in Settings dialog)? You should adjust server settings as shown here Server...

Good day. No, all the participants are equal Please see the Conference example source code on GitHub. A maximum participants number is defined in conference.html file: <script>var _participants = 3</script> Then, the current participant number is checked on ROOM_EVENT.STATE event...

Good day. This may be a publisher or player channel issue, or keyframe issue. Please clarify how do you publish a stream? What resolution and bitrate do you use? Set the keyframe interval as we recommended in this post. Try to check publish/playback channel quality: Publisher and player channel...

Usually Javascript code has no access to a hardware layer in browser. So we can't detect a error if the browser does not raise an exception. Please collect a report as described here including client debug logs and traffic dump (both are mandatory). The traffic dump collection must be started...

Seems like this is a hardware issue. Please check Bitrate value in publishers statistics at left: If this is 0, it means the browser does not send media traffic at all. So disabling hardware acceleration in Firefox should help. Clean Use hardware acceleration checkbox and restart browser Or...

Hello We have updated demo server to Web SDK v.2.0.223 and WCS 5.2.1431 https://demo.flashphoner.com Issue seems not reproduced with Firefox 105.0.2 Ubuntu 22. Could you check from your end on our demo server? If it works on our demo server but does not work on your, please send...

You can try network interfaces bonding https://www.tecmint.com/configure-network-bonding-teaming-in-ubuntu/. In this case, WCS will see two interfaces as one. But the channels may be bottleneck.