Search results

Probably, no. Headless Chrome does not use GPU, so transcoding will require a lot of client CPU. Also, canvas streaming requires a browser tab where canvas is rendering to be an active tab. So headless Chrome seems not a good solution for the case.

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

Good day. Please read the following doc about canvas streaming: From an HTML5 Canvas element (whiteboard) in a browser via WebRTC This is also step by step guide in this article About headless Chrome: we used it for load testing purposes only, please read here for details

Good day. WCS supports only one video track and one audio track in a stream. So you should use stream mixer at server side to mix all the needed tracks. Please also clarify your case: are the streams you want to mix published from different sources?

Good day. No, WCS is not affected. Please read details here: CVE-2021-44228 vulnerability Anyway, we working on update log4j to 2.15.0 in ticket WCS-2521.

Проблема исправлена в сборке 5.2.1113.

With AWS S3, you can use only URIs like vod-live://s3/cloud-storage-records/sintel.mp4. Full HTTP URIs works with S3 compatible storages only (Digital Ocean Spaces for example) So make sure you have an S3 bucket cloud-storage-records in your S3 storage. Make sure the file is compatilbe with...

Hello MPEG2 is not currently supported. We are working on MPEG-TS and SRT protocols now. Regarding MPEG2 and VLC. If you send a public URL like described above, we will be able to check this URLs and test with VLC to adjust our roadmap related MPEG2, MPEG-TS. The private form for sending URL

Transcoding means server-side transcoding and rescaling For example initial canvas size is 320x240 will be decoded on the server then upscaled to 1920x1080 then encoded to H.264 stream. 1. You will get blurry 1920x1080 image because upscale will affect image quality. 2. You will utilize 1-2...

You cannot use HTTP URL in VOD URI directly. Please read this doc: VOD capturing from AWS S3 or from other S3 compatible storage

Good day. This is a browser limit: a stream picture size published from canvas may only be equal or less than canvas element size on the page. So, to publish 1080p from canvas you need to place canvas element of 1920x1080 pixels to the web page. Another option is to transcode the stream picture...

Good day. There is no WCS builds for ARM architecture. WCS uses a lot of native code to transcode audio and video, so it is bound to x86_64. In its turn, Docker is not a full-fleged virtual machine, so it cannot virtualize hardware, just uses the platform on which it is running. The final answer...

We reproduced the issue and raised a ticket WCS-3407 to fix it. Will let you know results here. Use the workaround mentioned above as temporary solution.

The issue has been fixed in build 5.2.1110.

Hello Please provide RTSP url. We will check. If URL is public you can post it right here. If URL is private you can send it using the report form What is the channel between RTSP source and server? Run on the host where RTSP source installed iperf3 -s -p 9999 Run on the host where WCS...

Добрый день. Обычно так происходит, когда процессор не справляется с нагрузкой и не успевает кодировать стримы. Не успевать может как весь CPU, если стримов на сервере много, так и процессорное ядро, если стрим кодируется в большом разрешении, например Full HD 1920 x 1080. Поэтому нужно...

Это похоже на баг сервера. Создали внутренний тикет WCS-3406. Отпишем по прогрессу. transcoding_video_decoding_load = ∑ width * height * fps Т.е. цифра (2758598400 / 1920 x 1080 x 30) = 44 Говорит о том, что на ваш сервер попадают 44 Full HD стрима или соответствующее количество стримов...

Try this setting in flashphoner.properties: webrtc_pre_init=false The pre initializing was added in 5.2.1105 This looks like pre-initializing issue. https://docs.flashphoner.com/display/WCS52EN/Stream+recording#Streamrecording-Knownissues

Hello Please check out this doc https://docs.flashphoner.com/display/WCS52EN/Before+moving+to+production Section (1) http_enable_paths=rest,action,shared,embed_player,empty Ports 8081 and 8444 are the same endpoint. 8081 - http, 8444 -https.

Hello rtmpUrl is incorrect Valid URL: rtmp://localhost:1935/live/stream123