Peer-to-Peer Communications with WebRTC
I have been working on a large WebRTC project, and it’s a great technology but it’s just so fragmented right now it’s hard.For iOS1. Safari has a high pass filter or something on the incoming audio. Send in some music on opus/48000 with the proper maxbitrate and listen. Now download chrome for iOS and listen. Chrome has MUCH more low end. Running the audio before and after into a spectrum analyzer chrome is much closer to the original sound.2. If you make the video full screen then exit full screen if pauses.3. I couldn’t get incoming RTP that is opus/48000/2 to be played in stereo. But as number 1 playing it in chrome does play in stereo.Android isn’t much better.1.The fragmentation is such a HUGE pain. The manufacturer browsers on the phones seem to be very hit or miss. How many browsers come by default on android phones now days?2. The latest Samsung phones cameras can’t do resolution 640x360 for whatever reason. Previous generations could and other android phones can as well.Even desktop isn’t all there.1. If you want to webrtc screen share there is no way to automatically select a screen or tab, not even CLI flags. So you can’t automate testing it. And you can’t even click the dialog in the chrome remote debugger.2. FireFox has nothing like chromes chrome://webrtc-internalsA few other things1. Simulcasting is ghetto2. I wish server CPUs would support h264/vp8/vp9 hardware encoding and decoding on the CPUs3. Want to collect metrics with getStats? Well there is no easy way to record all of them and the one SaaS is super super expensive