Search results

Добрый день. Сборка WebSDK 2.0.208 выгружена.

We do not provide ETA for feature request on the forum. But we can raise implementation priority if more customers request the feature. For temporary workaround, you can use on demand transcoding as recommended above

>According to the stream-recording documentation, the flashphoner can record a stream with the VP8 codec. It's correct. WCS can record single stream in webM (vp8 codec). These two features are bit different: Single stream recording...

When you set disable_streaming_proxy=true Transcoding will be started upon playback only. The multi-recorder will not trigger transcoding automatically. Try to launch transcoding manually using REST API as described in the docs. Option1. REST API. Make a bash script using REST API which...

Seems like SRT publishing/playback is not supported in browsers yet, but ffmpeg-based tools (ffmpeg itself, OBS, Gstreamer) support it. So we consider MPEG-TS over SRT publishing from ffmpeg implementation.

Good day. We're working on it in ticket WCS-2680. Today, SRT is implemented as internal CDN transport, and SRT will be implemented for stream publishing. We let you know here.

If you've imported SSL certificate for domain, the IP address becomes unsecure at browser point, even if this is the address bound to domain name. So no, you should not replace a valid domain name with IP address.

We raised the ticket WCS-3418 to investigate the dump provided. Let you know results here.

Good day. Please read here.

Good day. We've cleaned your thread and banned the spammer.

If this tweak does not help webm_java_writer_enable=false then we need an original streams dumps and debug logs to reproduce the problem. So you should collect a report as described here and traffic dump: 1. Enable client debug logs 2. Start tcpdump to collect tcpdump -npi any -B 10240 -w...

We checked dumps you've sent. Unfortunately, the first dump does not contain a client IP addrees you mentioned in comment (192.168.1.140), and the second dump does not contain a session beginning, so we cannot play it to reproduce the issue. Please collect the traffic dump again: 1. Stop all VLC...

What is WCS version? If version is greater than 5.2.905, you can try fallback to old webM recording implementation webm_java_writer_enable=false https://docs.flashphoner.com/display/WCS52EN/Stream+recording#Streamrecording-VP8streamsrecordingtowebmcontainer

Could you try with ffmpeg 4.x ? If you can play this file in VLC, ffmpeg 4.x might be a fix too.

1. Regarding ports. 8444 - dashboard panel HTTPS 8081 - dashboard panel HTTP 8443 - websocket WSS 8080 - websocket WS So if you set AWS loadbalancer, it should forward ports, i.e. 8444 > 8081 8443 > 8080 or 8444 > 8444 8443 > 8443 In such a case you set SSL certificates on Load balancer...

As an option, you can transcode all VP8 streams to H.264 using Transcoder API. Once stream is being transcoded, it can be added to the multi-recorder. Please note. Single transcoding session may use 1-2 physical CPU cores on the server.

>Do we have anything that can automatically adjust bitrate as per internet speed without doing anything? Desired bitrate should be passed before subscribing (playing) on the stream. It won't be changed automatically for each viewer.

Для этого надо воспользоваться функцией inject (замена потока) https://docs.flashphoner.com/pages/viewpage.action?pageId=23038525 1. Отправляем стрим с экрана как отдельный стрим, например "main". 2. Отправляем стрим шаринга, например "sharing". 3. С помощью REST запроса /inject, делаем вставку...

You should buy a valid SSL certificate for your WCS server domain, then import SSL certificate via WCS web admin interface.

Good day. In this case, stream should be transcoded to desired resolution/bitrate. Let's suppose you plaing the stream as WebRTC. You can check viewer channel quality at client side as described here, and, if quality is bad, stop the playing stream and request it with desired constraints...