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] Surround client not handled correctly #36

Open
3 tasks done
pallaswept opened this issue Dec 1, 2024 · 1 comment
Open
3 tasks done

[Bug] Surround client not handled correctly #36

pallaswept opened this issue Dec 1, 2024 · 1 comment
Assignees

Comments

@pallaswept
Copy link

Discord Account

No response

Operating System

openSUSE Tumbleweed

Linux Only ~ Desktop Environment

KDE Wayland

Package Type

AppImage

What happens when the bug or crash occurs?

My system is configured to use surround audio (5.1) by default. Accordingly, the audio I attempt to capture with vencord, have nodes with 6 ports.

The vencord-screen-share node has only two input ports. Normally, connections from 6 ports to 2, would require some kind of mixdown, but none is performed. Rather, only the first two channels are captured.

What is the expected behaviour?

Capture all channels of selected audio stream.

How do you recreate this bug or crash?

  1. Play audio to a surround device (application's client node will become surround)
  2. Capture audio with vencord
  3. Check connections eg with qpwgraph to confirm that not all channels are captured

Debug Logs

No crash occurs

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)
@pallaswept pallaswept added the bug Something isn't working label Dec 1, 2024
@Vendicated
Copy link
Member

If you are reporting that the screenshare audio is mono, then yes that is known. Otherwise, you should open this issue in https://github.com/Vencord/venmic instead

@Vendicated Vendicated closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2024
@Vendicated Vendicated added invalid This doesn't seem right and removed bug Something isn't working labels Dec 1, 2024
@Vendicated Vendicated transferred this issue from Vencord/Vesktop Dec 1, 2024
@Vendicated Vendicated assigned Vendicated and Curve and unassigned Vendicated Dec 1, 2024
@Vendicated Vendicated removed the invalid This doesn't seem right label Dec 1, 2024
@Curve Curve reopened this Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants