Saúl Ibarra Corretgé
Saúl Ibarra Corretgé
@dependabot rebase
It's a performance tradeoff. Just like browsers, which default to low fps but high resolution. In our implementation we limit the fps because of performance reasons and the limitations around...
Sounds like a good idea to me 👍
Are you able to grab full logs? adb logcat for the duration of the meeting. There is a chance the CPU is not able to cope.
> D JitsiMeetSDK: [modules/qualitycontrol/QualityController] Encode stats for LocalTrack[2,video]: codec=VP8, time=26.96634615384615,resolution=360, qualityLimitationReason=bandwidth WebRTC limited the resolution due to bandwidth constraints.
> Is this due to the local bandwidth limitations of the current AR glasses device, or the bandwidth limitations of the Jitsi Meet server? It's the bandwidth available between the...
The CPU in those glasses is likely not very powerful, so you can try disabling simulcast and sending a single resolution then. You can also try to enable hardware accelerated...
Yeah seems like libWebRTC doesn't know how to work with that codec implementation :-/ It's likely it also has hw accelerated VP8, can you check?
I'm afraid you're out of luck here. The only supported hw encoder which we also support is H.264 (avc) but as you tested before WebRTC fails to initialize it. Not...
I wouldn't know how to do that, sorry.