search

muaz-khan / WebRTC-Scalable-Broadcast

This module simply initializes socket.io and configures it in a way that single broadcast can be relayed over unlimited users without any bandwidth/CPU usage issues. Everything happens peer-to-peer!
https://rtcmulticonnection.herokuapp.com/demos/Scalable-Broadcast.html
532 stars 142 forks source link

Hi,why i could not see video/screen/audio using webrtc-scalable-broadcast #15

Open Jackie2016 opened 8 years ago

Jackie2016 commented 8 years ago

hi,expert, i test demos of webrtc-scalable-broadcast on my server,i only can see the joined message or stream message from node server console.but i cant see the video/screen/audio in joined terminal browser.what is the setting of webrtc-scalable-broadcast for broadcast my video/screen/audio?could you give me a suggestion?thanks

muaz-khan commented 8 years ago

Please try this demo:

Jackie2016 commented 8 years ago

thanks muaz,this demos you showed is ok.but i want to realize these: i could realize screen+audio and video+audio.that is i could switch it easily from video+audio to screen+audio mode,or from screen+audio to video+audio.could show me another example or some light?thanks another question is whether i could switch screen+audio to video+audio without reconnection.

muaz-khan commented 8 years ago

Firefox supports audio+screen capturing; and Chrome 50+ supports audio+tab. So you can handle audio+tab or audio+screen inside your getUserMedia invocation codes.

Regarding switching from audio+screen to audio+video, Firefox supports replaceTrack (as well as applyConstraints) methods which works fine in the above demo. Chrome on the other hand, requires renegotiation, however it is/will-be tough/hard to implement renegotiation in a scalable-broadcast demo.