screen delay

sabb

New Member
Hi,

How can we best relay an existing rtmp stream using flashphoner

We tried doing through screen sharing or rtmp relay, the challenge is screen sharing for video is lagging - tried different setups like 320 x 240 or 640 x 480 with 30 or 60 fps

Relay takes conversion of ffmpeg for right codec settings for flashphoner - resource consumption and adds a further lag of processing incoming feed getting converted

Is there a way we can tag flashphoner to existing rtmp or hls relay for distribution
 

Max

Administrator
Staff member
Good day.
We tried doing through screen sharing or rtmp relay, the challenge is screen sharing for video is lagging - tried different setups like 320 x 240 or 640 x 480 with 30 or 60 fps
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, and you can change screen publishing resolution in Chrome and Firefox.
Note that screen is always captured in its native resolution in Mac OS Safari, so it requires a perfect channel to publish.
Is there a way we can tag flashphoner to existing rtmp or hls relay for distribution
You can capture RTMP by two ways:
1. Publish RTMP stream to WCS using RTMP encoder. In this case, WCS is an RTMP server for publisher.
2. Capture RTMP stream from third party server. In this case, WCS is an RTMP client for this server.
In both cases, the followin codecs are supported: H264 for video and AAC for audio.
WCS does not support HLS stream capturing, but HLS playback from WCS is supported.
 
Top