[Windows 10] Video-call: Crash if both peers (Windows 10 AND Android user;) don't enable hardware acceleration; Jami can't handle calls if the Android user enabled hardware acceleration
first title: Crash after you shared your screen twice (or if you select "OBS-VirtualCam" or "ManyCam Virtual Webcam" and DISABLE Hardware Acceleration?)
Alice: Android (EMUI 12) 20220615-01 Bob: Windows 10: Jami (beta-)Version 202206231612
You make a video call Android -> Windows 10 ("username1" -> "username2").
I think it's also related to the video codec H264? Probably not?
You always have to exit Android and Windows 10 once you changed the settings: #763 (comment 37579)
If you want to prevent a crash on Windows 10 you have to disable hardware acceleration and exit BOTH - the windows client AND the android client - and enter both apps again.
Update: #763 (comment 37408)
This is actually the main issue: #763 (comment 36675)
It does not matter if you actually launch OBS-VirtualCam or not.
If you select your video device "OBS-VirtualCam" but you disable Hardware Acceleration (using the video settings of the Jami client [Windows 10]) Jami will receive the Android call and crash as soon as you (the Windows 10 user) answer the call.
-
It does NOT happen if I select "ManyCam" and (also) disable hardware Acceleration.EDIT: Just reproduced a crash. - It does NOT happen if I select "OBS-VirtualCam" but ENABLE hardware acceleration.
Here are the logs:
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700] real-time buffer [@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A3FCE0F5-3493-419F-958A-ABA1250EC20B}] [video input] too full or near too full (103% of size: 3041280 [rtbufsize parameter])! frame dropped!
[dshow @ 000001DEABC91700]