Client does not recognize PTT keybind press

[Phelan]

I recently added an additional set of profiles for a specific server. I can connect successfully, hear all users, and successfully test my keybind for PTT. When I exit the Settings window and attempt to use the PTT hotkey, the client does not recognize the key press; the indicator next to my name does not light up.
The mic is working properly. I can see the Windows recording meter light up when I tap the mic and if I set my mic for continuous transmission or voice activation everyone can hear me loud and clear.
I have verified that the new profiles (identically named) are loaded in the Bookmark Management window, and selected under the various Self sub-menu options.

I tried creating the profiles both using the copy feature, and starting from scratch. Neither seems to make a difference.
Also note that the PTT hotkey is the default (Ctrl), both for the default profile and for the new profile.

The mic is a standard Logitech USB desktop mic on a stick.
See attached screenshot, Client Log, and DxDiag.

[SilentStorm]

Update to Client 3.0.7 (See Announcements) and if it still doesn't work, try using a different Hotkey Capture Mechanism. (Settings -> OPtions -> Hotkeys -> Bottom Left Dropdown)

[Phelan]

I updated to 3.07 and tried using the default settings first; no success. I then tried each of the Capture Mechanisms with a client restart between each change, but the client still does not recognize the keypress. I tried again without a client restart so that I could obtain a complete Capture Log. None of the Capture Mechanisms seem to have an impact; the client does not recognize the keypress in a live channel environment. All three Capture Mechanisms allow PTT when testing in the Capture Settings.
See attachments for verification and Client Log.

[SilentStorm]

Try starting TS3 as Admin

[Phelan]

No change while running as Admin.

[SilentStorm]

try a different Key then...

[PotaBlava]

Verify also that you don't have selected "Voice activation while using PTT".

Settings --> Options --> Capture --> In 'Advanced Options', verify that "Voice activation while using PTT" is unchecked.

[SilentStorm]

Verify also that you don't have selected "Voice activation while using PTT".

Settings --> Options --> Capture --> In 'Advanced Options', verify that "Voice activation while using PTT" is unchecked.

True, I assumed it wouldn't matter since he wrote in the OP that he could test his Settings successfully, however I just checked and the Settings Dialog indeed ignores that Option...

[Phelan]

Forgot to mention that in the original post. That's one of the first things I ruled out. Voice Activation while using PTT is not checked.
Editing the original hotkey in the Hotkeys section does not have an impact on the client's ability to recognize a keypress; I tried that too.

I have stumbled across the solution. The default hotkey works for either profile while testing but does not apply to the non-Default, active profile in a live channel environment. The hotkey is labeled as "(Default)", which leads users to believe that it is the default hotkey at first glance. However, through testing, I found that adding a new hotkey prompts users to select a profile to which it will be attached. The new hotkey adopts a new label with the profile's name, and applies to the profile it is associated with. PTT works in a live channel after adding this new hotkey and applying a profile to it.

It's pretty counter-intuitive that a profile built from scratch has a default PTT hotkey that applies only to the Default (name) profile, but in a nutshell that's exactly what is happening. It is especially confusing because the default hotkey, which has the "(Default)" label, does work for testing purposes while in the Capture options.

[dante696]

I see, what is wrong here on your Screenshots.
Your PTT Hotkey is set for the capture profile Default, but your Capture profile is Phelan.
The client waits for the capture profile Default, please fix this hotkey or add another for your own profile.

[Phelan]

As I said three days ago, I discovered that the Default tag was referring to a profile and not to be viewed as defining a default (original, standard) hotkey. The hotkey is created and linked to the Default profile by, well, default. In this case, that's a bit confusing.

Thank you for your input none the less, Dante. The issue is resolved and can be marked as such.