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

Audio in and out stops working after X amount of time. #997

Closed
mumble-voip opened this issue Jun 12, 2013 · 4 comments
Closed

Audio in and out stops working after X amount of time. #997

mumble-voip opened this issue Jun 12, 2013 · 4 comments

Comments

@mumble-voip
Copy link
Collaborator

I've had this issue start anywhere from 20 minutes after logging in to a few hours after. I've always had the audio disconnect happen during a lull in conversation, never cut anyone off mid stream.

The issue occurred on Win7 and Win8. And the beta versions of 1.2.4 had this issue as well.

From my end I see the mouth go red when I hit push to talk, no one sees my mouth go red though. No one else seems to have an issue when it happens to me, they continue talking thinking I'm there listening (as do I)

I have been resolving the problem by restarting the program.

This ticket has been migrated from sourceforge. It is thus missing some details like original creator etc.
The original is at https://sourceforge.net/p/mumble/bugs/997/ .

*The following attachments were added on the original item:

@mumble-voip
Copy link
Collaborator Author

I've tested this with the server/local loopback. I could hear myself local but not on the server side.

@riccruz
Copy link

riccruz commented Nov 13, 2014

I have this issue as well. I resolve the issue by reconnecting.

I run a local server that's running off of a virtual machine (KVM) on the same subnet.

@Krzmbrzl
Copy link
Member

Does this issue still exist in 1.3?

@no-response
Copy link

no-response bot commented Feb 15, 2020

This issue has been automatically closed because there has been no response to our request for more information.
With only the information that is currently in the issue, we don't have enough information to take action.

Please reach out if you have or find the answers we need so that we can investigate further (or if you feel like this issue shouldn't be closed for another reason).

@no-response no-response bot closed this as completed Feb 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants