Asking here even if am unsure if it is best place to start as the fear is that it is cross boundaries one.
WebRTC supports hardware acceleration as per i.e.:
This is sort of two fold question/problem:
- is it that request for hardware accelerated stream has to be made from browser/based on what i.e. Jitsi instructs browser to do or is it that hardware support is checked first just due to nature of how WebRTC is coded?
- if webcam supports h264 stream on top of yuyv and mjpeg, will WebRTC/Jitsi select first the h264? Assuming that bridge is pushed to h264 or for p2p.
Motivation - looking for a simple and relatively cheap setup based on Pi 4 which theoretically has acceleration, but maybe something is missing.
For 1080p am getting at max 4-6 fps with CPU maxed out and having GPU at browser level enabled (https://lemariva.com/blog/2020/08/raspberry-pi-4-video-acceleration-decode-chromium).
95% of time the system will be not doing anything hence looking towards arm based one to limit power consumption/overall price.
Current webcam is Logitech C920 (which used to have h264, but not anymore - removed by Logitech back in 2018).
Options being considered:
- get other webcam with h264 stream provided - there are some ~50EUR one available, but am afraid of picture quality or pay premium for Logitech with h264 (business line)
- get other unit, i.e. Nvidia Jetson 2GB with GPU onboard - also risk is that hw h264 encoding won’t be picked up by browser and don’t want to throw another $$$ on just simple test.
Thanks in advance!