WebRTC as RTMP re-publishing Not Working in Google Chrome

[Faraz Ahmed]

@Max
I am attaching screen shoot again here

I have also emailed logs to support@flashphoner.com

 

[Max]

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.

 

[Faraz Ahmed]

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

 

[Max]

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.

 

[Faraz Ahmed]

Hi @Max

Can we disable demo user account from https://wmedia.livepigeonapp.com:8888/admin/
or can we change password for demo account


Thanks,
Faraz

 

[Max]

Hello,

Yes, using CLI:

ssh -p 2001 admin@localhost

User 'demo' can be disabled

update user -a false demo

or, the password can be changed

passwd demo

 

[Faraz Ahmed]

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

 

[Max]

Good day.
We work on RTMPS support and let you know on results.

 

[Faraz Ahmed]

Good day.
We work on RTMPS support and let you know on results.

@Max
please see warning from Facebook in attached screen after 1st May RTMP will not be supported by Facebook we need to switched to RTMPS so please update us soon.

 

[Max]

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.