Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Troubleshooting in Windows 7 #55

Open
juancadavid opened this issue May 14, 2017 · 12 comments
Open

Troubleshooting in Windows 7 #55

juancadavid opened this issue May 14, 2017 · 12 comments

Comments

@juancadavid
Copy link

Hello,

Succesfully installed in Windows 7. When running the example code (without the export part, of course), I get no sound. I see that in the windows volume mixer (see image below) a couple of "Windows power shell" volume scrollers appear but they disappear after a second, and I get the "text has been spoken" callback in the console, so no errors.
image

Any ideas? Thanks!

@tlhunter
Copy link
Collaborator

Can you manually create and run some speak commands using Powershell and let me know if it's audible? I'm unfamiliar with Windows and can't provide more details, unfortunately.

@juancadavid
Copy link
Author

juancadavid commented Jun 5, 2017

Hi! Thanks for your reply. I tried running this script on Powershell and it worked fine:
Add-Type -AssemblyName System.speech
$speak = New-Object System.Speech.Synthesis.SpeechSynthesizer
$speak.Speak('Hello...I am Arun')

Any ideas? Thanks!

@juancadavid
Copy link
Author

I just tried replacing in your script the argument in $speak.Speak(\'[Console]::In.ReadToEnd()\') to just speak a random string, and it works well. Seems like the problem comes from the \'[Console]::In.ReadToEnd()\'. What is that supposed to do?

@tlhunter
Copy link
Collaborator

tlhunter commented Nov 6, 2017

Sorry, @juancadavid, but I'm going to have to close this as cannot reproduce. Others are able to use this on Windows as well. If you are able to reproduce and can get more details on why it works please reopen a new issue.

@tlhunter tlhunter closed this as completed Nov 6, 2017
@jupanSH
Copy link

jupanSH commented Nov 17, 2017

I had the same problem.I find the childprocess.spawn is not executed in windows7.But I haven't find out the reason.Who know?

@tlhunter tlhunter reopened this Nov 17, 2017
@jupanSH
Copy link

jupanSH commented Nov 19, 2017

I update the powershell from 2.0 to 5.1。The sound has been out。

@tlhunter
Copy link
Collaborator

@jupanSH does the sound work correctly?

@jupanSH
Copy link

jupanSH commented Nov 21, 2017

yes

@tlhunter
Copy link
Collaborator

@juancadavid can you upgrade your version of Powershell and let us know if it resolves your issue?

@jupanSH
Copy link

jupanSH commented Nov 24, 2017

MY win7 is not win7 SP1 system,and the powershell version is 2.0.Firstly I update my system to SP1 ,then install .Net framework required by powershell 5.1.Last I can use say.js to speak the text correctly after poweshell 5.1 had been installed.

@tlhunter
Copy link
Collaborator

Awesome, good to hear. I'll update the documentation to specify the minimum version of powershell.

@MrAmericanMike
Copy link

Just for the record, installing PowerShell 5.1 also fixed the problem for me.
However on Windows 7, one thing that the provided examples assume when running the different voices code is that we are on Windows 10 I guess, as David and Zara are W10 voices, but on Windows 7 the only available is Anna.
Other than that, working really nice.
PD: Also that example plays one text on top of the other. Shouldn't it provide an example on how to wait until the previous text is over and then play the new one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants