Using Firefox, a vMix call runs solidly at 1280x720@30 at ~1800kbps on Auto. If I change the Remote Guest Video Bandwidth to say 800, then the call manager shows this has happened.

Using Chrome and Edge with everything else the same, a vMix call mostly sits at 640x360@15-30 at 80-250kbps, occasionally moving up to 960x540 or down to 480x270 but without a corresponding change in bandwidth usage.

With all browsers, call manager reports negative packets lost, approximately equal to resent packets. This begs the question - is the client getting a bit trigger happy with resending packets?

Results at beta.vmixcall.com are the same. The camera, a Logitech HD C615, reports as supporting 1920x1080 in all browsers. Remote site speed is 100/10Mbps, vMix site speed is 100/30Mbps and all of that bandwidth was made available during tests. Client computer is a PC running win10, i7-9700K, NVIDIA RTX2060. Chrome utilisation during call is 5% CPU / 2% GPU.

I think I should be able to have a 1280x720@30 call running on any browser where the conditions clearly should allow it and even an option for higher resolutions. I am not interested in suggestions to edit the browser configs to achieve this as I cannot expect guests to follow complex instructions and even have the appropriate access.

Thanks,

Dave

Edge, Chrome and Firefox show support for my webcam at 1280x720 and at 1920x1080 via the WebRTC Troubleshooter https://test.webrtc.org/

I understand a little of how WebRTC works. Notice that I said Chrome changed resolution up to 960x540, so clearly a fallback default of 640x480 was not the situation there. For now, not wishing to derail the thread into the realms of higher resolution availability, let's just try to work on getting Chrome and Edge working at 1280x720. Where do you think the issue lies?

Thank you for your response.

Dave