Author Topic: Audio issues  (Read 5114 times)

TheThingIs

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 278
    • HCS Voicepacks
Audio issues
« on: July 01, 2016, 04:28:50 PM »
Ok Gary, this is a weird one and I don't know if you'll be able to tell me what is going on.

I'm trying to separate va's output and input for mixing sounds and I'm using a program called voicemeeter. This creates virtual cables allowing you to control where you direct output and input. There's no control in VA directly of where to assign input and output (please add this) so I don't know what's going on. Using wdm I'm able to play all audio output from windows through the mixer, except VA. Issuing a command on a running profile I see the level meter in the mixer reacting to the sound but no sound is heard. If I edit the profile and play a sound then I hear it fine so these 2 must play differently somehow. If I switch legacy audio on then the sound does play on the running profile but I get a warning message "Legacy audio enabled. Unable to wait : C:\Program....soundfilename". What does this error mean? The program is also very useful as it allows me to adjust the gate on my mic which is helping to stop random commands being run.

Told you it was a weird one :p
The Singularity profile - One profile to rule them all and at HCS we bound them ;)

You see, TheThingIs, eventually you'll be allright.

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2832
Re: Audio issues
« Reply #1 on: July 07, 2016, 10:50:18 AM »
VoiceAttack uses Windows media components to do its thing (normally).  Using those components, VoiceAttack is only able to use the default output device.  The audio device that TTS uses can be changed (globally), but the media components are not so nice.  There is a feature in VA called, 'legacy audio' which uses the built-in sound player objects.  This was what VA used in the very beginning, but then if you wanted to do more things (like adjust volume, get the audio position, etc) you would need something like Windows media components.  I left in the functionality of what is now, 'legacy audio' for those that can't/won't install Windows media components.  If there are no components installed, VA will drop back into, 'legacy audio' mode... or you can select it yourself.  Since there is almost no functionality in legacy mode, you will get warnings like you got.

I have a mess of code written to allow VA to change the default audio device, it just needs to be integrated meaningfully.  Waiting on this full release before stuffing that code in ;)  Also looking at other methods of audio output and do away with, 'legacy audio' mode.

TheThingIs

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 278
    • HCS Voicepacks
Re: Audio issues
« Reply #2 on: July 13, 2016, 03:30:42 PM »
Thanks for the answer Gary, that at least allows me to understand what is going on. I look forward to you working on new audio features for the next version.
The Singularity profile - One profile to rule them all and at HCS we bound them ;)

You see, TheThingIs, eventually you'll be allright.