VoxCommando
Help and Support (Using VoxCommando) => Windows 8 / 10 => Topic started by: macrho on January 18, 2014, 06:58:33 AM
-
...If you are sure you have languages installed that support speech recognition, then you may need to run as administrator.
This just started showing up after the blue. I'm on Win 8.1 64-bit, only recent changes are some Windows updates.
Running with admin privs shows the same message.
I've not added any new voices
-
After a 4th reboot I was actually able to get VC to open but when I attempted to test "WS Kate" on the General tab of options, I get an error:
Failed to create voice / speak:
ComException: Class not registered
-
I'm a bit confused about your posts ???
This just started showing up after the blue. I'm on Win 8.1 64-bit, only recent changes are some Windows updates.
Have you switched to a new Windows system?
Does VC works before you did any changes?
Which VC version?
After a 4th reboot I was actually able to get VC to open but when I attempted to test "WS Kate" on the General tab of options, I get an error
Reboot VC or Windows for 4 times?
Does the Windows speech recognition/TTS works?
-
Have you tried to disable UAC ?
Are you running VoxCommando as administrator? (I don't mean from an administrative account, I mean right click and choose "run as administrator".)
-
UAC is disabled
Yes, I'm running VoxCommando as administrator (right clicked)
-
Kalle's questions are all valid. You should answer them.
If it worked yesterday maybe you should do a system restore.
Windows 8 sucks.
-
It is also not clear now whether you have VC running OK and the only problem is TTS.
What is WS Kate? Do other voices work?
-
I'm a bit confused about your posts ???
Have you switched to a new Windows system?
Does VC works before you did any changes?
Which VC version?
Reboot VC or Windows for 4 times?
Does the Windows speech recognition/TTS works?
confused? Ok...
No, I have not switched to a new Windows system. It's been running for weeks now
In the last 2 days, when I reboot I get the error message about "No language suitable..."
I'm on 1.1.8.4
I didn't do any specific changes other than windows updates
I rebooted Windows 4 times
I'm observing different behavior on my 7th reboot: I still get the warning message, however, VoxCommando works
-
Ok, thanks for the info :)
-
Hi,
I installed windows 8.1 yesterday. When I launched VC for the first time ( 1.1.86 ) It said en-us not found switching to en-gb. After numerous restarts still no us option. This is ok for me because en-bb understands me ok as I'm australian. Perhaps its a regional setting issue ? Whilst win 8 is a poor attempt to mishmash a tablet interface on a PC, once I set it to boot into desktop mode and installed a 3rd party windows start button all is good.
cheers
Phil
-
I installed Start 8 on my 8.1 box and with the super fast boot off of my mSATA drive, I'm sold on it
Dumbest thing ever was to put a touch interface on top of it, I mean - they should have let people opt into it
It was even more shocked when I first connected to a Windows Server 2012 instance and found the same bloody interface on it
Anyway.. with the a start8 replacement, I like it but would like to get Aero back. No windows 7 for me
-
This is a "google" translation from german to english:
only for Windows 8.1: Direct boot into the desktop
In desktop mode, right-click the taskbar and select in the context menu "Properties".
Go up to the "Navigation" tab.
Under the category "Home" you have to a hook in front of the point "when logging in or close all apps instead of the Home Show Desktop".
Click below on the button "OK", you are the next time Windows starts immediately on the desktop.
Take a look here on page 17 : http://www.pcworld.com/article/2058330/windows-8-1-surprises-25-hidden-features-and-little-extras.html (http://www.pcworld.com/article/2058330/windows-8-1-surprises-25-hidden-features-and-little-extras.html)
I hope this will help ( I hate the Metro UI too)
-
Here is a video showing how to install language packs. I am using Windows 8.1 freshly installed. I don't yet have all the updates installed so I'll report back on whether that makes any difference.
I have UAC enabled and I am not running VC as administrator, but I am using an administrator account. I have no problems using any of the languages as long as the full language pack has been installed.
In case you are not sure how to download and install language packs correctly, please watch the video. :D
-
OK, I installed all available updates for Windows 8.1, even the optional ones, and still no problems starting VC and choosing any of the language packs that I installed, as shown in the video. So, no idea what was up with macrho's rig.
-
@Kalle:
I'm not sure if the translation is correct but I have "When I sign in or close all apps on a screen go to the desktop instead of Start" but nothing like the translation.
I did make sure that everything under Navigation was selected as shown in the screen shot on page 17 but upon reboot, I still had the language pack issue
@jitterjames:
I watched the video [ the music was trying to put me to sleep though ]
I went into VC options and en-US was set for Speech Recognition Language (I didn't have anything set for Display Language so set it to en-US as well)
When I went into time and language, I already had English (United States) listed so I installed a variant of the German language
finally, after doing that VoxCommando starts properly without any warnings
strange - wonder what happened?
-
I am having this same issue. Did installing a german tts file fix this for you?, can you elaborate.
-
I'm not sure how often macrho checks in to the forum. Can you be more specific when you say that you're "having the same issue"?
Are you saying that VC was working fine for you using Windows 8.1, until you installed some updates and then suddenly you started to receive the "no languages suitable for speech" message?
(I don't think macrho was referring to German TTS, but to the German language pack, though he's not very clear.)
If you can provide more details about your setup and the specific circumstances, maybe we can help.
-
I might have found out what was causing this error. I had my J River installation taking exclusive control of the sound card. This caused several issues including the error mentioned at the beginning of the thread and TSS didn't always output sound. After turning it off I could set voices properly and I could hear TTS all the time.
Hope this might help someone in the future.