So I remembered that i had not gone through the speech recognition training after reinstalling windows(I had done it before when i first started having the issues before the reinstall), so I gave that a shot to see if it would help. This is the result of two yawns followed by me actually saying the trigger word(in bold).
Code:
17:26:39.481 : Heard keyword Chief, waiting for command confidence 0.9845313
17:26:39.532 : Opened channel - waiting for speech
17:26:39.532 : Getting audio from default device
17:26:44.850 : Gave up waiting for voice command, now waiting for trigger word Chief
17:26:47.946 : Heard keyword Chief, waiting for command confidence 0.9871724
17:26:47.998 : Opened channel - waiting for speech
17:26:47.998 : Getting audio from default device
17:26:53.333 : Gave up waiting for voice command, now waiting for trigger word Chief
17:26:57.280 : Heard keyword Chief, waiting for command confidence 0.9899238
17:26:57.331 : Opened channel - waiting for speech
I then restarted CC and started getting better results. Not sure if this is related, but it seems if you do the speech training while cc is running you need to restart cc for it to take effect. Yawns are no longer setting it off, however any word that resembles chief, such as see, or cheese, etc, still occasionally set it off, but i assume thats to be expected when chief is throwing 0.95 and cheese is 0.949 theres likely to be some overlap there. I've dropped from 0.98 recognition for most sounds to .89-.94 for words resembling the trigger word. I set the trigger word confidence to 0.95 and that seems to be helping, as long as i don't get into a conversation about cheese while i'm racing. Thanks for the help