Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Webcam resolution lowers automatically #1076

Open
3 tasks done
veryrealwildcat opened this issue Feb 3, 2025 · 2 comments
Open
3 tasks done

[Bug] Webcam resolution lowers automatically #1076

veryrealwildcat opened this issue Feb 3, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@veryrealwildcat
Copy link

veryrealwildcat commented Feb 3, 2025

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?

  1. Connect a webcam
  2. Join a call
  3. Enable the webcam
  4. 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)
@veryrealwildcat veryrealwildcat added the bug Something isn't working label Feb 3, 2025
@n4htx
Copy link

n4htx commented Feb 23, 2025

This also happens on Windows 11 LTSC, and it causes my webcam to appear stretched vertically since im using a capture card for a camera and its picks the 480p option which is limited to 3:2.

@apeltsi
Copy link

apeltsi commented Mar 10, 2025

Also experiencing this, using nixos with sway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants