Closed pepper-ann closed 2 years ago
What platform, audio system, and version of Mumble are you experiencing this on?
Sorry..
Windows 10, realtek driver 6.0.1.7806, Mumble 1.2.19
Could you install the latest snapshot and see if the issue persists, please?
Are you referring to 1.3.0~2586~g894ade2~snapshot?
Yes.
Ok it is installed, I'll report back after using it later tonight or tomorrow. Thanks!
You're welcome, thank you!
So same issue persists. Also with this snapshot, I noticed that mumble freezer for about a half a minute when I select "connect" from the list of servers.
Is there something related to the issue in the developer console's log?
I don't have a way to view that, let me figure out how to use it and I'll try to recreate the issue while the log is recording.
On Sun, Feb 25, 2018 at 10:40 PM, Davide Beatrici notifications@github.com wrote:
Is there something related to the issue in the developer console's log?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mumble-voip/mumble/issues/3345#issuecomment-368388329, or mute the thread https://github.com/notifications/unsubscribe-auth/AjAC7YA1FoGcNWQPTLzlKaYmjcOr1O7Xks5tYjWpgaJpZM4SNplz .
To enable it:
Settings -> User Interface -> Enable Developer menu
You can view it by clicking on "Developer" from the main window's menu and then on "Developer Console..."
Here is the developer console log, I was in mumble for a bit and then the problem occurred. I verified that they could hear me, but I couldn't hear anyone else.
So after leaving the developer console open for a long time, I was able to pinpoint the entries that occured when the sound cuts out:
2018-03-11 10:25:36.047 WASAPINotificationClient: Default device changed flow= 0 role= 1 device "{0.0.0.00000000}.{dade4e67-55f9-4413-b5c2-825f5a4e94cf}" 2018-03-11 10:25:36.099 WASAPINotificationClient: Default device changed flow= 0 role= 0 device "{0.0.0.00000000}.{dade4e67-55f9-4413-b5c2-825f5a4e94cf}" 2018-03-11 15:58:35.788 WASAPINotificationClient: Default device changed flow= 0 role= 1 device "{0.0.0.00000000}.{6186de92-785e-41b5-962c-6b65b63adf83}" 2018-03-11 15:58:35.789 WASAPINotificationClient: Default device changed flow= 0 role= 0 device "{0.0.0.00000000}.{6186de92-785e-41b5-962c-6b65b63adf83}" 2018-03-11 18:57:37.922 WASAPINotificationClient: Default device changed flow= 0 role= 1 device "{0.0.0.00000000}.{dade4e67-55f9-4413-b5c2-825f5a4e94cf}" 2018-03-11 18:57:37.922 WASAPINotificationClient: Default device changed flow= 0 role= 0 device "{0.0.0.00000000}.{dade4e67-55f9-4413-b5c2-825f5a4e94cf}" 2018-03-11 19:03:38.039 WASAPINotificationClient: Default device changed flow= 0 role= 1 device "{0.0.0.00000000}.{6186de92-785e-41b5-962c-6b65b63adf83}" 2018-03-11 19:03:38.046 WASAPINotificationClient: Default device changed flow= 0 role= 0 device "{0.0.0.00000000}.{6186de92-785e-41b5-962c-6b65b63adf83}"
any ideas?
updates:
still getting the same issue. it's very frustrating
i got new headphones, windows 10 pro 1709 audio driver: 10.0.16299.15 corsair void
any help will be very appreciated
I think this is the same issue as https://github.com/mumble-voip/mumble/issues/5421. Since we have some more active discussion over there, I'll close this issue in favor of the linked one
This problem is especially annoying because I don't know it happens until I become aware of the long silence on the other end. I can still transmit sound but I don't hear anything. When I restart Mumble, my push to talk doesn't work for a good minute, after which point it works fine. That is, until the output eventually cuts out again. I haven't noticed any pattern as to what could be causing it. I have tried running in adminstrator mode with no luck.