regarding speech-dispatcher, dectalk and the init script

regarding speech-dispatcher, dectalk and the init script

[Hynek Hanke]

Hi all,

there are currently running various threads that complain that
the speech dispatcher's dectalk output module doesn't work if
speech dispatcher is started early during the boot process (before
login).

I don't know what may cause this, but possibly the problem can be
that the dectalk "say" program can't operate yet when speech-dispatcher
is starting. If it communicates to some server and the server is not
running yet, maybe the say command returns with an error and the output
module dies.

Could someone please look at what happens if you execute the say command
in that phase? I don't own Dectalk and I don't want to install it as
it's not free software.

With Regards,
Hynek Hanke

Re: regarding speech-dispatcher, dectalk and the init script

[Jacob Schmude]

Hi
The dectalk's say program works fine when executed in an initscript by
itself. I put it at the exact same point as I've tried to start speech
dispatcher and it works. It doesn't communicate with a server, it
communicates with the dectalk libraries. For the record, I'm using
slackware, so this init problem isn't tied down to one distribution. I
have it executing in rc.local, which means that it executes right before
the login prompt. By then, all hardware is up, including sound. None of
the log files, speechd, dtk-generic, nor speechd-up indicate any error
messages.

On Sun, 2 May 2004, Hynek Hanke wrote:

>
> Hi all,
>
> there are currently running various threads that complain that
> the speech dispatcher's dectalk output module doesn't work if
> speech dispatcher is started early during the boot process (before
> login).
>
> I don't know what may cause this, but possibly the problem can be
> that the dectalk "say" program can't operate yet when speech-dispatcher
> is starting. If it communicates to some server and the server is not
> running yet, maybe the say command returns with an error and the output
> module dies.

Re: regarding speech-dispatcher, dectalk and the init script

[Hynek Hanke]

On Sun, May 02, 2004 at 06:09:51AM -0400, Jacob Schmude wrote:
> The dectalk's say program works fine when executed in an initscript by
> itself. I put it at the exact same point as I've tried to start speech
> dispatcher and it works. It doesn't communicate with a server, it
> communicates with the dectalk libraries. For the record, I'm using
> slackware, so this init problem isn't tied down to one distribution. I
> have it executing in rc.local, which means that it executes right before
> the login prompt. By then, all hardware is up, including sound. 

This is very strange.

We should attempt to eliminate speechd-up from the possible places
where this problem might appear. Please can you repeat this proces (so
that dectalk wouldn't work with speechd-up) and try to run run_test
basic.test in src/tests after you login?

Under what user is speech-dispatcher executed on your system in the
init script? Does this user have permissions to acces the say command?

Regards,
Hynek

Re: regarding speech-dispatcher, dectalk and the init script

[Jacob Schmude]

Hi
Speech-dispatcher executes as root in my rc.local script, and root most
certainly has permission to access the say command. I get no output when
running run_test either, nor when I try to use speechd-el with
dtk-generic. Curiously, speechd-el can still use flite as its output even
though dectalk won't work when started from the initscript.

On Sun, 2 May 2004, Hynek Hanke wrote:

> This is very strange.
>
> We should attempt to eliminate speechd-up from the possible places
> where this problem might appear. Please can you repeat this proces (so
> that dectalk wouldn't work with speechd-up) and try to run run_test
> basic.test in src/tests after you login?

Re: regarding speech-dispatcher, dectalk and the init script

[Hynek Hanke]

On Sun, May 02, 2004 at 07:02:40AM -0400, Jacob Schmude wrote:
> Speech-dispatcher executes as root in my rc.local script, and root most
> certainly has permission to access the say command. I get no output when
> running run_test either, nor when I try to use speechd-el with
> dtk-generic. Curiously, speechd-el can still use flite as its output even
> though dectalk won't work when started from the initscript.

Flite and Festival should work. They do for me. It seems there is some
problem with the generic output module.

Please could you sent me privately your init.d script you use to run
Speech Dispatcher so that I can test it with epos-generic?

Thank you,
Hynek

Re: regarding speech-dispatcher, dectalk and the init script

[Jacob Schmude]

Hi
My script looks like this:

--script starts here--
#!/bin/sh
# rc.local - local startup script
#
# Get speech up and running:
/usr/local/bin/speech-dispatcher
sleep 1
modprobe speakup_sftsyn
/usr/local/bin/speechd_up
# Copy the speech settings:
cp /etc/speakup/sftsyn/* /proc/speakup
--script ends--
As can be seen, the script is extremely simple.

On Sun, 2 May 2004, Hynek Hanke wrote:

> On Sun, May 02, 2004 at 07:02:40AM -0400, Jacob Schmude wrote:
> > Speech-dispatcher executes as root in my rc.local script, and root most
> > certainly has permission to access the say command. I get no output when
> > running run_test either, nor when I try to use speechd-el with
> > dtk-generic. Curiously, speechd-el can still use flite as its output even
> > though dectalk won't work when started from the initscript.
>
> Flite and Festival should work. They do for me. It seems there is some
> problem with the generic output module.
>
> Please could you sent me privately your init.d script you use to run
> Speech Dispatcher so that I can test it with epos-generic?
>
> Thank you,
> Hynek
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: regarding speech-dispatcher, dectalk and the init script

[Cheryl Homiak]

I don't have a /etc/speakup but my sftsyn loads ok without being copied.


-- 
Cheryl
"Where your treasure is, there will your heart be also."

Re: regarding speech-dispatcher, dectalk and the init script

[nick G]

I think it's time for the maintainers of TuxTalk to work on it again.
Thanks,
Nick
----- Original Message ----- 
From: "Jacob Schmude" <jschmude@adelphia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, May 02, 2004 7:02 AM
Subject: Re: regarding speech-dispatcher, dectalk and the init script


> Hi
> Speech-dispatcher executes as root in my rc.local script, and root most
> certainly has permission to access the say command. I get no output when
> running run_test either, nor when I try to use speechd-el with
> dtk-generic. Curiously, speechd-el can still use flite as its output even
> though dectalk won't work when started from the initscript.
> 
> On Sun, 2 May 2004, Hynek Hanke wrote:
> 
> > This is very strange.
> >
> > We should attempt to eliminate speechd-up from the possible places
> > where this problem might appear. Please can you repeat this proces (so
> > that dectalk wouldn't work with speechd-up) and try to run run_test
> > basic.test in src/tests after you login?
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: regarding speech-dispatcher, dectalk and the init script

[dking]

Work is still being done on it, the problem from what I understand is 
space and size; a speech synthesis engine is large in size and you 
only have so much room your allowed to use in the size of the kernel.

 - D

Re: regarding speech-dispatcher, dectalk and the init script

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You forgot one more factor, time. Kirk doesn't have all the time in
the world to devote to working on it. So, instead of saying you think
the developer should get going on it, how about offering your help in
working on it instead?

Greg


On Sun, May 02, 2004 at 07:37:41AM -0700, dking@pimpsoft.com wrote:
> Work is still being done on it, the problem from what I understand is 
> space and size; a speech synthesis engine is large in size and you 
> only have so much room your allowed to use in the size of the kernel.
> 
>  - D
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> !DSPAM:4095078353772118218516!
> 
> 

- -- 
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAlR4m7s9z/XlyUyARAk32AJ47oehl+qLkLEByMvy9iSnEf4N+TQCgw4d6
jpnTcXnZ7E87uM8EuhgqPi8=
=lMQu
-----END PGP SIGNATURE-----

Re: regarding speech-dispatcher, dectalk and the init script

[Hynek Hanke]

On Sun, May 02, 2004 at 07:02:40AM -0400, Jacob Schmude wrote:
> Speech-dispatcher executes as root in my rc.local script, and root most
> certainly has permission to access the say command. I get no output when
> running run_test either, nor when I try to use speechd-el with
> dtk-generic. Curiously, speechd-el can still use flite as its output even
> though dectalk won't work when started from the initscript.

I tried to use the rc.local script you sent me and then let it talk
through epos-generic and it also worked. So it seems the problem
is only observed with dtk-generic. It seems it is some strange
thing related directly to dectalk.

Any ideas anyone?

Regards,
Hynek Hanke