WebRTC as RTMP re-publishing Not Working in Google Chrome

Good day.
We have checked your logs and tried to reproduce.
It seems like Facebook and Youtube issue: they both receive 1280x720 RTMP stream, but allows to choose for playback 360p maximum only.
You can check streaming with our Wowza demo server rtmp://wza4-demo.flashphoner.com:1935/live to make sure you have sending 720p stream.
 
Good Day @Max

Its not issue with Facebook or YouTube side we have checked with OBS 720P is working fine on Facebook and YouTube using OBS please see attached screen shoots.
Please check it on your side.

Thanks,
Faraz
 

Attachments

  • youtube_5.png
    youtube_5.png
    287 KB · Views: 531
  • youtube_6.png
    youtube_6.png
    61.5 KB · Views: 505
  • fb_3.png
    fb_3.png
    504.5 KB · Views: 487
With OBS, you start RTMP streaming with fixed resolution 720p.
With WebRTC as RTMP. you can start WebRTC streaming with resolution lower than 720p, depending on your channel bandwith, for example 360p, then it raise to 720p. It's WebRTC standart behaviour to adjust stream resolution on the fly. Seems like Facebook and Youtube adjust quality controls by first frame.
So you should use REST API to publish RTMP stream to Youtube and Facebook rather than JavaScript API as described in this example. In this case you start RTMP streaming when WebRCT stream is already published and probably has resolution 720p as needed (depending on channel bandwidth and quality).
Also you can try to publish WebRTC over TCP as described here, but this may not escape resolution adjusting.
 
Hello,

Yes, using CLI:
Code:
ssh -p 2001 admin@localhost
User 'demo' can be disabled
Code:
update user -a false demo
or, the password can be changed
Code:
passwd demo
 
With OBS, you start RTMP streaming with fixed resolution 720p.
With WebRTC as RTMP. you can start WebRTC streaming with resolution lower than 720p, depending on your channel bandwith, for example 360p, then it raise to 720p. It's WebRTC standart behaviour to adjust stream resolution on the fly. Seems like Facebook and Youtube adjust quality controls by first frame.
So you should use REST API to publish RTMP stream to Youtube and Facebook rather than JavaScript API as described in this example. In this case you start RTMP streaming when WebRCT stream is already published and probably has resolution 720p as needed (depending on channel bandwidth and quality).
Also you can try to publish WebRTC over TCP as described here, but this may not escape resolution adjusting.

@Max

We have checked with rest api method and found that its working for RTMP but not for RTMPS see attached screen shoot no stream comes to Facebook
 

Attachments

  • 2019-04-22_1854.png
    2019-04-22_1854.png
    214.2 KB · Views: 542
Good day.
We fixed RTMPS support in build 5.2.109 and tested it with Facebook, it works now. Please update to this build and check.
 
Top