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.

Sign up for GitHub

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

Jump to bottom

Volume mixer becomes empty within tens of seconds after EarTrumpet is turned on #1072

Closed
STONE-Git opened this issue Feb 21, 2022 · 3 comments
Closed

Volume mixer becomes empty within tens of seconds after EarTrumpet is turned on #1072

STONE-Git opened this issue Feb 21, 2022 · 3 comments
Labels
status: can't reproduce We cannot reproduce this issue

Comments

@STONE-Git
Copy link

Summary

Volume mixer becomes empty randomly within tens of seconds each time after EarTrumpet is turned on. Only the Volume mixer of EarTrumpet becomes empty. The Volume mixer of the system seems fine. It happens immediately after changing the default device, but also happens without changing the default device.

Steps to reproduce

image
bug

EarTrumpet version

2.1.9.0

Windows version

10.0.19044.1566

Additional information

tmp9CC0.tmp.txt
@riverar
Copy link
Contributor

riverar commented Mar 16, 2022

@STONE-Git Thanks for the bug report. Can you explain how you are switching devices? Is this via an external switch? Unplugging something? Trying to reproduce this here and so far I can't. Thanks!

@riverar riverar added the status: can't reproduce We cannot reproduce this issue label Mar 16, 2022
@Sebastian-Specjal
Copy link

I have the same issue with Windows 10 Pro 20H2 10.0.19042 Kompilacja 19042.
After restarting the application, I see active sound-broadcasting applications again

Zrzut ekranu 2022-03-28 100055

@riverar riverar mentioned this issue Jan 26, 2023
Open
@riverar
Copy link
Contributor

riverar commented Jan 26, 2023

Hi there. I'm cleaning up the issues list. I'm going to tie this to master issue #1305, thanks!

@riverar riverar closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: can't reproduce We cannot reproduce this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@riverar @STONE-Git @Sebastian-Specjal