Rockbox

Tasklist

FS#12049 - Rockbox Utility eSpeak support needs work

Attached to Project: Rockbox
Opened by Christian Blackburn (seier) - Thursday, 07 April 2011, 00:46 GMT
Last edited by Dominik Riebeling (bluebrother) - Friday, 22 April 2011, 15:43 GMT
Task Type Bugs
Category Rbutil
Status Closed
Assigned To No-one
Operating System Sansa AMSv2
Severity Low
Priority Normal
Reported Version Release 3.8.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I searched online for eSpeak, downloaded, and installed the current version. I specified in Rockbox the installation path to eSpeak and then Rbutil said my configuration was "OK". When I clicked test it brought up this elaborate TTS interface rather than just talking. If my configuration is "OK" then why doesn't it work? The answer seems obvious,the support for eSpeak isn't complete as of yet. If I select eSpeak and have it installed I shouldn't even have to specify the installation path providing it's at a default location. On Windows at least, that's C:\Program Files\eSpeak\. At the very least please make it to where if I do specify the path correctly that's all I need to create .Talk files.
This task depends upon

Closed by  Dominik Riebeling (bluebrother)
Friday, 22 April 2011, 15:43 GMT
Reason for closing:  Wont Fix
Additional comments about closing:  Reporters attitude needs work.

Report is useless and no response from reporter. Nothing to fix here, and if you don't like the "user (un)friendliness" of Rockbox Utility it's not a bug. There's always room for making things easier to use. Feel free to send patches.
Comment by Christian Blackburn (seier) - Thursday, 07 April 2011, 00:48 GMT
Here's a screenshot of Rockbox misleadingly saying my configuration is OK.
Comment by Dominik Riebeling (bluebrother) - Thursday, 07 April 2011, 06:32 GMT
Please post the output of the About / Troubleshooting / System Trace dialog after the problem occured. The screenshot is useless.

Besides, we do not support finding any TTS at its "default" location. While you consider that to be in c:\Program Files we would need to check c:\Programme on a german Windows installation, and possibly a lot of others on other localizations so detecting it is a WONTFIX (unless someone provides a patch for it. Detecting it in the system path is already implemented, and works fine on systems that have the espeak binary in their search path. This is not true for Windows.)

And last, configuring and using espeak on Windows works for me.
Comment by Nils Wallménius (nls) - Thursday, 07 April 2011, 07:59 GMT
There's %ProgramFiles% and %ProgramFiles(x86)% so only two places to look for default install path on most windows installs.
Comment by Dominik Riebeling (bluebrother) - Thursday, 07 April 2011, 17:32 GMT
If you use a standard install you can also access espeak via SAPI so no need to specify anything. Which means that checking any "default" locations is somewhat pointless as someone wanting to configure espeak himself is likely to not have it installed in the default location.

Loading...