Announcement

Collapse
No announcement yet.

Astra

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Astra

    Hello, every time i use voice attack, after about 20 mins Astra doesn't always respond to my voice( have to say things twice or 3 times). Its like there is some kind of memory leak within windows 7 that slows down the effectiveness of the speech. What i do is restart voice attack then its fine again for a while. Have you ever come across this? I don't think its a pc issue as I have a powerful pc regards Steve

  • #2
    okay which profile are you using first and we can see what we can do ^_^
    Last edited by ForumAdmin; 24 March 2015, 11:03 PM.

    Comment


    • #3


      Did i quick look into it myself , found this post by Gary who makes voice attack himself . Hope this helpful
      The link is below :-)
      https://groups.google.com/forum/#!to...ck/N8sDZyJFj8E

      woolfoma
      26/10/2014


      whenever I have voice attack open and I am not talking or there is no noise, "Windows Audio Device Graph Isolation" starts consuming .02 - .04 mb of ram per second.
      I know it doesn't seem like much of a leak, but I have had it tally up to 12 - 14 gb of ram causing my computer to become unresponsive and I am unable to do anything but kill the power to my computer



      Gary
      27/10/2014


      Hi, Woolfoma.

      I have had VoiceAttack running for days straight without any issue like this. I did a quick Google search for, 'Windows Audio Device Graph Isolation memory leak' and it may lend itself to faulty sound card drivers (and some cases even the enhancements turned on for your sound card may be causing the problem). You might want to do this search yourself and include your version of Windows in that search (may vary by version).

      Hope that helps!

      Gary


      On Sunday, October 26, 2014 6:01:49 PM UTC-5, woolfoma wrote:
      whenever I have voice attack open and I am not talking or there is no noise, "Windows Audio Device Graph Isolation" starts consuming .02 - .04 mb of ram per second.
      I know it doesn't seem like much of a leak, but I have had it tally up to 12 - 14 gb of ram causing my computer to become unresponsive and I am unable to do anything but kill the power to my computer



      woolfoma
      30/11/2014


      I just got the new Beta out of curiosity (more like begging on my hands and knees) that this issue might be fixed for me. and magically it was
      don't know what you did with the new beta but now voice attack doesn't do that memory leak thing and I can keep it running 24-7 to do things outside of my video game






      Last edited by ForumAdmin; 24 March 2015, 11:13 PM.

      Comment


      • #4
        Hey numpski
        If Rega's ideas are not the answer try this. I have read that Microsoft's speech recognition engine can get messed up on occasion. Some people have had to create a new speech profile and re train it. Go to Control Panel/Speech Recognition/Advanced speech options and create a new profile. Then Train the profile with your normal voice. It's a good idea to go through the training at least 3 times. Not sure if this will help but give it a shot.

        Fixx

        Comment


        • #5
          Thanks for all your replys I dont lose any performance at all, I dont think its a profile prob because as soon as I restart voice attack its fine again for another 20 mins or so. To try to explain the problem i'm facing a bit better. For the 1st 20 mins my mike is say 10 cm away from my mouth and astra responds to all my commands 1st time everytime. Then after 20 mins or so my commands are ignored until I place the mike 3cm away from me then its 50/50 weather the command is heared. As soon as I restart VA it goes back to being normal ie mike 20cm away and all commands recognised once again. I'm using realtec onboard sound and it just seems to be this that causes a problem. Windows Audio Device Graph Isolation does start when I start VA

          Comment


          • #6
            I have found this to be a product of a command failing to complete. The solution I use is to pause the game, Alt-Tab to desktop, open VoiceAttack and click on the Stop Command icon. This clears the stuck command and VoiceAttack then runs all the other commands that came after it (you can keep clicking stop command to clear them all). When you go back in game, you should then call for system diagnostics to reset all the toggle variables then check that all the functions are synchronised with the voice responses. E.g. call for gear down and see if ASTRA responds "Gear Deployed" or equivalent. You will need to be in space to perform some of the functions.
            If you were docked at a station when you did the system diagnostic and some of the functions are out of sync, then go into space and execute the command again. If this does not work, re-dock and pause the game, Alt tab to desktop and close-reopen VoiceAttack. Alt-Tab back to the game and resume.

            Hope this is useful.

            Comment


            • #7
              Originally posted by numpski View Post
              Thanks for all your replys I dont lose any performance at all, I dont think its a profile prob because as soon as I restart voice attack its fine again for another 20 mins or so. To try to explain the problem i'm facing a bit better. For the 1st 20 mins my mike is say 10 cm away from my mouth and astra responds to all my commands 1st time everytime. Then after 20 mins or so my commands are ignored until I place the mike 3cm away from me then its 50/50 weather the command is heared. As soon as I restart VA it goes back to being normal ie mike 20cm away and all commands recognised once again. I'm using realtec onboard sound and it just seems to be this that causes a problem. Windows Audio Device Graph Isolation does start when I start VA
              It could be worth ticking the "Disable Adaptive Recognition" box in the setting for VA, and seeing how that goes.

              Even though the microphone can be recognised from a distance, it cannot be 100% of the time accurate especially the more ambient noise there is. Creaks, the sound of the computer fan, keyboard/presses can all influence this. This is why the setup guide for Voice controls in windows recommends a headset mic to be 1inch away from the mouth. This is the distance where the human voice will typically overpower the other sounds that a mic can pick up.
              1) I reject your reality.... and substitute my own
              2) Not to be used when upset... will void warranty
              3) Stoke me a clipper i will be back for dinner
              4) Never tell Gangrel to do anything... he will probably get it wrong
              WARNING! Swedish wall-of-text hits you for bork-bork-bork damage!

              Comment

              Working...
              X