Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 33

Thread: Crew Chief Doesn't Hear My Commands

  1. #21
    Junior Member
    Join Date
    May 2017
    Posts
    8
    Quote Originally Posted by SloweyGonzalez View Post
    Sparten got me sorted out on Discord. In case anyone else stumbles across this thread with the same problem:

    Right click speaker in system tray
    Open sound settings
    open input (mic) device properties
    click "additional device properties" (right side, under "Related Settings")
    Open "advanced" tab in the new window
    uncheck "allow applications to take exclusive control of this device"
    Do have issues as well that CC is not recognizing my commands although "Allow applications to take exclusive control of this device" is already disabled. Do have discord running in parallel but it is configured to listen only on push-to-talk which is mapped to a different button.

    Any other advise is highly appreciated. Did work great in the past. Not sure what changed

  2. #22
    Junior Member
    Join Date
    Jul 2020
    Posts
    2
    I too have the same issue. Have talk to chief mapped to a button everything works fine but once I start up Iracing it all stops working. CC seems to only recognise the PPT when it has active focus which it does not have as Iracing has it. If I click on CC when in Iracing it works but then I crash lol.

  3. #23
    Junior Member
    Join Date
    Aug 2020
    Posts
    1
    So any time I give a command or say chief he or it goes with to beeps and doesn't respond.

    I have read through this and turned down my mic but nothings working.

    Thank you

  4. #24
    Junior Member
    Join Date
    Sep 2020
    Posts
    2
    I have the same issue, push to talk button just wont work no matter what i map it to.

    Surely we are not the first to face this problem??

  5. #25
    Crew Chief Mega Corp CEO mr_belowski's Avatar
    Join Date
    Feb 2017
    Posts
    1,815
    If you're using Windows speech recognition (Property "prefer Windows speech recogniser" is enabled) then you need to complete the Windows speech training (all phases) using the mic you'll use while racing. The app will log attempts to make voice commands including which recogniser is doing the work, the recognition confidence and the threshold being used so it should help you track down what's going on.

    The app will use the default sound recording device as configured in the Windows Sounds control panel - ensure your mic is set to be the default before starting the app.

    Most commands won't work if you're not in a game session (because the app won't have data) but the "can you hear me?" command will work at any time (as long as you've started the app) - use this to check the wiring is correct

  6. #26
    Junior Member
    Join Date
    Sep 2020
    Posts
    2
    Thanks mr_belowski for the tip, I have since changed mine to prefer windows speech, done the speech training sessions a few times, and things are definitely working better for me now. A side problem for me is the mic on my astro A40 headset, barely hits 10% input volume at normal speaking volume and theres no way to increase - so I would say my problem is probably not related to crew chief itself.

    The long and short of it is now it works nearly every time, just have to learn the commands a bit better

  7. #27
    Junior Member
    Join Date
    Sep 2017
    Posts
    5
    Quote Originally Posted by Notoooriou5 View Post
    Thanks mr_belowski for the tip, I have since changed mine to prefer windows speech, done the speech training sessions a few times, and things are definitely working better for me now. A side problem for me is the mic on my astro A40 headset, barely hits 10% input volume at normal speaking volume and theres no way to increase - so I would say my problem is probably not related to crew chief itself.

    The long and short of it is now it works nearly every time, just have to learn the commands a bit better
    Can the voice commands be seen as a overlay in VR please? I have poor memory.

  8. #28
    Junior Member
    Join Date
    Mar 2021
    Posts
    1
    With old versions of Crew chief, he could understand me %90 of the times, since a year ago or so with newer versions, he only understands %20 of the times, having to keep repeating myself till he does.

  9. #29
    Junior Member
    Join Date
    Apr 2021
    Posts
    1
    I have spent most of my day trying to get CC to hear me. I am using a Razor blackshark V2 with synapse. I have read about every thread I can find, and tried every setting, uninstall/reinstall of CC, drivers, changed USB ports, changed mic gain, etc... I am out of answers and frustrated I can not use all of the cool features of CC. If anyone can see anything a miss in the below log, let me know.

    Loading screen opened
    22:51:36.684 : Set iRacing mode from previous launch
    22:51:36.686 : Starting app. Version: 4.15.2.3
    22:51:36.808 : Device name: Speakers (Realtek(R) Audio) Guid: {0.0.0.00000000}.{5cd1d763-7c16-4937-886e-d83c7675be78} DeviceWaveId 1
    22:51:36.808 : Device name: Realtek Digital Output (Realtek(R) Audio) Guid: {0.0.0.00000000}.{d0f5a002-e3d5-49f2-9e09-5ba908f57a4c} DeviceWaveId 2
    22:51:36.809 : Device name: Speakers (Razer USB Sound Card) Guid: {0.0.0.00000000}.{d789fb47-eaf4-4f22-9dc0-366d7bfbfb4e} DeviceWaveId 0
    22:51:36.809 : Device name: Speakers (THX Spatial Audio) Guid: {0.0.0.00000000}.{e33ca82e-4f38-4d57-be6e-c5b682a33cc2} DeviceWaveId 3
    22:51:36.809 : Detected saved message audio output device: Speakers (THX Spatial Audio)
    22:51:36.809 : Detected saved background audio output device: Speakers (THX Spatial Audio)
    22:51:36.842 : Device name: Microphone (Razer USB Sound Card) Guid: {0.0.1.00000000}.{bcd96a57-14e3-426d-9ee3-9b59569df386} DeviceWaveId 0
    22:51:36.842 : Detected saved audio input device: Microphone (Razer USB Sound Card)
    22:51:36.911 : nAudio output interface: WAVEOUT
    22:51:36.929 : Using sound pack version 185, driver names version 140 and personalisations version 147
    22:51:36.935 : Preparing sound effects
    22:51:36.937 : Prepare sound effects completed
    22:51:36.937 : Preparing driver names
    22:51:36.965 : Prepare driver names completed
    22:51:36.966 : Preparing personalisations for selected name John
    22:51:36.969 : Spotter Jim (default) has oval-specific sounds - these will be used for tracks marked as 'oval'
    22:51:36.970 : Prepare personalisations completed
    22:51:36.972 : Preparing voice messages
    22:51:37.159 : Prepare voice message completed
    22:51:37.160 : Finished preparing sounds cache, found 9990 driver names and 3020 sound sets. Loaded 426 message sounds
    22:51:37.160 : 324 sounds have personalisations
    22:51:37.220 : Reading driver name mappings
    22:51:37.221 : Read 2164 driver name mappings
    22:51:37.221 : Reading driver name mappings
    22:51:37.222 : Read 422 driver name mappings
    22:51:37.269 : Loading controller settings
    22:51:37.269 : Load controller settings complete
    22:51:37.274 : got language codes data countryToUse = "", langToUse = "en" langAndCountryToUse = ""
    22:51:37.306 : Successfully initialised preferred System SRE
    22:51:37.309 : Attempting to get recogniser for en
    22:51:37.309 : Got SRE for en-US
    22:51:37.315 : Speech engine initialized successfully.
    22:51:37.315 : Attempted to initialise speech engine - success = True
    22:51:37.411 : Device Connected - Name: "Driving: FANATEC Podium Wheel Base DD2" GUID: "1ee970a0-61a7-11eb-8006-444553540000"
    22:51:37.416 : Device Connected - Name: "Driving: FANATEC Podium Wheel Base DD2" GUID: "1eebe1a0-61a7-11eb-8007-444553540000"
    22:51:37.417 : Device Connected - Name: "Keyboard" GUID: "6f1d2b61-d5a0-11cf-bfc7-444553540000"
    22:51:37.435 : Loading screen closed
    22:51:37.442 : Checking for updates
    22:51:37.768 : Took 0.61s to lazy load remaining message sounds, there are now 9443 loaded message sounds
    22:51:37.768 : Skipped 101 sweary sounds
    22:51:38.215 : Got update data from primary URL:
    22:51:38.219 : Check for updates completed

    Any help would be appreciated!

  10. #30
    Crew Chief Mega Corp CEO mr_belowski's Avatar
    Join Date
    Feb 2017
    Posts
    1,815
    from the log, the speech recogniser has been successfully initialised so that part of the wiring / setup is OK. The issue is likely to be on the audio input side. CC will use the Windows default sound recording device (in the "sounds" control panel's Recording tab, ensure your microphone is set to the be default device - i.e. the only one with a green tick, restart CC after changing this). You may also need to tell Windows to allow apps to access your microphone - last time i checked this was in the Security settings page in the windows Settings app, but MS have a habit of moving stuff around

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Posting Permissions

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