Rendezvous offers low quality comparing to other WebRTC solutions
I'm reopening this subject because this needs a lot of attention and has not been solved.
I'm also in direct contact with Support.
From my own inspection, it seems Rendezvous is passing incorrect video constraints on getUserMedia API (see attached image).
It sets ideal resolution to 640 which is incorrect. ideal resolution should be set to 1280.
I've made countless test sessions and none of them ever switched to 720p.
Not to mention that the host stream is locked at 480x270 at all times!!! I only saw it once at 480p which is still not ideal (see attached image).
I’ve tried Google Meets, WhereBy, Zoom Web and other WebRTC apps and all of them instantly lock to 720p. So it’s obvious that something is wrong with Rendezvous at this moment. There is no bottleneck on cpu, network or other factor.
Wirecast Rendezvous should be 720p for both the host and the guest at least for a small amount of peers (e.g. less than 3)
Wirecast Rendezvous is completely unusable for any professional work right now and forced me to look for last minute solutions while also spending 4 days debugging and trying to make it work.
For such an expensive software issues like this should simply not exist.
With that said, If Wirecast has any chance to stand, in a hardware mix era, is by offering smart solutions like Rendezvous. So please make it a priority.
Rendezvous supports 1280x720 but will vary depending on the connection conditions of both the host and the guests. The number of guests will also impact the frame size as it impacts the data rate.
The host back to the guest is low resolution as that has no impact on what is sent live. It's for guest monitoring only and ensures lower bandwidth use as some guests have limited bandwidth. It also uses the host's upload bandwidth that's also used for live streaming so it's best to be cautious. We are investigating more control over the send to guest but there are potential issues when the guest bandwidth is unknown to the host.
Wirecast is limiting the frame size to conserve bandwidth and we are investigating more control or better allocation.
All I ask is for the devs to look at their constraints. I don't see why you require 360p unconditionally from the guest. At least give as an option or a query string parameter to set desired resolution and bandwidth.
Angelos Michalopoulos said:
All I ask is for the devs to look at their constraints. There is no need to hardcode 360p for everyone.
The developers will consider this but as developers, there are "ease of use" considerations. Many customers don't understand bandwidth limitations which results in users claiming reliability issues when the problem is on their end. For example, some hosts mention their own bandwidth without understanding that the guest's bandwidth plays a role. Wirecast 15 improves the host's ability to monitor incoming statistics but there may be more work to be done in that area.
Investigating removing frame size constraints WIRE-20263