Recent Posts

Pages: 1 ... 8 9 [10]
91
Issues / Re: Say command and other text to speech not working.
« Last post by Pfeil on January 18, 2025, 03:06:48 PM »
If you hold the Windows key on your keyboard, press the "R" key, then release both and paste
Code: [Select]
control.exe /NAME Microsoft.TextToSpeechinto the "Open:" textbox and click "OK", what is listed in the "Voice selection" dropdown?
92
Issues / Say command and other text to speech not working.
« Last post by mbelew on January 18, 2025, 03:00:24 PM »
I have VoiceAttack 1.15 and Windows 10.  All of the general sound commands such as Play a sound work fine, but the Say something with text-to-speech command does not work and, the preview in setting up Sound Effects does not work.

I have tried multiple outputs, speakers, headphones, voicemeeter, etc with no luck. I have double-checked all of my settings in VoiceAttack and Windows 10 Settings> Time and Language > Speech. Changing voices and the preview voice work in Windows settings. Windows Narrator works fine as well.

Any idea what I need to change to get the Say something with text-to-speech command to work?

93
Feature Suggestions / Access VoiceAttack Options while in Compact Mode
« Last post by SemlerPDX on January 16, 2025, 02:35:16 PM »
I like to keep VoiceAttack in the compact mode most of the time, and find it tedious/cumbersome to exit compact mode anytime I want to access the main VoiceAttack Options menu because the wrench/spanner icon is hidden in compact mode.  I do have a handy voice command to toggle compact mode, but it's a minor QoL thing - the "click through" concept of having a pre- and post- task to perform when accessing VoiceAttack Options while favoring compact mode as a user.

I wanted to suggest that maybe it could be a line item at the very bottom of the menu we see when we right-click the VoiceAttack icon on the taskbar or system tray, just below 'Relocate to Primary Display' perhaps, such that we could then access it without leaving compact mode or altering the nice and neat GUI of the compact mode.

94
Issues / Re: volume issues
« Last post by arjepsen on January 14, 2025, 01:04:20 PM »
Hmm... not really.
In the bottom of the speech properties dialog where I can make a new profile, in the bottom, is a microphone part (with audio input, advanced, and configure microphone button.
When I speak in the microphone here, I dont see any level indication. If I tap the microphone (in the way I alsways tell my singing students they should never do) I do see some indication - but nothing when I just speak. So this indicates an input level that is too low.
But if I click the audio input button, go to the recording tab, and look at the level indicator of the microphone when I speak, it clearly peaks when I just raise my voice slightly over normal speaking.

I suspect the issue could be with the windows speech recognition - it seems that windows generally receives a fine full signal, but somehow the speech recognition gets a much lower signal.
95
Issues / Re: volume issues
« Last post by Pfeil on January 14, 2025, 12:50:14 PM »
That all looks in order (the majority being defaults anyway).


This issue is quite unusual, as the Microsoft SAPI speech recognition system doesn't have any volume controls, or methods for attenuating the volume.
There is no logical explanation as to why the input volume should differ between other applications and the speech recognition system, that I can think of.

The microphone setup wizard is also part of the Microsoft SAPI speech recognition system, so in that sense it does track that it would exhibit the same issue.


Something you can try, just in case, as it has helped with bizarre issues in the past, is to create a new speech recognition profile, and see if that makes any difference.
96
Issues / Re: volume issues
« Last post by arjepsen on January 14, 2025, 12:33:12 PM »
ok, here you go.
97
Issues / Re: volume issues
« Last post by Pfeil on January 14, 2025, 12:26:11 PM »
Click the wrench icon on VoiceAttack's main window, and on the "General" tab of the VoiceAttack options window click "System info >", choose "Generate Settings Summary", then "Write to File"; Save the file and upload it here (attach it to a post).
98
Issues / Re: volume issues
« Last post by arjepsen on January 14, 2025, 12:24:39 PM »
Thanks for the answer :-)

Yes it's set up for system default.
If I tap on the microphone, I can see voice attack is registering it.
It seems that the audio level that voice attack receives is much lower than what the "normal" system volume is - as per my test with audacity. The input volume seems quite high generally - borderline clipping, so I don't quite understand why it seems that voice attack gets so much lower input.
99
Issues / Re: volume issues
« Last post by Pfeil on January 14, 2025, 11:39:16 AM »
Have you checked to make sure VoiceAttack is configured to use the intended device?

E.G. is the "Windows Speech Recording Device" option on the "Recognition" tab of the VoiceAttack options window set to that device (or the "Default - "-prefixed device, if you want to use the Windows default multimedia recording device)?
100
Issues / volume issues
« Last post by arjepsen on January 14, 2025, 11:12:23 AM »
I bought voice attack recently, and have been using it with edcopilot.
I run my mic (shure sm57) into an audio interface, which passes it through an analog out to the mic input of my pc.

Today I moved the mic, since it was picking up too much noise from the keyboard.
In the process I must have done something wrong, because now I hardly get any input into voice attack.
In windows, when I go to additional microphone properties, and enables "Listen to this device" - the sound is perfectly clear - I can pretty much hear a mouse fart next door...) :-)
I also tried using the mic in the program audacity, and I can see the volume is close to overdriving...

So what have I done wrong, since voice attack seems to almost get no signal?
I have tried going to settings (wrench) -> recognition -> utilities -> microphone setup -> other and choosing next until the volume control is shown. Here it is the same thing - almost no signal.
Pages: 1 ... 8 9 [10]