Search results

Good day. Please clarify: do you mean WebRTC screen sharing from browser as described here? If yes, what WCS build and Web SDK build do you use? Please try to update Web SDK to the latest build from this page, in this case, you can use screen sharing without extension in all the main browsers...

Good day. This seems like publisher channel or browser issue. When you playing the stream with WSPlayer, the stream is always transcoded on server (WSPlayer uses MPV codec). If you cannot play WebRTC without transcoding, this probably means irregular keyframe sending interval. So please try to...

Yes, you should enable demo user for Embed Player to work. So, to use Embed Player, do the following 1. Enable demo user, if you've disabled it according to this recommendations 2. Disable web admin interface http_enable_paths=rest,action,shared,embed_player,empty

Good day. This is not GIF image. The HLS preloader should consist of HLS segments. Please read details about HLS preloader and its customizing here.

We have not received your report yet. If you've not already sent it, please send using this form.

Mixer output is H.264 + Opus . Strictly this is not WebM and not mp4. So if you just play mixer output you would play H.264 + Opus WebRTC stream. If you try to record mixer output it will be recorded to H.264 + AAC = mp4 file

Здравствуйте. Это известная проблема, связанная с наличием B-фреймов в RTMP потоке Браузер Google Chrome не поддерживает воспроизведение B-фреймов в WebRTC видеопотоке, поэтому варианты следующие 1) Отключить B - фреймы в настройках на OBS. Например используя preset ultrafast 2)...

Please collect a report as described here and send using this form. Also please provide us RTSP link to test using this form.

Please provide us SSH access to the server with publishing and playback ability for our engineers to check. Use this private form. Also please check if quality issues are reproducing while publishing in Two Way Streaming or Media Devices examples. Yes. Please read recommendations in this post...

Good day. We raised the ticket WCS-3049 and let you know here when fix it. Please use you workarounds temporary. This is the patch to prevent microphone access request in iOS 14 for player only applications. This does not affect audio, only permissions.

No. VP8 requires WebM container. You should either publish H264 or transcode VP8 to H264 on server to record a stream to MP4 container. Do you chek our recommendations about publishing H264 in this post?

You can capture VOD from file as described here. But this is supported for MP4 container only (H264+AAC). So if you want to operate with webm recording files, not the streams, you have to use ffmpeg for muxing and nginx/apache for delivering.

Good day. Seems like systemd or kernel on your system does not support capabilities setting for service. So the following workarounds may be applied: 1. Update systemd 2. Or update OS kernel 3. Or comment the following line in the file /etc/systemd/system/webcallserver.service [Service] ... #...

Good day. The first option is to use ffmpeg to mux video from one file and audio from another, for example: ffmpeg -i video.webm -i audio.webm -c copy -map 0:0 -map 1:1 -shortest -f webm audio_video.webm Then, place the resulting file to webserver (nginx for example) folder to play it in...

WCS supports the following codecs for publishing: To play audio only stream in browser, you should use constraints: session.createStream({ name: streamName, display: remoteVideo, constraints: { video: false, audio: true } ... }).play(); Please check...

Good day. For two person video chat, mixer seems to be excessive. You can just publish and play two streams from two participants, and change webpage or application layout on client side as you wish. In this case, you can use mixer to record the meeting. But, if you prefer to use mixer, you...

Добрый день. Тикет WCS-3009 находится в работе, мы известим о результатах в этой теме.

For most mobile devices (excluding iPad), aspect ratio 16:9 is preferrable, for example mixer_video_width=360 mixer_video_height=640

We cannot reproduce the issue on your server: 1. Publish RTMP stream using ffmpeg 2. Play using Player example So it seems like media ports were blocked until you opened them for test, or they are blocked between your desktop and server. Please check. But we still can't connect to SSH port, it...

Unfortunately, the SSH credentials do not work: Please provide a working credentials or collect a report as described here and send the report using this private form.