Search results

Добрый день Локальное видео и не будет ухудшаться. WebRTC - протокол, предусматривающий адаптацию публикации под канал. Допустим, Вы публикуете поток 80x60 30 fps H264 видео + 48 кГц Opus аудио. При этом битрейт видео будет в среднем около 70 кбит/с, при движениях в кадре до 100-200 кбит/с...

This option. In the all SDKs you should: - to get a stream status after subscribing to the stream: handle STREAM_STATUS.PLAYING event and get state using Stream.getAudioState(), Stream.getVideoState(); - to get the stream status when publishing client calls muteAudio or muteVideo, use...

They should fix it if you provide them a steps to reproduce with well-known examples (AppRTC, TrickleICE). You can recommend your customers to use Firefox on such device until Samsung will fix the issue.

Hello Server is up and running. Default example operates correctly. https://cibunet.com:8444/client2/examples/demo/streaming/two_way_streaming/two_way_streaming.html If you want we test your application, please send step-by-step instructions including screenshots and all the details and...

Good day. You need to re-establish Websocket connection to a new URL, so the previous session must be closed.

PLease also check with AppRTC. If the problem is reproducing using this test, please contact Samsung support about it. The codec used does not matter, the STUN connection is not established using correct address and port. You can also try to switch to TCP transport (use the Media Devices...

We checked the stream in the dump provided. VLC cannot play this stream: displaying only one frame in the beginning and one frame in the end of the stream. Please check if the stream is playing correctly in VLC. If yes, and there are no errors in VLC log, please collect a traffic dump on VLC...

This will be fixed in ticket WCS-3275 as we wrote above. This will be fixed in ticket WCS-3266.

We added logging on StreamEvent receiving both to SDK and samples in build 2.6.55. And you're right: StreamEvent is not fired when subscriber connects to the stream. In this case, stream status can be received in StreamStatusPlaying event handler using Stream.getAudioState() and...

Добрый день. Это известная проблема, по краш логам (файлы errorPID.log) виден краш в нативной библиотеке декодера. Проблема была исправлена в сборке 5.2.969, рекомендуем обновить сервер до нее или до последней сборки 5.2.1002.

We checked your report. Seems like your device does not send STUN Binding Request at all while the problem is reproducing. We see STUN traffic for successful WebRTC connection only in the dump provided. Also you said that the problem is reproducing with Samsung browser only, but according to the...

Please make sure you've updated the license key. Also note that expiry date may be displayed incorrectly for subscription license. Sales department will respond you today.

Good day. Please reproduce a problem, collect a report as described here and send using this form

Good day. We suppose m5.24xlarge or m5.metal for this high load task. But we recommend you to perform load tests before moving to production. Please read this article about stress testing. Please also note that 6 patricipants video chat requires a good client channel and a capable client...

Hello, The issue has been fixed in WCS build 5.2.1002.

Добрый день. Для того, чтобы сессии при тестировании не закрывались преждевременно, нужно на обоих серверах, тестируемом и тестирующем, добавить эту настройку wcs_activity_timer_timeout=86400000 Это отмечено, например, в статье по нагрузочному тестированию, а также в документации (речь идет про...

Good day. uuid developer strongly recommends to update, so other customers requested this. So we raised the ticket WCS-3274 to change export syntax (and to check if this break anything else). As workaround, you can change it yourself locally from module.exports = { connect: appSession...

We raised the tickect WCS-3273 to implement this. Will let you know here. As workaround, you can wrap every stream operation (publish/play/stop) in try/catch to catch this exception, because all the actions requires Websocket messaging, so this exception can be thrown everywhere.

Несколько тысяч входящих потоков - это очень много. Если битрейт одного потока 1 Мегабит/сек (640x360 - 800x450 стрим с учетом возможного разброса битрейта), то несколько тысяч входящих потоков - это несколько гигабит в секунду. При этом, полоса до сервера должна быть гарантирована, иначе стримы...

В нашей реализации Websocket (сообщения) никак не связан с WebRTC (стриминг видео), в плане синхронизации. Поэтому да, если WebRTC будет работать по протоколу UDP с минимальной задержкой, то Websocket сессии могут отставать друг от друга при передаче сообщений. Поэтому зрители должны знать...