Search results

Unfortunately, we do not provide ETA on forum tickets.

You can post-process the file after user has uploaded it, this is one-time operation. The alternative is the stream transcoding to equalize gop: - start VOD file capture - start transcoder for the VOD stream: Transcoding management with REST API - play the transcoded stream But realtime...

We checked the report. First, to handle 50 calls simultaneously you need a more powerful server, recommended at least 8 CPU / 16 Gb RAM. The most of SIP calls in logs are established correctly and are finished by caller hangup. The traffic dump was collected after the logs, so we did not see the...

Good day. First, for restreaming it is recommended to start VOD files using REST API: VOD capture management with REST API This is due to a long keyframe interval in file. You should reencode file to set a stable keyframe interval, for example 2 seconds: ffmpeg -i video.mp4 -c:v libx264...

Да, проблема воспроизвелась у другого клиента, и это помогло отловить deadlock. В сборке 1.1.0.58 проблема исправлена.

Seems like youtube-dl returns somethin different from downloaded file name, so ffmpeg cannot open the file. Please read this thread about getting downloaded file name.

As we mentioned above you should modify Embed Player code to pass a parameter needed, for example ... var urlServer = getUrlParam("urlServer") || setURL(); var token = getUrlParam("token") || null; ... function playStream(session) { var options = { name: streamName, display...

Good day. Please reproduce the problem and collect a report as described here using report.sh script, then send report archive using this form. If the archive size is more than 30 M, place it on Google Drive and send the link using Comment field in from.

You should fix the file to play it as VOD from S3 bucket: File format requirements

Действительно, если Вы захватываете поток с канваса, констрейнты должны быть выставлены следующим образом: constraints = { audio: false, video: false, customStream: stream }; Посмотрите также исходные тексты примера Canvas Streaming. В этом случае будут...

Good day. We fixed the issue with RTMP republishing to Youtube when RTMP outgoing buffer is enabled in build 5.2.1366. Please update and check.

Добрый день. Вы публикуете поток с констрейнтами по умолчанию Рекомендуем проставить констрейнты: video: { width: 1280, height: 720, frameRate: 30 minBitrate: 2800, maxBitrate: 4000 } В последних версиях Chrome достаточно выставить минимальный битрейт в констрейнтах...

Good day. Use record_dir parameter: Directory for saving recorded files record_dir=/opt/records

We reproduced the problem in GPUImageDemo Swift example and raised the ticket WCS-3584. Will let you know about progress.

Please clarify how do you publish a stream. Check the server logs for Failed by video RTP activity message. Is it appear for the stream? Also please clarify how do you test a network issues: closing the media port, breaking the physical connection etc? Then collect a report as described here...

Good day. Yes, stream publishing may fail if RTP data are not received in 60 seconds by default. In this case, there should be message Failed by video RTP activity in server logs. The timeout is set by the following parameter: rtp_activity_timeout=60 Set this parameter in seconds to reduce the...

Если требуется подгонка под определенный макет, то стандартный шаблон, конечно, не подойдет, т.к. размеры картинок потоков вычисляются, исходя из их количества. Используйте FullScreenDesktopLayout в качестве образца при разработке собственного шаблона.

switchCamera method should not be called for playStream, it is only working for publishing, not for playback. See also usage example in Two Way Streaming source code.

Hello, Please send the MP4 file (or a download link to it if its size more than 30 M) with which the issue occurs using this form. Seems like it has no atoms needed in header. You can also check this file in ffprobe.

Hello, Ticket WCS-3582 has been submitted for the issue, we'll notify in this thread about an update. Use mediaSessionId as workaround: /rest-api/stream/terminate { mediaSessionId: "stream-mediaSessionId-to-terminate" } You can get mediaSessionId using /stream/find query...