search

Vencord / Vesktop

Vesktop is a custom Discord App aiming to give you better performance and improve linux support
GNU General Public License v3.0
3.69k stars 175 forks source link

[windows] Streaming with audio does not work #334

Open NolonQ opened 8 months ago

NolonQ commented 8 months ago

Describe the bug streaming with vekstop only works if the "stream with audio" option is disabled

To Reproduce In vesktop start a stream in any quality with the "stream with audio" option enabled

Expected behavior Streaming any quality with audio should work correctly

Screenshots

Desktop (please complete the following information):

Additional context .

NolonQ commented 8 months ago

Any input?

TheAngryTurkey commented 7 months ago

Same issue here, except for me I can reproduce it if I select the output audio on Windows as my headphones. Any other audio output works and I can stream with audio perfectly fine, but as soon as I select my headphones as the output audio it doesn't let me stream. It doesn't matter what the audio settings are in Vesktop, as soon as I change to audio that isn't the headphones it works fine. Vesktop Audio Problem

thek0d3r commented 6 months ago

Same here two months later... image

Skiexx commented 6 months ago

same problem

Vendicated commented 6 months ago

do not reply if you have no new info to contribute. it's spam. react with a :+1: to show that you have the same issue

Joshua-Ashton commented 3 months ago

I am getting a similar bug, I am posting here as #618 was closed.

I am not screensharing with audio.

It starts with: 'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:426 pw_thread_loop_wait() on the Screenshare dialog

and ends up with

stdout:

(node:4830) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
    at AsyncFunction.<anonymous> (VCDMain:24:2433)
(node:4830) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

Console:

Error: webpack.findStore found no module
    at Zn (webpack.ts:96:17)
    at Vy (webpack.ts:343:9)
    at webpack.ts:353:28
    at [vencord.lazy.get] (lazy.ts:98:38)
    at Object.get (lazy.ts:120:39)
    at onClick (VCDRenderer:1:15193)
    at Object.eF (67096.30c593c3471420b5c889.js:12:914242)
    at eG (67096.30c593c3471420b5c889.js:12:914396)
    at 67096.30c593c3471420b5c889.js:12:932705
    at re (67096.30c593c3471420b5c889.js:12:932804) Filter: ['MediaEngineStore']
_log @ Logger.ts:35
error @ Logger.ts:53
Zn @ webpack.ts:97
Vy @ webpack.ts:343
(anonymous) @ webpack.ts:353
[vencord.lazy.get] @ lazy.ts:98
get @ lazy.ts:120
onClick @ VCDRenderer:1
eF @ 67096.30c593c3471420b5c889.js:12
eG @ 67096.30c593c3471420b5c889.js:12
(anonymous) @ 67096.30c593c3471420b5c889.js:12
re @ 67096.30c593c3471420b5c889.js:12
rt @ 67096.30c593c3471420b5c889.js:12
(anonymous) @ 67096.30c593c3471420b5c889.js:12
sA @ 67096.30c593c3471420b5c889.js:12
eI @ 67096.30c593c3471420b5c889.js:12
rs @ 67096.30c593c3471420b5c889.js:12
tF @ 67096.30c593c3471420b5c889.js:12
tP @ 67096.30c593c3471420b5c889.js:12
Logger.ts:35  Vencord   VesktopScreenShare  Error while submitting stream. TypeError: Reflect.get called on non-object
    at Reflect.get (<anonymous>)
    at Object.get (lazy.ts:120:28)
    at onClick (VCDRenderer:1:15193)
    at Object.eF (67096.30c593c3471420b5c889.js:12:914242)
    at eG (67096.30c593c3471420b5c889.js:12:914396)
    at 67096.30c593c3471420b5c889.js:12:932705
    at re (67096.30c593c3471420b5c889.js:12:932804)
    at rt (67096.30c593c3471420b5c889.js:12:933218)
    at 67096.30c593c3471420b5c889.js:12:938680
    at sA (67096.30c593c3471420b5c889.js:12:995753)
_log @ Logger.ts:35
error @ Logger.ts:53
onClick @ VCDRenderer:1
eF @ 67096.30c593c3471420b5c889.js:12
eG @ 67096.30c593c3471420b5c889.js:12
(anonymous) @ 67096.30c593c3471420b5c889.js:12
re @ 67096.30c593c3471420b5c889.js:12
rt @ 67096.30c593c3471420b5c889.js:12
(anonymous) @ 67096.30c593c3471420b5c889.js:12
sA @ 67096.30c593c3471420b5c889.js:12
eI @ 67096.30c593c3471420b5c889.js:12
rs @ 67096.30c593c3471420b5c889.js:12
tF @ 67096.30c593c3471420b5c889.js:12
tP @ 67096.30c593c3471420b5c889.js:12
758694862408122368:1 Uncaught (in promise) DOMException: Error starting capture
BadKiko commented 3 months ago

yep EndeavourOS after updating get error

[3:0620/004346.030868:ERROR:shared_x_display.cc(39)] Unable to open display
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
[2024-06-20 00:43:49.242] [venmic] [info] [patchbay] (get) running venmic 3.4.2
[2024-06-20 00:43:49.394] [venmic] [info] [patchbay] (handle) found default metadata: 40
[2024-06-20 00:43:49.394] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.pci-0000_0c_00.4.iec958-stereo"
(node:3) UnhandledPromiseRejectionWarning: TypeError: Video was requested, but no video stream was provided
    at AsyncFunction.<anonymous> (VCDMain:24:2411)
(Use `vesktop.bin --trace-warnings ...` to show where the warning was created)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
Vendicated commented 3 months ago

this is a windows issue. do not hijack it with unrelated Linux issues. they are an issue with your system and have nothing to do with this issue.