Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 5 of 5
  1. #1
    Join Date
    June 2014
    Posts
    6

    Question New mic randomly disconnects/stops responding in teamspeak.

    So I picked up a new headset (HyperX Cloud II) and it's all good and fine expect for the fact when I'm ingame (World of Warships) and talking to people on teamspeak, after a short while my microphone stops working, example I use push to talk with voice detection on top of the push to talk and when I press my push to talk button teamspeak won't pick up any sound from the mic.

    The microphone is not the issue as after I restart teamspeak the problem goes away for 20mins to 1 hour until it comes back again and it only happens when I'm ingame, looking at logs I'm thinking it's just an issue with lacking CPU time since I do play my game on high priority due to the fact my pc is a potato, the odd thing about it is that I didn't once have an issue with my old mic even with games on high priority and I'm not quite sure why it's happening now, however I did have to update teamspeak to a new version to get my headset to work.

    TeamSpeak version: 3.0.19.4 (14-Jul-16 22:16:58)
    Operating System: Windows 10 Pro 64-bit (10.0, Build 10240) (10240.th1.150819-1946)
    Soundcard & Driver version:
    • Description: Headset Microphone (HyperX 7.1 Audio)
    • Default Sound Capture: Yes
    • Default Voice Capture: Yes
    • Driver Name: USBAUDIO.sys
    • Driver Version: 10.00.10240.16384 (English)
    • Driver Attributes: Final Retail
    • Date and Size: 7/10/2015 23:59:36, 131584 bytes

    DirectX version: 11.2
    Error messages:
    Code:
    29-Dec-16 20:12:45	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 35	
    29-Dec-16 20:20:07	Newsticker	Info	Newsticker next check: Fri Dec 30 09:20:07 2016	
    29-Dec-16 20:20:17	Newsticker	Info	Newsticker next check: Fri Dec 30 09:20:07 2016	
    29-Dec-16 20:20:18	Newsticker	Info	Newsticker received for language en, expires on Fri Dec 30 09:50:17 2016, next check in 1800 seconds	
    29-Dec-16 20:21:57	Windows Audio Session	Debug	Got 3 or more rendering spaces in same loop 441 970 529	
    29-Dec-16 20:24:01	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2573 ms 2000	
    29-Dec-16 20:24:01	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2578 ms 2000	
    29-Dec-16 20:24:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2312 ms 2000	
    29-Dec-16 20:24:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2314 ms 2000	
    29-Dec-16 20:25:03		Info	Memory usage: 64.32 MiB	
    29-Dec-16 20:26:20	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 3432 ms 2000	
    29-Dec-16 20:26:20	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 3437 ms 2000	
    29-Dec-16 20:26:52	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 5303 ms 2000	
    29-Dec-16 20:26:52	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 5304 ms 2000
    Code:
    29-Dec-16 19:02:43	ClientUI	Info	Connect status: Connection established	
    29-Dec-16 19:02:43	PermManager	Info	Loading permissions from cache	
    29-Dec-16 19:02:45	Windows Audio Session	Debug	WAS::associateAECDevice-enter	
    29-Dec-16 19:02:45	Windows Audio Session	Debug	WAS::associateAECDevice-leave	
    29-Dec-16 19:13:00	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2477 ms 2000	
    29-Dec-16 19:13:00	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2477 ms 2000	
    29-Dec-16 19:14:04	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 5689 ms 2000	
    29-Dec-16 19:14:04	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 5689 ms 2000	
    29-Dec-16 19:17:00		Info	Memory usage: 70.83 MiB	
    29-Dec-16 19:19:56	Newsticker	Info	Newsticker next check: Fri Dec 30 08:19:57 2016	
    29-Dec-16 19:20:06	Newsticker	Info	Newsticker next check: Fri Dec 30 08:19:57 2016	
    29-Dec-16 19:20:07	Newsticker	Info	Newsticker received for language en, expires on Fri Dec 30 08:50:06 2016, next check in 1800 seconds	
    29-Dec-16 19:24:09	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 269	
    29-Dec-16 19:27:43	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2021 ms 2000	
    29-Dec-16 19:27:43	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2027 ms 2000	
    29-Dec-16 19:27:45	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2146 ms 2000	
    29-Dec-16 19:27:45	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2147 ms 2000	
    29-Dec-16 19:28:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2992 ms 2000	
    29-Dec-16 19:28:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2992 ms 2000	
    29-Dec-16 19:28:06	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2685 ms 2000	
    29-Dec-16 19:28:06	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2685 ms 2000	
    29-Dec-16 19:29:36	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2169 ms 2000	
    29-Dec-16 19:29:36	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2169 ms 2000	
    29-Dec-16 19:30:47	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2932 ms 2000	
    29-Dec-16 19:30:47	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2932 ms 2000	
    29-Dec-16 19:31:17	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 5179 ms 2000	
    29-Dec-16 19:31:17	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 5179 ms 2000	
    29-Dec-16 19:32:00		Info	Memory usage: 52.73 MiB	
    29-Dec-16 19:34:56	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 63	
    29-Dec-16 19:47:00		Info	Memory usage: 51.01 MiB	
    29-Dec-16 19:50:07	Newsticker	Info	Newsticker next check: Fri Dec 30 08:50:06 2016	
    29-Dec-16 19:50:08	Newsticker	Info	Newsticker received for language en, expires on Fri Dec 30 09:20:07 2016, next check in 1800 seconds	
    29-Dec-16 19:52:02	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2136 ms 2000	
    29-Dec-16 19:52:02	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2445 ms 2000	
    29-Dec-16 19:52:48	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 28	
    29-Dec-16 19:53:46	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2890 ms 2000	
    29-Dec-16 19:53:46	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2890 ms 2000	
    29-Dec-16 19:54:15	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 5541 ms 2000	
    29-Dec-16 19:54:15	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 5541 ms 2000	
    29-Dec-16 20:02:00		Info	Memory usage: 51.46 MiB	
    29-Dec-16 20:04:22	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 23	
    29-Dec-16 20:04:53	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2412 ms 2000	
    29-Dec-16 20:04:53	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2412 ms 2000	
    29-Dec-16 20:07:16	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2733 ms 2000	
    29-Dec-16 20:07:16	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2733 ms 2000	
    29-Dec-16 20:07:54	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 3175 ms 2000	
    29-Dec-16 20:07:54	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 3175 ms 2000	
    29-Dec-16 20:07:57	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2307 ms 2000	
    29-Dec-16 20:07:57	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2307 ms 2000	
    29-Dec-16 20:08:21	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 5379 ms 2000	
    29-Dec-16 20:08:21	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 5379 ms 2000

  2. #2
    Join Date
    June 2014
    Posts
    6
    Downgraded to Teamspeak 3.0.19.2 (23-Jun-16 00:16:25), still have this issue and this is the last stable build I can run for teamspeak otherwise my mic is very highpitched for some reason.

    Tried the capture mode "Direct Sound" and the issue still happens, I'm quite at a loss on what to do but in the meantime I'm using my old mic but I would really like to know why teamspeak doesn't like my headset mic.

  3. #3
    Join Date
    May 2016
    Location
    Idar-Oberstein
    Posts
    163
    Hi mikenzb,
    the client log complains that the recorder thread is behind schedule.
    This tells us two things, first as already suspected by you, your CPU is at it's limit when this happens.
    Second, in case you weren't recording on purpose, you might wanna check if you have set a conflicting hotkey in your game (recording is ctrl-shift-r to start, ctrl-shift-t to stop - triggered only when TS is the active window).

    High pitched voice:
    We had a bug in an earlier beta that would cause that, to my knowledge this has all been solved.
    If it happens with the current beta, it'd be interesting to know what is selected in the windows sound setup -> capture device -> properties -> advanced tab -> standard format.

  4. #4
    Join Date
    June 2014
    Posts
    6
    Quote Originally Posted by thorwe View Post
    Hi mikenzb,
    the client log complains that the recorder thread is behind schedule.
    This tells us two things, first as already suspected by you, your CPU is at it's limit when this happens.
    Second, in case you weren't recording on purpose, you might wanna check if you have set a conflicting hotkey in your game (recording is ctrl-shift-r to start, ctrl-shift-t to stop - triggered only when TS is the active window).
    The very odd thing is I have switched back to my old mic which is coming in from the 3.5mm mic jack and I have not yet had the same issues that occurred on my headset mic which leads me to think my CPU just can't handle the USB mic input which I'm not sure why as I looked in the client log and I still have very similar errors but at least my microphone doesn't freeze up on me, is there a difference in how teamspeak captures input from a normal 3.5mm jack compared to a USB soundcard/headset input?

    Example using my old mic which doesn't have the issue:
    Code:
    03-Jan-17 00:33:45	ClientUI	Info	Connect status: Connected	
    03-Jan-17 00:33:48	ClientUI	Info	Connect status: Establishing connection	
    03-Jan-17 00:33:48	UIHelpers	Info	setClientVolumeModifier: 4 5	
    03-Jan-17 00:33:48	ClientUI	Info	Connect status: Connection established	
    03-Jan-17 00:33:48	PermManager	Info	Loading permissions from cache	
    03-Jan-17 00:34:17	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 25	
    03-Jan-17 00:34:39	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2917 ms 2000	
    03-Jan-17 00:34:39	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2918 ms 2000	
    03-Jan-17 00:37:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 7149 ms 2000	
    03-Jan-17 00:37:03	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 7150 ms 2000	
    03-Jan-17 00:47:55		Info	Memory usage: 62.50 MiB	
    03-Jan-17 00:50:29	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2072 ms 2000	
    03-Jan-17 00:50:29	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2073 ms 2000	
    03-Jan-17 00:51:54	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2047 ms 2000	
    03-Jan-17 00:51:54	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2047 ms 2000	
    03-Jan-17 00:52:00	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2747 ms 2000	
    03-Jan-17 00:52:00	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2747 ms 2000	
    03-Jan-17 00:52:05	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 3023 ms 2000	
    03-Jan-17 00:52:05	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 3023 ms 2000	
    03-Jan-17 00:52:52	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2772 ms 2000	
    03-Jan-17 00:52:52	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2772 ms 2000	
    03-Jan-17 00:53:32	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 8322 ms 2000	
    03-Jan-17 00:53:32	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 8322 ms 2000	
    03-Jan-17 00:53:45	Newsticker	Info	Newsticker next check: Tue Jan 3 13:53:38 2017	
    03-Jan-17 00:53:49	Newsticker	Info	Newsticker received for language en, expires on Tue Jan 3 14:23:45 2017, next check in 1800 seconds	
    03-Jan-17 01:01:03	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 67	
    03-Jan-17 01:02:56		Info	Memory usage: 59.66 MiB	
    03-Jan-17 01:09:49	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 184	
    03-Jan-17 01:11:51	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 3227 ms 2000	
    03-Jan-17 01:11:51	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 3227 ms 2000	
    03-Jan-17 01:17:55		Info	Memory usage: 56.80 MiB	
    03-Jan-17 01:20:04	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 3768 ms 2000	
    03-Jan-17 01:20:04	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 3768 ms 2000	
    03-Jan-17 01:21:23	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2544 ms 2000	
    03-Jan-17 01:21:23	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2544 ms 2000	
    03-Jan-17 01:23:49	Newsticker	Info	Newsticker next check: Tue Jan 3 14:23:45 2017	
    03-Jan-17 01:23:50	Newsticker	Info	Newsticker received for language en, expires on Tue Jan 3 14:53:49 2017, next check in 1800 seconds	
    03-Jan-17 01:24:13	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2655 ms 2000	
    03-Jan-17 01:24:13	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2655 ms 2000	
    03-Jan-17 01:24:43	Windows Audio Session	Debug	RenderDeviceContext inner loop lasted > 20 ms 161	
    03-Jan-17 01:24:51	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2163 ms 2000	
    03-Jan-17 01:24:51	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2163 ms 2000	
    03-Jan-17 01:25:37	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2831 ms 2000	
    03-Jan-17 01:25:37	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2922 ms 2000	
    03-Jan-17 01:27:15	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2290 ms 2000	
    03-Jan-17 01:27:15	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2290 ms 2000	
    03-Jan-17 01:27:29	ClientUI	Info	LIMSTOPWATCH RecorderThread::run (wait): 2115 ms 2000	
    03-Jan-17 01:27:29	ClientUI	Info	LIMSTOPWATCH RecorderThread::run: 2115 ms 2000

    I use the "ALT" button as my push to talk key and it is very unlikely in world of warships I would press the CTRL+SHIFT+R key at all so that is very unlikely as even if I did I've been using my old mic for 3 years with the same push to talk key and have never had an issue before.

    What I might try is running teamspeak on the beta channel to see if it makes a difference however I don't expect much of a change, if worst come to worst I'll just keep using my old mic.

    Also any reason why I see this in my teamspeak log?
    Code:
    2017-01-03 09:21:26.227711|INFO    |InputDevices  |   |Input device name: Kingston Technology HID Device
    2017-01-03 09:21:26.227711|INFO    |InputDevices  |   |UNKNOWN DEVICE: VID_0951&PID_16A4&MI_03&COL02#7&1C94FA2&0&0001
    Last edited by mikenzb; January 3rd, 2017 at 09:23 AM.

  5. #5
    Join Date
    May 2016
    Location
    Idar-Oberstein
    Posts
    163
    There's no difference code wise, windows gives audio data to an application transparently of the technology used, i.e. there's no direct connection between a driver and the TS client, it's like driver <-> windows sound system <-> TS.

    Scratch the remark about the hotkey, I've looked around and it's not an indication that you're actually recording. However, the point of CPU time still stands.
    Information what those logs mean:
    LIMSTOPWATCH RecorderThread::run (wait): 8322 ms 2000
    Should be: way under 2s, which is the threshould of putting it in the log. Here it took 8 seconds instead.

    Windows Audio Session Debug RenderDeviceContext inner loop lasted > 20 ms 184
    Should be under 20ms, was 184ms.

    The log doesn't show any "actual" errors, besides these reports - hence it's probably your root cause.

    USB audio devices indeed tend to be a little more taxing than built-in devices. Could also be power related, as your system is already stressed. Potentially using a different usb port can help with that (note: avoid USB-3 ports with audio devices, tends to cause trouble).
    Most likely though the best measurement would be to find a way to reduce the CPU consumption of World of Warships on your system, in case the game offers an option of that sort.

    Edith:
    The input devices log is about (H)uman (I)nterface (D)evices, reported by the hotkey system when it looks for potential candidates to use. Can safely be ignored.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 6
    Last Post: March 1st, 2018, 11:57 AM
  2. Server randomly stops responding temporarily
    By Smeewth in forum Windows
    Replies: 0
    Last Post: August 12th, 2015, 02:13 PM
  3. Push-To-Talk randomly stops responding.
    By Celebrim in forum Client Support
    Replies: 1
    Last Post: May 23rd, 2011, 12:11 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •