Search results

Good day. The ticket WCS-2853 is on testing stage. We'll let you know in this topic when Swift SDK implementation and examples will be ready.

Good day. Please check if audio track is present in the stream to be recorded on statistics page http://wcs:8081/?action=stat&params=streams_synchronization, for example -----Stream Stats----- streams_synchronization=test/-41 Normally, the absolute value should be below 500, otherwise well be...

Good day. In the latest builds, picture-in-picture mixer layout is supported. To enable this, update WCS to latest build from this page and add the following mixer option to flashphoner.properties file mixer_video_desktop_fullscreen=true In this case, you don't need custom layout to get this result:

Good day. Please read this article

You can set the folder to save recording files with the following parameter record_dir=/opt/records Note that in latest WCS builds you should either set the permissions to flashphoner user to the custom recordings folder sudo chown -R flashphoner /opt/records or start WCS as root cd...

We cannot reproduce the issue using your entry point Please describe how do you test step by step. Also please provide SSH access to the server using this private from, we will try to reproduce your test

This seems like VP8->H264 transcoding. The stripCodecs option strips the codec from browsers SDP, so this codec is not used any more. We recommend to remove the option from client code or set it to stripCodecs: "VP8" to exclude VP8 codec usage if you need H264 only. Then, if stream quality is...

Good day. Do you publish RTMP stream from MP4 file, for example ffmpeg -i file.mp4 -preset ultrafast -acodec aac -ar 48000 -vcodec h264 -strict -2 -f flv "rtmp://wcs:1935/live/stream1" and then try to play the stream via WebRTC (in Player example) as stream1? If not, please clarify exactly how...

Please ask the license questions to sales@flashphoner.com

Допустим, Вы републикуете поток stream1 на тот же сервер по RTMP POST /rest-api/push/startup HTTP/1.1 Host: localhost:8081 Content-Type: application/json { "streamName": "stream1", "rtmpUrl":"rtmp://localhost:1935/live", } По умолчанию, поток будет опубликован на том же сервере под...

Добрый день. Попробуйте включить многопоточное шифрование WebRTC трафика, добавив следующие настройки в файл flashphoner.properties rtp_paced_sender=true rtp_paced_sender_initial_rate=200000 rtp_paced_sender_increase_interval=50 rtp_paced_sender_k_up=0.9 Кроме того, рекомендуем использовать...

Pushed будет RTMP. В результате будет два стрима: исходный WebRTC и pushed RTMP.

Yes, you should publish stream before republishing it via RTMP You can republish the same stream to a number of RTMP servers simultaneously when using REST API. But, if you're using Stream object option rtmpUrl on client side, you can republish the stream to only one RTMP server. So you can...

Please check if there is stripCodecs: "H264" options in client side code. Also, set H264 codec as priotity in the following parameter: codecs=opus,...,h264,vp8,... h264 should be listed before vp8 /stream/startRecording REST query may be applied to a stream published at any moment, not just...

We checked your server. Seems like streams are published from your frontend using VP8 video codec. When you republish such stream to Wowza via RTMP, video is transcoded to H264. So if you publishing more than 20 streams simultaneously, the CPU load may be too high depending on streams resolution...

Yes, - using REST methods, or - CLI v2 commands

FFmpeg is supported for streaming RTMP Please try this way ffmpeg -re -i music.m4a -ar 48000 -acodec aac -strict -2 -f flv rtmp://server-ip:1935/live/stream

Добрый день. К сожалению, проблема не воспроизводится на стандартных примерах (Streaming-min, Media Devices, Player) на Nokia 5, Samsung S10+, Redmi 9. В наших приложениях используются следующие разрешения (на примере Streaming-min): <uses-permission android:name="android.permission.CAMERA"...

We have not tested WCS in HyperV, but there are the customers using servers in Azure cloud which uses HyperV under the hood. So WCS should work on CentOS in HyperV.

This is probably NFS driver issue in Amazon Linux 2. Unfortunately, we cannot affect low level I/O API implementation from Java process by any way, just standard open-write-close operations are used.