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
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Still having this problem with 3.1.4 / 1.1, as well as with the last few patches as well (don't remember the earliest patch it occurred with).
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Hello,
So I'm struggling with an issue for a while now and I have tried many options in other topics before I'm posting this.
After a random time, my PTT hotkey does no longer work. When I click the button, the light does not show up and people can no longer hear me. When I go to Options I cannot set a new hotkey. Not a single key is accepted. Then I have to close Teamspeak and restart it. Teamspeak will however still stay active in the Task Manager, until I close it. The whole situation repeats itself about 5 to 7 times a night.
Things I tried:
-Changing the key from my mouse to my keyboard
-Go to hotkeys page in options and set it on mouse and keyboard only
-Unplug any other devices, besides my mouse and keyboard
-Tried a different headset (tried both USB and mini-jack)
-Tried reinstalling Teamspeak
-Tried to use compatibility mode up to Win7 (I'm using Win10)
-Reinstalled all the sound drivers I could find in device manager
-Running TS3 as Admin|
At some point I even reinstalled Win10, so it may be a hardware issue after all. I just would like to hear your thoughts, before I'm spending a lot of money on either Keyboard and Mouse or a new Motherboard. Could it be that my sound card is simply broken?
Is there any way I can see a log and see why it stops working?
Last edited by dante696; July 13th, 2017 at 10:42 AM. Reason: merged
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Hi Dante.
Thanks for the reply.
The log I'm getting:
I am not seeing anything interesting. Do you?Code:13-7-2017 17:45:07 Info TeamSpeak 3 Client 3.1.4.2 (2017-06-28 10:01:41) 13-7-2017 17:45:07 Info SystemInformation: Windows 7 (7600) x64 (AMD or Intel) Binary: 64bit 13-7-2017 17:45:07 Info Using hardware aes 13-7-2017 17:45:07 Direct Sound Debug setting timer resolution to 1ms - 13-7-2017 17:45:07 ClientUI Info OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (NVIDIA GeForce GTX 770 Direct3D11 vs_5_0 ps_5_0), Version: OpenGL ES 2.0 (ANGLE 2.1.99f075dade7c) 13-7-2017 17:45:07 Addons Info Checking for addon updates... 13-7-2017 17:45:07 Plugins Info Loading plugin: clientquery_plugin_win64.dll 13-7-2017 17:45:07 Query Info listening on 127.0.0.1:25639 13-7-2017 17:45:07 Plugins Info Loading plugin: task_force_radio_win64.dll 13-7-2017 17:45:07 task_force_radio Info registerPluginID: {52d27e78-4099-4ca6-b5d5-f6538eadae7f} 13-7-2017 17:45:07 Plugins Info Loading plugin: teamspeak_control_plugin_win64.dll 13-7-2017 17:45:07 Plugins Info Loading plugin: gamepad_joystick_win64.dll 13-7-2017 17:45:07 Addon Info Addon up to date. 13-7-2017 17:45:07 Addon Info Addon up to date. 13-7-2017 17:45:07 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList 13-7-2017 17:45:07 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList 13-7-2017 17:45:07 Addon Info Addon up to date. 13-7-2017 17:45:07 Info *** Time [SERVERVIEWMANAGER]: 124 13-7-2017 17:45:08 Info *** Time [MAINWINDOW]: 565 13-7-2017 17:45:08 Info *** Time [INIT]: 566 13-7-2017 17:45:08 ClientUI Devel Notifications init: Soundpack path: C:/Program Files/TeamSpeak 3 Client/sound\default 13-7-2017 17:45:08 ClientUI Info Qt version: 5.6.1 13-7-2017 17:45:08 ClientUI Info Using configuration location: C:\Users\faces\AppData\Roaming\TS3Client\settings.db 13-7-2017 17:45:08 ClientUI Info Last update check was: do jul 13 08:05:48 2017 13-7-2017 17:45:08 Info Statistics report: Not yet, next report on ma jul 24 15:09:10 2017 13-7-2017 17:45:08 Bookmarks Info Collecting autoconnect bookmarks 13-7-2017 17:45:09 Newsticker Info Newsticker next check: do jul 13 20:37:23 2017 13-7-2017 17:45:09 ClientUI Info Connect to server: 144.76.2.143 13-7-2017 17:45:09 ClientUI Info Blacklist check ok 13-7-2017 17:45:09 ClientUI Info Initiating connection: 144.76.2.143:10000 13-7-2017 17:45:09 TSDNS Info A/AAAA DNS resolve successful, "blacklist.teamspeak.com" =(h: 46.105.112.65 p:0) 13-7-2017 17:45:09 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList 13-7-2017 17:45:09 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList 13-7-2017 17:45:09 Windows Audio Session Debug WAS::openDevice-enter - {0.0.0.00000000}.{80b13647-e53b-4b21-8d14-c46243df3ea8} 13-7-2017 17:45:09 Windows Audio Session Devel Format detected: Multichannel capable Float - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Info Initialized with 2 channels in 16bit, 48kHz. - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Devel WAS Buffer size: 1056 - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Debug WAS::openDevice-leave - {0.0.0.00000000}.{80b13647-e53b-4b21-8d14-c46243df3ea8} 13-7-2017 17:45:09 Windows Audio Session Debug WAS::startDevice-enter - {0.0.0.00000000}.{80b13647-e53b-4b21-8d14-c46243df3ea8} 13-7-2017 17:45:09 Windows Audio Session Debug WAS::startDevice-leave - {0.0.0.00000000}.{80b13647-e53b-4b21-8d14-c46243df3ea8} 13-7-2017 17:45:09 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList 13-7-2017 17:45:09 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList 13-7-2017 17:45:09 Windows Audio Session Debug WAS::openDevice-enter - {0.0.1.00000000}.{979b1cc4-8d69-443f-9f98-e02fed720280} 13-7-2017 17:45:09 Windows Audio Session Devel Format detected: Multichannel capable Float - Microfoon (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Info Initialized with 2 channels in 16bit, 48kHz. - Microfoon (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Devel WAS Buffer size: 1058 - Microfoon (Sennheiser SC60 Control) 13-7-2017 17:45:09 Windows Audio Session Debug WAS::openDevice-leave - {0.0.1.00000000}.{979b1cc4-8d69-443f-9f98-e02fed720280} 13-7-2017 17:45:09 PreProSpeex Info Speex version: speex-1.2beta3 13-7-2017 17:45:09 Windows Audio Session Debug WAS::startDevice-enter - {0.0.1.00000000}.{979b1cc4-8d69-443f-9f98-e02fed720280} 13-7-2017 17:45:09 Windows Audio Session Debug WAS::startDevice-leave - {0.0.1.00000000}.{979b1cc4-8d69-443f-9f98-e02fed720280} 13-7-2017 17:45:09 ClientUI Info Connect status: Connecting 13-7-2017 17:45:09 PktHandler Devel Puzzle solve time: 5 13-7-2017 17:45:09 ClientUI Info Connect status: Connected 13-7-2017 17:45:09 Windows Audio Session Debug [Playback] RenderDeviceContext inner loop lasted > 20 ms 24 - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:10 Windows Audio Session Debug [Playback] Got 3 or more rendering spaces in same loop 480 1056 576 - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:10 Windows Audio Session Debug [Playback] RenderDeviceContext inner loop lasted > 20 ms 21 - Luidsprekers (Sennheiser SC60 Control) 13-7-2017 17:45:10 ClientUI Info Connect status: Establishing connection 13-7-2017 17:45:10 ClientUI Info Connect status: Connection established 13-7-2017 17:45:10 PermManager Info Loading permissions from cache 13-7-2017 17:45:11 Info Failed to download remote image: Error transferring http://img62.imageshack.us/img62/3996/izoq.png - server replied: Not Found 203 13-7-2017 18:00:08 Info Memory usage: 158.57 MiB 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:44 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:45 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:46 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:47 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:47 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:47 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:00:47 task_force_radio Info can't center client : invalid clientID 13-7-2017 18:15:08 Info Memory usage: 85.45 MiB 13-7-2017 18:30:08 Info Memory usage: 87.32 MiB 13-7-2017 18:37:23 Newsticker Info Newsticker next check: do jul 13 20:37:23 2017 13-7-2017 18:37:33 Newsticker Info Newsticker next check: do jul 13 20:37:23 2017 13-7-2017 18:37:33 Newsticker Info Newsticker not found for language nl 13-7-2017 18:37:33 Newsticker Info Newsticker received for language nl, expires on do jul 13 21:07:33 2017, next check in 1800 seconds
I am using an ancient Microsoft keyboard that used to be white. My mouse is a Trust GXT 33.
I have no further hardware plugged in right now.
My current headphones are Sennheiser SC60.
The log displays the usage of Task Force Radio. This is also happening when Task Force Radio is not enabled or even installed.
Thank you for the fast feedback
Nope the log doesn't show something related to the problem.
We still have no clue then why this happens to you ;(
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Found the issue and I thought you might be interested to know.
So it turned out my Windows Time was off as well. Via the settings the time stopped counting. Since I never use that clock I never noticed. I even had to go as far as to replace the motherboard battery. Interestingly enough that also solved my PTT issues.
I have no idea about how this may affect only the PTT function of Teamspeak, while direct voice chat or activate on speaking worked just fine. So far my issues have been resolved.
I've been having this issue for the last 6 months or so and for me it's not a Windows time issue. It has persisted through reformatting and 2 different TeamSpeak versions and happens on every server I connect to. I've attached a client log although it doesn't seem to show anything. Push to talk works fine for awhile (not always the same amount of time) and then will randomly refuse to work. The push to talk button (`) is working and I can type it into the chat window, but it will not recognize it as a push to talk keybinding.
I also have this problem - started for the first time last night; never had problems previously with TS (I have been running version 3.1.7 without problems since it was released).
The only thing that changed since I last used TS (12th Jan) is my PC was fully unplugged and then replugged - so all physical connections were disconnected and reconnected; I can't guarantee that every USB went back into the USB port it came out of, but that is the only thing that I'm aware of that has changed.
Help! I play online using TS 2-3 times a week; not having it is not an option!
Thanks
Teamspeak has always worked for years on my pc and suddenly I got this very annoying PTT error.
Today it was a rainy day so I decided to stay at home and spend 8 hours to find the root cause of this problem.
I havent been using Teamspeak for about a month and after logging on to my favourite server my PTT randomly stopped working after a few minutes. After going to the Teamspeak sound capture options I tried to change recording device from my desktop microphone to default and I did a mic test and it worked....for about 1 minute and then the problem repeated itself...
I tried closing and restarting Teamspeak and then mic worked for about a minute and after a minute the problem rose again.
recap:
I tried reinstalling my soundcard drivers > No result
I tried re-installing Teamspeak > no result
I tried reinstalling Nvidia HD audio driver > No result
I tried disabling all devices in windows hardware manager except the mic > no result
I searched on Google for a solution to problem "PTT stops working in teamspeak after few minutes" > none of the provided solutions worked
I disconnected my mic and reconnected > no result
I disabled all addons in Teamspeak > no result
I reinstalled usb drivers > no result
I tried running Teamspeak as admin > no result
I tried to change my PTT key to different keystrokes > no result
I tried to run Teamspeak in Win7 compatibility mode > no result
Finally after around 8 hours I realized that I cleaned the room last month and I detached all usb cables from my PC. I then tried to switch my microphone from a usb 3.0 to a usb 2.0 input and VOILA > PROBLEM SOLVED!!!
I took the time to share this with you guys so I hope this solution will work for more ppl who encounter this issue.
If it worked for you, id appreciate a reply![]()
For me I switched from a Snowball to a Blue Yeti and when I did this started happening to me.. After looking into it.. I found out that when I moved the microphone from being plugged into the USB of my monitor to the USB of my computer that it no longer did that.
The fix.. Make sure to plug it into something that doesnt go into powersave mode like a monitor. For some reason that messes up Teamspeak from using it until restarted.
There are currently 1 users browsing this thread. (0 members and 1 guests)