You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you turn on a webcam with Vesktop, the camera resolution is automatically lowers to 432x240 at 30fps, I've witnessed it happening in real time from 1080p30 -> 240p using cameractrls when i enable my webcam in a voice call.
-Using the official Discord client, the webcam stays at 1080p.
-Using an OBS Virtual camera, the resolution stays at 1080p (however the camera occasionally appears black to other members of the call).
What is the expected behaviour?
I expect Vencord to NOT be able to change my webcams resolution. If i set my camera to use 1080p30 in the software (cameractrls), Vesktop should respect that.
How do you recreate this bug or crash?
Connect a webcam
Join a call
Enable the webcam
Observe the resolution
Debug Logs
[8979:0204/001405.004498:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.004570:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.072468:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.072536:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.140480:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.140560:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.204495:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.204559:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.272469:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.272531:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.340463:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.340534:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.404485:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[8979:0204/001405.404566:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[8979:0204/001405.472459:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
Request Agreement
I have searched the existing issues and found no similar issue
I am using the latest Vesktop and Vencord versions
This issue occurs on an official release (not just the AUR or Nix packages)
The text was updated successfully, but these errors were encountered:
Discord Account
euphoric.cat
Operating System
Arch Linux
Linux Only ~ Desktop Environment
KDE Plasma 6
Package Type
AppImage
What happens when the bug or crash occurs?
When you turn on a webcam with Vesktop, the camera resolution is automatically lowers to 432x240 at 30fps, I've witnessed it happening in real time from 1080p30 -> 240p using cameractrls when i enable my webcam in a voice call.
-Using the official Discord client, the webcam stays at 1080p.
-Using an OBS Virtual camera, the resolution stays at 1080p (however the camera occasionally appears black to other members of the call).
What is the expected behaviour?
I expect Vencord to NOT be able to change my webcams resolution. If i set my camera to use 1080p30 in the software (cameractrls), Vesktop should respect that.
How do you recreate this bug or crash?
Debug Logs
Request Agreement
The text was updated successfully, but these errors were encountered: