Search results

REST API queries support filtering by mandatory fields, but custom object is optional. Also, we can't make a supposition about custom object contents, every customer may use its own form.

Проверили Ваш сервер. При публикации WebRTC поток в VLC по RTSP играет: Однако Вы используете VP8 как предпочитаемый кодек для публикации. Это означает, что для проигрывания потока по RTSP по умолчанию будет включаться транскодинг VP8->H264. На тестовом сервере всего 1 vCPU, поэтому его...

Эта документация относится к Android SDK 1.0. В Android SDK 1.1 эта опция, как и весь код класса X509TrustManager, была удалена в связи с тем, что приложения с использованием Android SDK 1.1 перестали проходить проверку при публикации в Google Play, посокльку код этого класса был признан...

Fixed, it is available again. But we do not test it with latest WCS builds, and do not recommend to use it due to codec limitations (VP8 only). Please use MPEG-TS over SRT publishing instead (ffmpeg, OBS, Gstreamer support this). When receiving a /playStream hook, you have a stream name, a...

По умолчанию, для обслуживания RTSP клиентов используется TCP порт 554. Начиная со сборки 5.2.801, WCS запускается от пользователя flashphoner. Порт 554 привилегированный, поэтому сервер не может его использовать по умолчанию. Нужно либо менять значение порта: rtsp.port=5554 и играть поток как...

Добрый день. Вы можете забрать поток с WCS сторонним приложением по RTSP или RTMP. Кодеки при этом настраиваются в файлах SDP flash_handler_play.sdp для RTMP и rtsp_server.sdp для RTSP. Кодеки можно выбрать только из числа поддерживаемых для каждого из этих двух кейсов.

You can detect the publisher stream quality: Publisher and player channel quality control. Then, if quality becomes BAD, you can republish the stream with a lower resolution/bitrate. Also, there is WebRTC ABR or HLS ABR for playing streams only. Note that ABR cases require transcoding on the...

Good day. The custom fiels is intended to use in REST hooks, not in REST API filters. Please look at this use case: Authentication. So you should set up REST hook /publishStream (see the example of /connect REST hook setup), collect a stream descriptions including tokens on your backend and then...

Проблема исправлена в сборке WCS 5.2.1586. SFU SDK требуется обновить до 2.0.206 (или из NPM).

Проблема исправлена в сборке WCS 5.2.1586. SFU SDK требуется обновить до 2.0.206 (или из NPM).

In the last report, there are two successfull reconnects to Facebook ingest point. Note that Facebook may drop connection if no keyframe received, so reencode the file for even keyframe interval (2-4 seconds as Facebook recommends). Also please test publishing to Facebook only, to clarify the...

Please provide a report when trying to capture the file as VOD from S3.

The last file you've sent Sample Video 10 MB.mp4 has a wrong atoms structure So it cannot be captured as VOD from S3 storage, see File format requirements You should also to encode files with an even keyframe interval (Facebook recommends 2-4 seconds) and without B-frames.

Your sample has 4K resolution and bitrate 10 Mbps. So its capturing as VOD and republishing requires a very good channels. You have the following bottlenecks: 1. Between S3 storage and WCS 2. Between WCS and Youtube server 3. Between WCS and Facebook server So you should use lower resolution and...

Seems like you're republishing the VOD stream to Youtube and Facebook simultaneosly, and Facebook closes the RTMP connection at its side after 10-12 seconds of republishing: But translation to Youtube goes until the end of the file. Seems like you have some channel problems between your server...

The report we received contains no stream capturing and republishing. Please reproduce the problem before collecting the report.

Please restart the server, reproduce the problem, collect a full report as described here: Getting logs with report.sh script and send the archive using this form.

Good day. Seems like the VOD is successfully captured, but Facebook republishing is eventually stopped. Please check if you applied the following settings rtmp_transponder_full_url=true rtmp_transponder_stream_name_prefix= rtmp_flash_ver_subscriber=LNX 76.219.189.0...

We fixed the issue in build 5.2.1584. The demo server is updated, your stream is playing successfully. Please note that the stream has a 2K resolution and a huge bitrate (up to 6 Mbps peak), so you should play it via TCP. Set the Transport switch in Media Devices example as shown, then play the...

We checked the stream. It's H265, and seems its bitstream is not parsed correctly. We're about to fix it in ticket WCS-3704, will inform you in this topic.