* Trouble with speech dispatcher.
@ Satyam
` Tomas Cerha
` (2 more replies)
0 siblings, 3 replies; 22+ messages in thread
From: Satyam @ UTC (permalink / raw)
To: speakup
Dear all,
I installed speakup modified Fc3 and planning to use speakup using
software synth. As per the instructions given in the howto install
speakup guide I downloaded speech dispatcher 0.6 and
festival-freebsoft-utils-0.6 After careful reading the install document
of speech dispatcher I issued the command
Make all
Then I am getting the following error: No rule to make target all.stop
What is the cause for this message and how to rectify it.
Hope to hear from you.
Satyam.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: Trouble with speech dispatcher. Trouble with speech dispatcher Satyam @ ` Tomas Cerha ` Willem van der Walt ` Hynek Hanke 2 siblings, 0 replies; 22+ messages in thread From: Tomas Cerha @ UTC (permalink / raw) To: satyanarayanamurthy.tanikella, Speakup is a screen review system for Linux. Satyam napsal(a): > After careful reading the install document > of speech dispatcher I issued the command > Make all > Then I am getting the following error: No rule to make target all.stop Hi Satym, you should run "./configure" first. I checked the INSTALL document and I see it is not clear from it, so I CC this to Hynek, since he might want to fix that. > What is the cause for this message and how to rectify it. The cause is that you don't have the Makefile, which drives the build process. The Makefile is created by running the ./configure script. This is a common method, and is generally applied when building any C software from source on Linux. Best regards, Tomas. PS: It would be definitely nice to find someone willing to maintain Fedora binary packages of Speech Dispatcher... -- Brailcom, o.p.s. http://www.brailcom.org Free(b)soft project http://www.freebsoft.org Eurochance project http://eurochance.brailcom.org ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. Trouble with speech dispatcher Satyam ` Tomas Cerha @ ` Willem van der Walt ` Hynek Hanke 2 siblings, 0 replies; 22+ messages in thread From: Willem van der Walt @ UTC (permalink / raw) To: satyanarayanamurthy.tanikella, Speakup is a screen review system for Linux. You should extract speech-dispatcher, change to its directory, do ./configure&&make&&make install Note the punctuation in the line above. You also need speechd-up which you can also get where you got speech-dispatcher. I think it also requires dotconf. HTH Willem On Wed, 17 May 2006, Satyam wrote: > Dear all, > I installed speakup modified Fc3 and planning to use speakup using > software synth. As per the instructions given in the howto install > speakup guide I downloaded speech dispatcher 0.6 and > festival-freebsoft-utils-0.6 After careful reading the install document > of speech dispatcher I issued the command > Make all > Then I am getting the following error: No rule to make target all.stop > What is the cause for this message and how to rectify it. > Hope to hear from you. > Satyam. > > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006 > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to HelpDesk@csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. Trouble with speech dispatcher Satyam ` Tomas Cerha ` Willem van der Walt @ ` Hynek Hanke ` Steve Holmes ` Satyam 2 siblings, 2 replies; 22+ messages in thread From: Hynek Hanke @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Cc: satyanarayanamurthy.tanikella Satyam píše v St 17. 05. 2006 v 08:34 +0530: > After careful reading the install document of speech dispatcher I issued > the command > Make all > Then I am getting the following error: No rule to make target all.stop Hello, you need to first call ./configure then make all I've just fixed the INSTALL document, sorry for the trouble. Have a nice day, Hynek ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Hynek Hanke @ ` Steve Holmes ` Michael Whapples ` Satyam 1 sibling, 1 reply; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 More specificly, I'm having trouble with speechd-up. It says it cannot find /dev/softsynth. Well, I have had that device all along and I just now rebuilt it in case there was something wrong and I still have the problem. I'm now using Speakup from latest CVS with kernel 2.6.16.12, Speech-dispatcher 0.6 and speechd-up 0.3. I should point out that I was using this stuff a month or so ago with Dectalk speech and no problems at that time. I will now include the log from /var/log/speechd-up.log - ----- Beginning of log ----- [Wed May 17 00:19:57 2006] speechd: Speechd-speakup starts! [Wed May 17 00:19:57 2006] speechd: Error while openning the device in read/write mode 19,No such device [Wed May 17 00:19:57 2006] speechd: Trying to open the device in the old way. [Wed May 17 00:19:57 2006] speechd: Error while openning the device in read mode 19,No such device [Wed May 17 00:19:57 2006] speechd: ERROR! Unable to open soft synth device (/dev/softsynth) - ----- End of log ----- Yes, if I do a ls -l on /dev/softsynth, I get the following: crw-rw-rw- 1 root root 10, 26 2006-05-17 00:18 softsynth This is inside the /dev directory. I get same errors whether I try using Dectalk, flite or now espeak. In fact, I manually tested espeak through the spd-say command and that part does work. So it is the soft synth problem that I can't figure out. - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEatI0WSjv55S0LfERA2w2AJ4kTUO40dtscRE5bnYFpp/Oe6wCogCfY7Fd KV344ueqi1HXvxSpWVhz6qk= =OkwR -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes @ ` Michael Whapples ` Steve Holmes 0 siblings, 1 reply; 22+ messages in thread From: Michael Whapples @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. I know this may seem obvious, but have you changed speakup to sftsyn before trying to start speechd-up? (I have tried to get my email client to try and connect to hotwayd, but forgotten to start it, and then it suddenly dawned on me). I found that it doesn't always start unless that is done. Don't know if that would give the error you are saying about in the log, but worth a try. From Michael Whapples ----- Original Message ----- From: "Steve Holmes" <steve@holmesgrown.com> To: <speakup@braille.uwo.ca> Sent: Wednesday, May 17, 2006 8:35 AM Subject: Re: Trouble with speech dispatcher. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > More specificly, I'm having trouble with speechd-up. It says it cannot > find /dev/softsynth. Well, I have had that device all along and I just > now rebuilt it in case there was something wrong and I still have the > problem. I'm now using Speakup from latest CVS with kernel 2.6.16.12, > Speech-dispatcher 0.6 and speechd-up 0.3. I should point out that I was > using this stuff a month or so ago with Dectalk speech and no problems > at that time. I will now include the log from /var/log/speechd-up.log > - ----- Beginning of log ----- > [Wed May 17 00:19:57 2006] speechd: Speechd-speakup starts! > [Wed May 17 00:19:57 2006] speechd: Error while openning the device in > read/write mode 19,No such device > [Wed May 17 00:19:57 2006] speechd: Trying to open the device in the old > way. > [Wed May 17 00:19:57 2006] speechd: Error while openning the device in > read mode 19,No such device > [Wed May 17 00:19:57 2006] speechd: ERROR! Unable to open soft synth > device (/dev/softsynth) > - ----- End of log ----- > Yes, if I do a ls -l on /dev/softsynth, I get the following: > crw-rw-rw- 1 root root 10, 26 2006-05-17 00:18 softsynth > This is inside the /dev directory. > > I get same errors whether I try using Dectalk, flite or now espeak. In > fact, I manually tested espeak through the spd-say command and that part > does work. So it is the soft synth problem that I can't figure out. > > - -- > HolmesGrown Solutions > The best solutions for the best price! > http://ld.net/?holmesgrown > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.7 (GNU/Linux) > > iD8DBQFEatI0WSjv55S0LfERA2w2AJ4kTUO40dtscRE5bnYFpp/Oe6wCogCfY7Fd > KV344ueqi1HXvxSpWVhz6qk= > =OkwR > -----END PGP SIGNATURE----- > > > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Michael Whapples @ ` Steve Holmes ` Hynek Hanke 0 siblings, 1 reply; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I used the same shell script I've always been using. The only thing that really changed was Speakup version; wonder if that could have anything to do with it? I echo "none" to /proc/speakup/synth_name unload any modules then start speechd-up and speech dispatcher in proper order and then echo sftsyn to synth_name again. Oops, I am raddling this off the top of my head but I think speakup's synth is being set first and then speechd-up is started. No matter, I'm using the same script I used a month or two ago and it worked then but not now <sigh>. Maybe I'll have to go and try and run each of those steps manually with a second or two to spare between each. I'm just baffled that it can't find /dev/softsynth when it is *REALLY THERE*. On Wed, May 17, 2006 at 05:32:42PM +0100, Michael Whapples wrote: > I know this may seem obvious, but have you changed speakup to sftsyn before > trying to start speechd-up? (I have tried to get my email client to try and > connect to hotwayd, but forgotten to start it, and then it suddenly dawned > on me). I found that it doesn't always start unless that is done. Don't know > if that would give the error you are saying about in the log, but worth a > try. > From > Michael Whapples > ----- Original Message ----- > From: "Steve Holmes" <steve@holmesgrown.com> > To: <speakup@braille.uwo.ca> > Sent: Wednesday, May 17, 2006 8:35 AM > Subject: Re: Trouble with speech dispatcher. > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: RIPEMD160 > > > > More specificly, I'm having trouble with speechd-up. It says it cannot > > find /dev/softsynth. Well, I have had that device all along and I just > > now rebuilt it in case there was something wrong and I still have the > > problem. I'm now using Speakup from latest CVS with kernel 2.6.16.12, > > Speech-dispatcher 0.6 and speechd-up 0.3. I should point out that I was > > using this stuff a month or so ago with Dectalk speech and no problems > > at that time. I will now include the log from /var/log/speechd-up.log > > - ----- Beginning of log ----- > > [Wed May 17 00:19:57 2006] speechd: Speechd-speakup starts! > > [Wed May 17 00:19:57 2006] speechd: Error while openning the device in > > read/write mode 19,No such device > > [Wed May 17 00:19:57 2006] speechd: Trying to open the device in the old > > way. > > [Wed May 17 00:19:57 2006] speechd: Error while openning the device in > > read mode 19,No such device > > [Wed May 17 00:19:57 2006] speechd: ERROR! Unable to open soft synth > > device (/dev/softsynth) > > - ----- End of log ----- > > Yes, if I do a ls -l on /dev/softsynth, I get the following: > > crw-rw-rw- 1 root root 10, 26 2006-05-17 00:18 softsynth > > This is inside the /dev directory. > > > > I get same errors whether I try using Dectalk, flite or now espeak. In > > fact, I manually tested espeak through the spd-say command and that part > > does work. So it is the soft synth problem that I can't figure out. > > > > - -- > > HolmesGrown Solutions > > The best solutions for the best price! > > http://ld.net/?holmesgrown > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.7 (GNU/Linux) > > > > iD8DBQFEatI0WSjv55S0LfERA2w2AJ4kTUO40dtscRE5bnYFpp/Oe6wCogCfY7Fd > > KV344ueqi1HXvxSpWVhz6qk= > > =OkwR > > -----END PGP SIGNATURE----- > > > > > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEa4zLWSjv55S0LfERA9GRAKDLv3JX4UVmDLQkGdeDNiHaB70/TgCfcK8F wQuDRTjz9+FE9wdZznQFE4s= =Zkgf -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes @ ` Hynek Hanke ` Steve Holmes 0 siblings, 1 reply; 22+ messages in thread From: Hynek Hanke @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Steve Holmes píše v St 17. 05. 2006 v 13:51 -0700: > I used the same shell script I've always been using. The only thing > that really changed was Speakup version; wonder if that could have > anything to do with it? Possibly yes. > Maybe I'll have to go and try and run each of those steps manually with a second > or two to spare between each. Yes. That would be useful. The only steps you need to do are: 1) load speakup 2) load the sftsyn module 3) start speechd-up Speech Dispatcher, Festival and other components have nothing to do with this. It is entirely between speechd-up and Speakup. > I'm just baffled that it can't find /dev/softsynth when it is *REALLY THERE*. It doesn't say it can't find it. It can't open it. Maybe it is there but it is not working for some reason. Yes, it is puzzling. I can't think of any reason why the system should refuse to open it as is apparent from the log files you sent, supposing sftsyn is loaded and the permissions are as you described. The best next step would be to try manually and make sure the sftsyn module gets fully loaded before speechd-up is started. Please let me know, Hynek Hanke ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Hynek Hanke @ ` Steve Holmes ` Gregory Nowak ` Trouble with speech dispatcher Sean M McMahon 0 siblings, 2 replies; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I think I'm on to something. I'm sorking this machine by remote ssh session so can't be totally sure but What I see so far is the sftsyn module is not being auto loaded when echoing "sftsyn" to /proc/speakup/synth_name. That used to work. when I echoed "sftsyn" to /proc..., the value did not stick; as soon as I modprobed speakup_sftsyn, then the /proc variable got updated. Is this change by design? do we have to explicitely modprobe speakup modules now or am I missing something some place. I don't recall seeing keyhelp in there either but that's for another discussion:). if it is by design, I'll just add the modprobe line into my rc.speakup script and it'll be all good. On Wed, May 17, 2006 at 11:14:34PM +0200, Hynek Hanke wrote: > Steve Holmes pí?e v St 17. 05. 2006 v 13:51 -0700: > > I used the same shell script I've always been using. The only thing > > that really changed was Speakup version; wonder if that could have > > anything to do with it? > > Possibly yes. > > > Maybe I'll have to go and try and run each of those steps manually with a second > > or two to spare between each. > > Yes. That would be useful. The only steps you need to do are: > 1) load speakup > 2) load the sftsyn module > 3) start speechd-up > Speech Dispatcher, Festival and other components have nothing to do with > this. It is entirely between speechd-up and Speakup. > > > I'm just baffled that it can't find /dev/softsynth when it is *REALLY THERE*. > > It doesn't say it can't find it. It can't open it. Maybe it is there but > it is not working for some reason. > > Yes, it is puzzling. I can't think of any reason why the system should > refuse to open it as is apparent from the log files you sent, supposing > sftsyn is loaded and the permissions are as you described. The best > next step would be to try manually and make sure the sftsyn module > gets fully loaded before speechd-up is started. > > Please let me know, > Hynek Hanke > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEa7CAWSjv55S0LfERAwXKAKC/GHvZLrCJGE6PP5HDK57Mxl2jGQCfRiKL u8eZbwlpJuYgDnC6pXV6bDc= =3GJe -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes @ ` Gregory Nowak ` Steve Holmes ` Trouble with speech dispatcher Sean M McMahon 1 sibling, 1 reply; 22+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I believe I reported on this a while back when describing the kernel panics I got when trying to switch between bns, dtlk, and sftsyn. Unless something has changed since that report, (and I don't know if it has, since I haven't upgraded speakup since then yet), then you need to modprobe sftsyn by hand, at least that's something that I needed to do. Greg On Wed, May 17, 2006 at 04:23:46PM -0700, Steve Holmes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > I think I'm on to something. I'm sorking this machine by remote ssh > session so can't be totally sure but What I see so far is the sftsyn > module is not being auto loaded when echoing "sftsyn" to > /proc/speakup/synth_name. That used to work. when I echoed "sftsyn" to > /proc..., the value did not stick; as soon as I modprobed > speakup_sftsyn, then the /proc variable got updated. Is this change by > design? do we have to explicitely modprobe speakup modules now or am I > missing something some place. I don't recall seeing keyhelp in there > either but that's for another discussion:). if it is by design, I'll > just add the modprobe line into my rc.speakup script and it'll be all > good. > - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager@EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEa7SS7s9z/XlyUyARAjh5AKCnXFNuLhh2h4KtiqbQYaR7HBh2LACfWi0N 749xudhyZF3zh4j9vhvmNqA= =F0H9 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Gregory Nowak @ ` Steve Holmes ` Gary Cramblitt ` (2 more replies) 0 siblings, 3 replies; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I checked this out further when I got home last night and I got speech dispatcher working now. The modprobe did the trick. I modprobe it just after echoing "sftsyn" to /proc/speakup/synth_name. All I need to do now is see if I can optimize the sound of Espeak a little better; dunno if I can really change much yet. I might have to refer to previous comments on this. It seems a bit choppy but the basic pronunciation is really clear and it seemed to be pretty responsive from the little I played with it. Right now, I'm using the espeak-generic.conf that was previously posted to this list. I understand there's a binary module or something on speech dispatcher's CVS, is that true? Is it any better? It really doesn't sound too bad so far though. On Wed, May 17, 2006 at 04:41:06PM -0700, Gregory Nowak wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I believe I reported on this a while back when describing the kernel > panics I got when trying to switch between bns, dtlk, and > sftsyn. Unless something has changed since that report, (and I don't > know if it has, since I haven't upgraded speakup since then yet), then > you need to modprobe sftsyn by hand, at least that's something that I > needed to do. > > Greg > > > On Wed, May 17, 2006 at 04:23:46PM -0700, Steve Holmes wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: RIPEMD160 > > > > I think I'm on to something. I'm sorking this machine by remote ssh > > session so can't be totally sure but What I see so far is the sftsyn > > module is not being auto loaded when echoing "sftsyn" to > > /proc/speakup/synth_name. That used to work. when I echoed "sftsyn" to > > /proc..., the value did not stick; as soon as I modprobed > > speakup_sftsyn, then the /proc variable got updated. Is this change by > > design? do we have to explicitely modprobe speakup modules now or am I > > missing something some place. I don't recall seeing keyhelp in there > > either but that's for another discussion:). if it is by design, I'll > > just add the modprobe line into my rc.speakup script and it'll be all > > good. > > > > - -- > web site: http://www.romuald.net.eu.org > gpg public key: http://www.romuald.net.eu.org/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > > - -- > Free domains: http://www.eu.org/ or mail dns-manager@EU.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > > iD8DBQFEa7SS7s9z/XlyUyARAjh5AKCnXFNuLhh2h4KtiqbQYaR7HBh2LACfWi0N > 749xudhyZF3zh4j9vhvmNqA= > =F0H9 > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEbHvhWSjv55S0LfERA0zoAKC3yhmzVi097tVFT4r1fy9tKJTz/gCfaiVh 7F6JW02DWd2sK3i7ICkHeEk= =2K4c -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes @ ` Gary Cramblitt ` Sean M McMahon ` Gregory Nowak ` A synthesizer analogy Jonathan Duddington 2 siblings, 1 reply; 22+ messages in thread From: Gary Cramblitt @ UTC (permalink / raw) To: speakup On Thursday 18 May 2006 09:51, Steve Holmes wrote: > I understand there's a binary module or > something on speech dispatcher's CVS, is that true? Is it any better? A "direct" espeak output module is planned for the future when espeak offers a library API. For now, you must use the generic output module with espeak. -- Gary Cramblitt (aka PhantomsDad) ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Gary Cramblitt @ ` Sean M McMahon ` Steve Holmes ` Hynek Hanke 0 siblings, 2 replies; 22+ messages in thread From: Sean M McMahon @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Can we use the generic espeak module with a stable version of speech-dispatcher or do we have to use it with the speech-dispatcher in cvs? ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Sean M McMahon @ ` Steve Holmes ` Hynek Hanke 1 sibling, 0 replies; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I did it with the production 0.6 of Dispatcher and 0.3 of speechd-up. Dunno if there is a difference ornot. On Thu, May 18, 2006 at 10:43:49AM -0700, Sean M McMahon wrote: > Can we use the generic espeak module with a stable version of > speech-dispatcher or do we have to use it with the speech-dispatcher in > cvs? > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEbLT6WSjv55S0LfERA5h2AJsEsMGNg4mOQ38bqWF+3YqOEVdYNQCg7cPc 0mlX/ScurGw3jd8CiOuLivs= =EFaF -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Sean M McMahon ` Steve Holmes @ ` Hynek Hanke 1 sibling, 0 replies; 22+ messages in thread From: Hynek Hanke @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Sean M McMahon píše v Čt 18. 05. 2006 v 10:43 -0700: > Can we use the generic espeak module with a stable version of > speech-dispatcher [...]? Yes. With regards, Hynek Hanke ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes ` Gary Cramblitt @ ` Gregory Nowak ` Steve Holmes ` A synthesizer analogy Jonathan Duddington 2 siblings, 1 reply; 22+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You don't need to echo sftsyn to /proc/speakup/synth_name, modprobing for the speakup_sftsyn module will do that for you automatically. Greg On Thu, May 18, 2006 at 06:51:31AM -0700, Steve Holmes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > I checked this out further when I got home last night and I got speech > dispatcher working now. The modprobe did the trick. I modprobe it just > after echoing "sftsyn" to /proc/speakup/synth_name. All I need to do > now is see if I can optimize the sound of Espeak a little better; dunno > if I can really change much yet. I might have to refer to previous > comments on this. It seems a bit choppy but the basic pronunciation is > really clear and it seemed to be pretty responsive from the little I > played with it. Right now, I'm using the espeak-generic.conf that was > previously posted to this list. I understand there's a binary module or > something on speech dispatcher's CVS, is that true? Is it any better? > > It really doesn't sound too bad so far though. > - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager@EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEbMNc7s9z/XlyUyARAgNfAJ9KvUGUnqgUfvRi0EgZGtIsEX/1/gCfafjN YSQc3BnZBqWL+a0ia7ZLgC4= =Xim2 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Gregory Nowak @ ` Steve Holmes ` Gregory Nowak 0 siblings, 1 reply; 22+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I'll probably leave the echo command in there because I use this same script to switch back to my speakout which is statically linked so AFAIK the echo would have to be used to switch back to Speakout. This load step is done only if sftsyn. I guess if everything were modulized, then maybe I could switch to modprobing only. Though I thought originally that echoing the synth name was supposed to modprobe the module for you. On Thu, May 18, 2006 at 11:56:28AM -0700, Gregory Nowak wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > You don't need to echo sftsyn to /proc/speakup/synth_name, modprobing > for the speakup_sftsyn module will do that for you automatically. > > Greg > > > On Thu, May 18, 2006 at 06:51:31AM -0700, Steve Holmes wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: RIPEMD160 > > > > I checked this out further when I got home last night and I got speech > > dispatcher working now. The modprobe did the trick. I modprobe it just > > after echoing "sftsyn" to /proc/speakup/synth_name. All I need to do > > now is see if I can optimize the sound of Espeak a little better; dunno > > if I can really change much yet. I might have to refer to previous > > comments on this. It seems a bit choppy but the basic pronunciation is > > really clear and it seemed to be pretty responsive from the little I > > played with it. Right now, I'm using the espeak-generic.conf that was > > previously posted to this list. I understand there's a binary module or > > something on speech dispatcher's CVS, is that true? Is it any better? > > > > It really doesn't sound too bad so far though. > > > > - -- > web site: http://www.romuald.net.eu.org > gpg public key: http://www.romuald.net.eu.org/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > > - -- > Free domains: http://www.eu.org/ or mail dns-manager@EU.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > > iD8DBQFEbMNc7s9z/XlyUyARAgNfAJ9KvUGUnqgUfvRi0EgZGtIsEX/1/gCfafjN > YSQc3BnZBqWL+a0ia7ZLgC4= > =Xim2 > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEbQi3WSjv55S0LfERA1gwAKC3DoZ6+CmwPn6bgGcgmR1QQvkVXQCeKkgl 8mJ74n950OqvH4mzmwhcw7k= =Pesu -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes @ ` Gregory Nowak 0 siblings, 0 replies; 22+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 18, 2006 at 04:52:24PM -0700, Steve Holmes wrote: > Though I thought originally > that echoing the synth name was supposed to modprobe the module for you. > Yes, it was supposed to, but as Kirk said recently, that functionality was broken during some change or other. Greg - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager@EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEbQqQ7s9z/XlyUyARAnPnAJ9xCPSJ5G9uCjzK0VZwwM5K84ToJgCgiwE4 neN/hORZ7wex3FUqEgKTBVA= =W5UZ -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 22+ messages in thread
* A synthesizer analogy ` Steve Holmes ` Gary Cramblitt ` Gregory Nowak @ ` Jonathan Duddington 2 siblings, 0 replies; 22+ messages in thread From: Jonathan Duddington @ UTC (permalink / raw) To: speakup In article <20060518135129.GB2854@lnx3.holmesgrown.com>, Steve Holmes <steve@holmesgrown.com> wrote: > [eSpeak] seems a bit choppy but the basic pronunciation is really > clear and it seemed to be pretty responsive from the little I played > with it. Yes. eSpeak doesn't pretend to sound natural or smooth or as human as the large commercial synthesizers, or the better Festival voices. After all, it's only 380 kBytes. But I did aim to make the pronunciation clear. Perhaps unnaturally so. To use an analogy, a good quality speech synthesizer is like a photograph (a large bitmap graphic file), whereas eSpeak is like a drawing or vector graphics. ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Steve Holmes ` Gregory Nowak @ ` Sean M McMahon 1 sibling, 0 replies; 22+ messages in thread From: Sean M McMahon @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. I've always had to modprobe speakup_sftsyn but then again I'm using a different distro and compiled sftsyn as a module in my custom kernel. ^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Trouble with speech dispatcher. ` Hynek Hanke ` Steve Holmes @ ` Satyam ` Michael Whapples 1 sibling, 1 reply; 22+ messages in thread From: Satyam @ UTC (permalink / raw) To: 'Hynek Hanke'; +Cc: speakup -----Original Message----- From: Hynek Hanke [mailto:hanke@brailcom.org] Sent: Wednesday, May 17, 2006 12:22 PM To: Speakup is a screen review system for Linux. Cc: satyanarayanamurthy.tanikella@gmail.com Subject: Re: Trouble with speech dispatcher. Satyam píše v St 17. 05. 2006 v 08:34 +0530: > After careful reading the install document of speech dispatcher I > issued the command Make all > Then I am getting the following error: No rule to make target all.stop Hello, you need to first call ./configure then make all I've just fixed the INSTALL document, sorry for the trouble. Have a nice day, Dear Hynek, As per your instruction I Compiled speech dispatcher version 0.6 using the command ./configure. When the command ./ configure I found the following 2 types of errors. 1. No glib 2.0 2. Flite libraries are missing. On verification I found that glib-2.0 is in /usr/local/lib. From the instruction mentioned in install document in the directory speech-dispatcher-0.6 I compiled flite 1.3 using the option ./configure --enable-shared. At the time of compilation it is Ok but When I issue the command make, flite-1.3 is throwing errors. Please help me in this regard. Appreciating your help -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Trouble with speech dispatcher. ` Satyam @ ` Michael Whapples 0 siblings, 0 replies; 22+ messages in thread From: Michael Whapples @ UTC (permalink / raw) To: satyanarayanamurthy.tanikella, Speakup is a screen review system for Linux. There was reports of flite 1.3 not compiling with shared libs, before on this list. I would suggest using flite 1.2. Check if your distribution has a package of flite, as this would simplify things. If it does not, then with newer versions of gcc or some standard library flite1.2 might not compile without some patches, I don't know where you can get this patch from but I could send a copy to you. From Michael Whapples ----- Original Message ----- From: "Satyam" <satyanarayanamurthy.tanikella@gmail.com> To: "'Hynek Hanke'" <hanke@brailcom.org> Cc: <speakup@braille.uwo.ca> Sent: Saturday, May 20, 2006 7:18 PM Subject: RE: Trouble with speech dispatcher. -----Original Message----- From: Hynek Hanke [mailto:hanke@brailcom.org] Sent: Wednesday, May 17, 2006 12:22 PM To: Speakup is a screen review system for Linux. Cc: satyanarayanamurthy.tanikella@gmail.com Subject: Re: Trouble with speech dispatcher. Satyam píše v St 17. 05. 2006 v 08:34 +0530: > After careful reading the install document of speech dispatcher I > issued the command Make all > Then I am getting the following error: No rule to make target all.stop Hello, you need to first call /configure then make all I've just fixed the INSTALL document, sorry for the trouble. Have a nice day, Dear Hynek, As per your instruction I Compiled speech dispatcher version 0.6 using the command ./configure. When the command ./ configure I found the following 2 types of errors. 1. No glib 2.0 2. Flite libraries are missing. On verification I found that glib-2.0 is in /usr/local/lib. From the instruction mentioned in install document in the directory speech-dispatcher-0.6 I compiled flite 1.3 using the option ./configure --enable-shared. At the time of compilation it is Ok but When I issue the command make, flite-1.3 is throwing errors. Please help me in this regard. Appreciating your help -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006 ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Trouble with speech dispatcher Satyam
` Tomas Cerha
` Willem van der Walt
` Hynek Hanke
` Steve Holmes
` Michael Whapples
` Steve Holmes
` Hynek Hanke
` Steve Holmes
` Gregory Nowak
` Steve Holmes
` Gary Cramblitt
` Sean M McMahon
` Steve Holmes
` Hynek Hanke
` Gregory Nowak
` Steve Holmes
` Gregory Nowak
` A synthesizer analogy Jonathan Duddington
` Trouble with speech dispatcher Sean M McMahon
` Satyam
` Michael Whapples
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).