IBMTTS on slackware

IBMTTS on slackware

[Michael Whapples]

Hello,
I know this has come up before, but I can't remember any actual final
conclusion.

Whilst I thought espeak was fast enough, I found I had to use a windows
machine last week, and it reminded me how I do actually use eloquence in
windows faster than I have espeak. This has got me thinking whether I
should get IBMTTS for linux, but I have a few questions.

I know that IBMTTS requires an old compatibility library, which I am
unsure is provided in slackware. So how could I go about trying to get
this library? Does anyone know of a suitable slackware package for it?
If not how might I go about providing this myself from source (I had a
look around for the source code I might need, but all libstdc++ seems to
have numbers such as 6.0.x etc much highrt than what the TTSynth site
suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
different distribution, eg. I remember back in the days when I used
trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
slackware package and it worked fine, but I suspect that for libstdc++
compatibility libraries things may not be so simple.

This brings me on to another question, whether to use voxin or ttsynth?
The ttsynth website says there won't be any support provided, so I guess
this means if I buy ttsynth and can't get it working then I am on my own
and may have wasted money on it. Might things be better with voxin,
their website says that voxin includes the libstdc++ compatibility
library (I guess for debian or ubuntu as those are the distros
mentioned). 

Alternatively I am wondering whether it would be best save the money and
stick with espeak as it is good and works, where as ibmtts sounds like I
may hit all sorts of compatibility issues and potentially have no
support from the seller.

Michael Whapples

Re: IBMTTS on slackware

[William Hubbs]

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

Hi Michael,

In my opinion, this is a big waste of money since there is no support
for it with current libraries.  

As much as I like eloquence, that is all I use on windows these days, I,
for one, do not intend to purchase or install this on my linux system
because of the total lack of support or interest in updating it.

William

On Sun, Jun 01, 2008 at 08:33:48PM +0100, Michael Whapples wrote:
> Hello,
> I know this has come up before, but I can't remember any actual final
> conclusion.
> 
> Whilst I thought espeak was fast enough, I found I had to use a windows
> machine last week, and it reminded me how I do actually use eloquence in
> windows faster than I have espeak. This has got me thinking whether I
> should get IBMTTS for linux, but I have a few questions.
> 
> I know that IBMTTS requires an old compatibility library, which I am
> unsure is provided in slackware. So how could I go about trying to get
> this library? Does anyone know of a suitable slackware package for it?
> If not how might I go about providing this myself from source (I had a
> look around for the source code I might need, but all libstdc++ seems to
> have numbers such as 6.0.x etc much highrt than what the TTSynth site
> suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> different distribution, eg. I remember back in the days when I used
> trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> slackware package and it worked fine, but I suspect that for libstdc++
> compatibility libraries things may not be so simple.
> 
> This brings me on to another question, whether to use voxin or ttsynth?
> The ttsynth website says there won't be any support provided, so I guess
> this means if I buy ttsynth and can't get it working then I am on my own
> and may have wasted money on it. Might things be better with voxin,
> their website says that voxin includes the libstdc++ compatibility
> library (I guess for debian or ubuntu as those are the distros
> mentioned). 
> 
> Alternatively I am wondering whether it would be best save the money and
> stick with espeak as it is good and works, where as ibmtts sounds like I
> may hit all sorts of compatibility issues and potentially have no
> support from the seller.
> 
> Michael Whapples
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkhDGrUACgkQblQW9DDEZTgOggCcDOV8HQMDRovaqK/fjcVQwpX3
K6oAn1FNvbysNHMgwAbv8OFf2l49i8Qn
=pkUq
-----END PGP SIGNATURE-----

Re: IBMTTS on slackware

[Nick Stockton]

I know it's doable because I helped a friend set up their copy of ttsynth on 
their slackware box a while back.
I forget if it was slackware version 11 or 12 but I think the process would 
be the same for eather one.
I've not ever seen any instructions on the speakup list on how to do it so 
I'll write down what I did here.
Lucky for you I saved the commands I enterd to a text file so I'd know how 
it was done although I'm using voxin which I got for $5 and am running it 
under debian.
Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
to get working under slackware so you better get ttsynth.
I've also prepended the commands with '$ ' in case my email client tries to 
wrap commands to the next line. So you'll be able to see where each line 
begins.
You will need to run all the commands as root. You also need to have alien 
installed.
If you don't want to find, download, compile and install alien and all the 
dependencies from source to your copy of slackware then you might want to 
download GRML and use it only to run the alien commands.
--------------------
$ wget 
http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
$ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
$ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
$ ldconfig
$ alien -t -c -k ttsynthcore-1.0-i386.deb
$ installpkg ttsynthcore-1.0.tgz
$ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
$ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
$ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
$ cp /opt/IBM/ibmtts/inc/* /usr/include/
$ ldconfig
$ I know it's doable because I helped a friend set up their copy of ttsynth 
on their slackware box.
I forget if it was slackware version 11 or 12 but I think the process would 
be the same for eather one.
I've not ever seen any instructions on the speakup list on how to do it so 
I'll write down what I did here.
Lucky for you I saved the commands I enterd to a text file so I'd know how 
it was done although I'm using voxin which I got for $5 and am running it 
under debian.
Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
to get working under slackware so you better get ttsynth.
I've also prepended the commands with '$ ' in case my email client tries to 
wrap commands to the next line. So you'll be able to see where each line 
begins.
You will need to run all the commands as root. You also need to have alien 
installed.
If you don't want to find, download, compile and install alien and all the 
dependencies from source to your copy of slackware then you might want to 
download GRML and use it to run the alien commands.
--------------------
$ wget 
http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
$ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
$ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
$ ldconfig
$ alien -t -c -k ttsynthcore-1.0-i386.deb
$ installpkg ttsynthcore-1.0.tgz
$ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
$ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
$ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
$ cp /opt/IBM/ibmtts/inc/* /usr/include/
$ ldconfig
$ mknod /dev/softsynth c 10 26
--------------------
Hope this helps.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 01, 2008 3:33 PM
Subject: IBMTTS on slackware


> Hello,
> I know this has come up before, but I can't remember any actual final
> conclusion.
>
> Whilst I thought espeak was fast enough, I found I had to use a windows
> machine last week, and it reminded me how I do actually use eloquence in
> windows faster than I have espeak. This has got me thinking whether I
> should get IBMTTS for linux, but I have a few questions.
>
> I know that IBMTTS requires an old compatibility library, which I am
> unsure is provided in slackware. So how could I go about trying to get
> this library? Does anyone know of a suitable slackware package for it?
> If not how might I go about providing this myself from source (I had a
> look around for the source code I might need, but all libstdc++ seems to
> have numbers such as 6.0.x etc much highrt than what the TTSynth site
> suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> different distribution, eg. I remember back in the days when I used
> trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> slackware package and it worked fine, but I suspect that for libstdc++
> compatibility libraries things may not be so simple.
>
> This brings me on to another question, whether to use voxin or ttsynth?
> The ttsynth website says there won't be any support provided, so I guess
> this means if I buy ttsynth and can't get it working then I am on my own
> and may have wasted money on it. Might things be better with voxin,
> their website says that voxin includes the libstdc++ compatibility
> library (I guess for debian or ubuntu as those are the distros
> mentioned).
>
> Alternatively I am wondering whether it would be best save the money and
> stick with espeak as it is good and works, where as ibmtts sounds like I
> may hit all sorts of compatibility issues and potentially have no
> support from the seller.
>
> Michael Whapples
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: IBMTTS on slackware

[Willem van der Walt]

Hi,
I use espeak all the time although I still have an old version of viavoice 
going on this machine.
People can also try out the mbrola voice with Espeak. It is more natural 
sounding and free.
Check the espeak documentation for details.
Regards, Willem


On Sun, 1 Jun 2008, William Hubbs wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Michael,
> 
> In my opinion, this is a big waste of money since there is no support
> for it with current libraries.  
> 
> As much as I like eloquence, that is all I use on windows these days, I,
> for one, do not intend to purchase or install this on my linux system
> because of the total lack of support or interest in updating it.
> 
> William
> 
> On Sun, Jun 01, 2008 at 08:33:48PM +0100, Michael Whapples wrote:
> > Hello,
> > I know this has come up before, but I can't remember any actual final
> > conclusion.
> > 
> > Whilst I thought espeak was fast enough, I found I had to use a windows
> > machine last week, and it reminded me how I do actually use eloquence in
> > windows faster than I have espeak. This has got me thinking whether I
> > should get IBMTTS for linux, but I have a few questions.
> > 
> > I know that IBMTTS requires an old compatibility library, which I am
> > unsure is provided in slackware. So how could I go about trying to get
> > this library? Does anyone know of a suitable slackware package for it?
> > If not how might I go about providing this myself from source (I had a
> > look around for the source code I might need, but all libstdc++ seems to
> > have numbers such as 6.0.x etc much highrt than what the TTSynth site
> > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> > different distribution, eg. I remember back in the days when I used
> > trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> > slackware package and it worked fine, but I suspect that for libstdc++
> > compatibility libraries things may not be so simple.
> > 
> > This brings me on to another question, whether to use voxin or ttsynth?
> > The ttsynth website says there won't be any support provided, so I guess
> > this means if I buy ttsynth and can't get it working then I am on my own
> > and may have wasted money on it. Might things be better with voxin,
> > their website says that voxin includes the libstdc++ compatibility
> > library (I guess for debian or ubuntu as those are the distros
> > mentioned). 
> > 
> > Alternatively I am wondering whether it would be best save the money and
> > stick with espeak as it is good and works, where as ibmtts sounds like I
> > may hit all sorts of compatibility issues and potentially have no
> > support from the seller.
> > 
> > Michael Whapples
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> 
> iEYEARECAAYFAkhDGrUACgkQblQW9DDEZTgOggCcDOV8HQMDRovaqK/fjcVQwpX3
> K6oAn1FNvbysNHMgwAbv8OFf2l49i8Qn
> =pkUq
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

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.

Re: IBMTTS on slackware

[Michael Whapples]

Good to hear that it is possible. Can I ask why you say voxin will be
more of a problem? Considering the significant difference in price I
would prefer to get voxin if possible. Its the high price of TTSynth
which had made me question so much whether it would be worth the money,
the question wasn't so high for voxin until you said that it might be
more difficult on slackware. Might it be less painful if I were to use
GRML for certain parts of voxin's install?

I may discuss things with the voxin people to see if I could get them to
help me sort out a slackware version of voxin.

Michael Whapples
On Sun, 2008-06-01 at 18:01 -0400, Nick Stockton wrote:
> I know it's doable because I helped a friend set up their copy of ttsynth on 
> their slackware box a while back.
> I forget if it was slackware version 11 or 12 but I think the process would 
> be the same for eather one.
> I've not ever seen any instructions on the speakup list on how to do it so 
> I'll write down what I did here.
> Lucky for you I saved the commands I enterd to a text file so I'd know how 
> it was done although I'm using voxin which I got for $5 and am running it 
> under debian.
> Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> to get working under slackware so you better get ttsynth.
> I've also prepended the commands with '$ ' in case my email client tries to 
> wrap commands to the next line. So you'll be able to see where each line 
> begins.
> You will need to run all the commands as root. You also need to have alien 
> installed.
> If you don't want to find, download, compile and install alien and all the 
> dependencies from source to your copy of slackware then you might want to 
> download GRML and use it only to run the alien commands.
> --------------------
> $ wget 
> http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> $ ldconfig
> $ alien -t -c -k ttsynthcore-1.0-i386.deb
> $ installpkg ttsynthcore-1.0.tgz
> $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> $ ldconfig
> $ I know it's doable because I helped a friend set up their copy of ttsynth 
> on their slackware box.
> I forget if it was slackware version 11 or 12 but I think the process would 
> be the same for eather one.
> I've not ever seen any instructions on the speakup list on how to do it so 
> I'll write down what I did here.
> Lucky for you I saved the commands I enterd to a text file so I'd know how 
> it was done although I'm using voxin which I got for $5 and am running it 
> under debian.
> Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> to get working under slackware so you better get ttsynth.
> I've also prepended the commands with '$ ' in case my email client tries to 
> wrap commands to the next line. So you'll be able to see where each line 
> begins.
> You will need to run all the commands as root. You also need to have alien 
> installed.
> If you don't want to find, download, compile and install alien and all the 
> dependencies from source to your copy of slackware then you might want to 
> download GRML and use it to run the alien commands.
> --------------------
> $ wget 
> http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> $ ldconfig
> $ alien -t -c -k ttsynthcore-1.0-i386.deb
> $ installpkg ttsynthcore-1.0.tgz
> $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> $ ldconfig
> $ mknod /dev/softsynth c 10 26
> --------------------
> Hope this helps.
> ----- Original Message ----- 
> From: "Michael Whapples" <mwhapples@aim.com>
> To: <speakup@braille.uwo.ca>
> Sent: Sunday, June 01, 2008 3:33 PM
> Subject: IBMTTS on slackware
> 
> 
> 
> > Hello,
> > I know this has come up before, but I can't remember any actual final
> > conclusion.
> >
> > Whilst I thought espeak was fast enough, I found I had to use a windows
> > machine last week, and it reminded me how I do actually use eloquence in
> > windows faster than I have espeak. This has got me thinking whether I
> > should get IBMTTS for linux, but I have a few questions.
> >
> > I know that IBMTTS requires an old compatibility library, which I am
> > unsure is provided in slackware. So how could I go about trying to get
> > this library? Does anyone know of a suitable slackware package for it?
> > If not how might I go about providing this myself from source (I had a
> > look around for the source code I might need, but all libstdc++ seems to
> > have numbers such as 6.0.x etc much highrt than what the TTSynth site
> > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> > different distribution, eg. I remember back in the days when I used
> > trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> > slackware package and it worked fine, but I suspect that for libstdc++
> > compatibility libraries things may not be so simple.
> >
> > This brings me on to another question, whether to use voxin or ttsynth?
> > The ttsynth website says there won't be any support provided, so I guess
> > this means if I buy ttsynth and can't get it working then I am on my own
> > and may have wasted money on it. Might things be better with voxin,
> > their website says that voxin includes the libstdc++ compatibility
> > library (I guess for debian or ubuntu as those are the distros
> > mentioned).
> >
> > Alternatively I am wondering whether it would be best save the money and
> > stick with espeak as it is good and works, where as ibmtts sounds like I
> > may hit all sorts of compatibility issues and potentially have no
> > support from the seller.
> >
> > Michael Whapples
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup 
> 
> 
> 

Re: IBMTTS on slackware

[Alex Snow]

Voxin requires a kernel recompile to build the cryptoloop and aes 
modules. 
On Mon, Jun 02, 2008 at 01:42:05PM +0100, Michael Whapples 
wrote:
> Good to hear that it is possible. Can I ask why you say voxin will be
> more of a problem? Considering the significant difference in price I
> would prefer to get voxin if possible. Its the high price of TTSynth
> which had made me question so much whether it would be worth the money,
> the question wasn't so high for voxin until you said that it might be
> more difficult on slackware. Might it be less painful if I were to use
> GRML for certain parts of voxin's install?
> 
> I may discuss things with the voxin people to see if I could get them to
> help me sort out a slackware version of voxin.
> 
> Michael Whapples
> On Sun, 2008-06-01 at 18:01 -0400, Nick Stockton wrote:
> > I know it's doable because I helped a friend set up their copy of ttsynth on 
> > their slackware box a while back.
> > I forget if it was slackware version 11 or 12 but I think the process would 
> > be the same for eather one.
> > I've not ever seen any instructions on the speakup list on how to do it so 
> > I'll write down what I did here.
> > Lucky for you I saved the commands I enterd to a text file so I'd know how 
> > it was done although I'm using voxin which I got for $5 and am running it 
> > under debian.
> > Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> > to get working under slackware so you better get ttsynth.
> > I've also prepended the commands with '$ ' in case my email client tries to 
> > wrap commands to the next line. So you'll be able to see where each line 
> > begins.
> > You will need to run all the commands as root. You also need to have alien 
> > installed.
> > If you don't want to find, download, compile and install alien and all the 
> > dependencies from source to your copy of slackware then you might want to 
> > download GRML and use it only to run the alien commands.
> > --------------------
> > $ wget 
> > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> > $ ldconfig
> > $ alien -t -c -k ttsynthcore-1.0-i386.deb
> > $ installpkg ttsynthcore-1.0.tgz
> > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> > $ ldconfig
> > $ I know it's doable because I helped a friend set up their copy of ttsynth 
> > on their slackware box.
> > I forget if it was slackware version 11 or 12 but I think the process would 
> > be the same for eather one.
> > I've not ever seen any instructions on the speakup list on how to do it so 
> > I'll write down what I did here.
> > Lucky for you I saved the commands I enterd to a text file so I'd know how 
> > it was done although I'm using voxin which I got for $5 and am running it 
> > under debian.
> > Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> > to get working under slackware so you better get ttsynth.
> > I've also prepended the commands with '$ ' in case my email client tries to 
> > wrap commands to the next line. So you'll be able to see where each line 
> > begins.
> > You will need to run all the commands as root. You also need to have alien 
> > installed.
> > If you don't want to find, download, compile and install alien and all the 
> > dependencies from source to your copy of slackware then you might want to 
> > download GRML and use it to run the alien commands.
> > --------------------
> > $ wget 
> > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> > $ ldconfig
> > $ alien -t -c -k ttsynthcore-1.0-i386.deb
> > $ installpkg ttsynthcore-1.0.tgz
> > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> > $ ldconfig
> > $ mknod /dev/softsynth c 10 26
> > --------------------
> > Hope this helps.
> > ----- Original Message ----- 
> > From: "Michael Whapples" <mwhapples@aim.com>
> > To: <speakup@braille.uwo.ca>
> > Sent: Sunday, June 01, 2008 3:33 PM
> > Subject: IBMTTS on slackware
> > 
> > 
> > 
> > > Hello,
> > > I know this has come up before, but I can't remember any actual final
> > > conclusion.
> > >
> > > Whilst I thought espeak was fast enough, I found I had to use a windows
> > > machine last week, and it reminded me how I do actually use eloquence in
> > > windows faster than I have espeak. This has got me thinking whether I
> > > should get IBMTTS for linux, but I have a few questions.
> > >
> > > I know that IBMTTS requires an old compatibility library, which I am
> > > unsure is provided in slackware. So how could I go about trying to get
> > > this library? Does anyone know of a suitable slackware package for it?
> > > If not how might I go about providing this myself from source (I had a
> > > look around for the source code I might need, but all libstdc++ seems to
> > > have numbers such as 6.0.x etc much highrt than what the TTSynth site
> > > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> > > different distribution, eg. I remember back in the days when I used
> > > trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> > > slackware package and it worked fine, but I suspect that for libstdc++
> > > compatibility libraries things may not be so simple.
> > >
> > > This brings me on to another question, whether to use voxin or ttsynth?
> > > The ttsynth website says there won't be any support provided, so I guess
> > > this means if I buy ttsynth and can't get it working then I am on my own
> > > and may have wasted money on it. Might things be better with voxin,
> > > their website says that voxin includes the libstdc++ compatibility
> > > library (I guess for debian or ubuntu as those are the distros
> > > mentioned).
> > >
> > > Alternatively I am wondering whether it would be best save the money and
> > > stick with espeak as it is good and works, where as ibmtts sounds like I
> > > may hit all sorts of compatibility issues and potentially have no
> > > support from the seller.
> > >
> > > Michael Whapples
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup 
> > 
> > 
> > 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
> You know you are "there" when you are known by your first name, and
> are recognized.
> Lemmie see, there is Madonna, and Linus, and ..... help me out here!
Bill ? ;-)
	-- From some postings on comp.os.linux.misc

Re: IBMTTS on slackware

[Michael Whapples]

I am happy enough recompiling the kernel, but I have just checked the
slackware 12.1 configuration and it appears this is already done,
cryptoloop is a module and aes options seem to be compiled in.

I think my next step is to contact voxin and get a copy.

Michael Whapples
On Mon, 2008-06-02 at 11:39 -0400, Alex Snow wrote:
> Voxin requires a kernel recompile to build the cryptoloop and aes 
> modules. 
> On Mon, Jun 02, 2008 at 01:42:05PM +0100, Michael Whapples 
> wrote:
> > Good to hear that it is possible. Can I ask why you say voxin will be
> > more of a problem? Considering the significant difference in price I
> > would prefer to get voxin if possible. Its the high price of TTSynth
> > which had made me question so much whether it would be worth the money,
> > the question wasn't so high for voxin until you said that it might be
> > more difficult on slackware. Might it be less painful if I were to use
> > GRML for certain parts of voxin's install?
> > 
> > I may discuss things with the voxin people to see if I could get them to
> > help me sort out a slackware version of voxin.
> > 
> > Michael Whapples
> > On Sun, 2008-06-01 at 18:01 -0400, Nick Stockton wrote:
> > > I know it's doable because I helped a friend set up their copy of ttsynth on 
> > > their slackware box a while back.
> > > I forget if it was slackware version 11 or 12 but I think the process would 
> > > be the same for eather one.
> > > I've not ever seen any instructions on the speakup list on how to do it so 
> > > I'll write down what I did here.
> > > Lucky for you I saved the commands I enterd to a text file so I'd know how 
> > > it was done although I'm using voxin which I got for $5 and am running it 
> > > under debian.
> > > Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> > > to get working under slackware so you better get ttsynth.
> > > I've also prepended the commands with '$ ' in case my email client tries to 
> > > wrap commands to the next line. So you'll be able to see where each line 
> > > begins.
> > > You will need to run all the commands as root. You also need to have alien 
> > > installed.
> > > If you don't want to find, download, compile and install alien and all the 
> > > dependencies from source to your copy of slackware then you might want to 
> > > download GRML and use it only to run the alien commands.
> > > --------------------
> > > $ wget 
> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> > > $ ldconfig
> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
> > > $ installpkg ttsynthcore-1.0.tgz
> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> > > $ ldconfig
> > > $ I know it's doable because I helped a friend set up their copy of ttsynth 
> > > on their slackware box.
> > > I forget if it was slackware version 11 or 12 but I think the process would 
> > > be the same for eather one.
> > > I've not ever seen any instructions on the speakup list on how to do it so 
> > > I'll write down what I did here.
> > > Lucky for you I saved the commands I enterd to a text file so I'd know how 
> > > it was done although I'm using voxin which I got for $5 and am running it 
> > > under debian.
> > > Note: this is for ttsynth under slackware. Voxin would be quite alot harder 
> > > to get working under slackware so you better get ttsynth.
> > > I've also prepended the commands with '$ ' in case my email client tries to 
> > > wrap commands to the next line. So you'll be able to see where each line 
> > > begins.
> > > You will need to run all the commands as root. You also need to have alien 
> > > installed.
> > > If you don't want to find, download, compile and install alien and all the 
> > > dependencies from source to your copy of slackware then you might want to 
> > > download GRML and use it to run the alien commands.
> > > --------------------
> > > $ wget 
> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
> > > $ ldconfig
> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
> > > $ installpkg ttsynthcore-1.0.tgz
> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
> > > $ ldconfig
> > > $ mknod /dev/softsynth c 10 26
> > > --------------------
> > > Hope this helps.
> > > ----- Original Message ----- 
> > > From: "Michael Whapples" <mwhapples@aim.com>
> > > To: <speakup@braille.uwo.ca>
> > > Sent: Sunday, June 01, 2008 3:33 PM
> > > Subject: IBMTTS on slackware
> > > 
> > > 
> > > 
> > > > Hello,
> > > > I know this has come up before, but I can't remember any actual final
> > > > conclusion.
> > > >
> > > > Whilst I thought espeak was fast enough, I found I had to use a windows
> > > > machine last week, and it reminded me how I do actually use eloquence in
> > > > windows faster than I have espeak. This has got me thinking whether I
> > > > should get IBMTTS for linux, but I have a few questions.
> > > >
> > > > I know that IBMTTS requires an old compatibility library, which I am
> > > > unsure is provided in slackware. So how could I go about trying to get
> > > > this library? Does anyone know of a suitable slackware package for it?
> > > > If not how might I go about providing this myself from source (I had a
> > > > look around for the source code I might need, but all libstdc++ seems to
> > > > have numbers such as 6.0.x etc much highrt than what the TTSynth site
> > > > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
> > > > different distribution, eg. I remember back in the days when I used
> > > > trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
> > > > slackware package and it worked fine, but I suspect that for libstdc++
> > > > compatibility libraries things may not be so simple.
> > > >
> > > > This brings me on to another question, whether to use voxin or ttsynth?
> > > > The ttsynth website says there won't be any support provided, so I guess
> > > > this means if I buy ttsynth and can't get it working then I am on my own
> > > > and may have wasted money on it. Might things be better with voxin,
> > > > their website says that voxin includes the libstdc++ compatibility
> > > > library (I guess for debian or ubuntu as those are the distros
> > > > mentioned).
> > > >
> > > > Alternatively I am wondering whether it would be best save the money and
> > > > stick with espeak as it is good and works, where as ibmtts sounds like I
> > > > may hit all sorts of compatibility issues and potentially have no
> > > > support from the seller.
> > > >
> > > > Michael Whapples
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup 
> > > 
> > > 
> > > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: IBMTTS on slackware

[Nick Stockton]

hmmm haven't used slackware sence 11.0 but yes that's why it was a bit 
harder.
also I had to get the IBMTTS SDK from sourceforge in order to compile the 
ttsynth_say and spk-connect-ttsynth programs.
ttsynth already has the files needed to compile them built in.
I see though that voxin has been updated since I baut it.
So maybe they have added in the stuff from the SDK.
If not you can get it from
http://ibmtts-sdk.sourceforge.net/
You will still have to do the business of copying all the include files in 
viavoice's inc directory to the /usr/include directory and making links to 
all the files in viavoice's lib directory to /usr/lib unless voxin fixed 
this since I baut it.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, June 02, 2008 4:09 PM
Subject: Re: IBMTTS on slackware


>I am happy enough recompiling the kernel, but I have just checked the
> slackware 12.1 configuration and it appears this is already done,
> cryptoloop is a module and aes options seem to be compiled in.
>
> I think my next step is to contact voxin and get a copy.
>
> Michael Whapples
> On Mon, 2008-06-02 at 11:39 -0400, Alex Snow wrote:
>> Voxin requires a kernel recompile to build the cryptoloop and aes
>> modules.
>> On Mon, Jun 02, 2008 at 01:42:05PM +0100, Michael Whapples
>> wrote:
>> > Good to hear that it is possible. Can I ask why you say voxin will be
>> > more of a problem? Considering the significant difference in price I
>> > would prefer to get voxin if possible. Its the high price of TTSynth
>> > which had made me question so much whether it would be worth the money,
>> > the question wasn't so high for voxin until you said that it might be
>> > more difficult on slackware. Might it be less painful if I were to use
>> > GRML for certain parts of voxin's install?
>> >
>> > I may discuss things with the voxin people to see if I could get them 
>> > to
>> > help me sort out a slackware version of voxin.
>> >
>> > Michael Whapples
>> > On Sun, 2008-06-01 at 18:01 -0400, Nick Stockton wrote:
>> > > I know it's doable because I helped a friend set up their copy of 
>> > > ttsynth on
>> > > their slackware box a while back.
>> > > I forget if it was slackware version 11 or 12 but I think the process 
>> > > would
>> > > be the same for eather one.
>> > > I've not ever seen any instructions on the speakup list on how to do 
>> > > it so
>> > > I'll write down what I did here.
>> > > Lucky for you I saved the commands I enterd to a text file so I'd 
>> > > know how
>> > > it was done although I'm using voxin which I got for $5 and am 
>> > > running it
>> > > under debian.
>> > > Note: this is for ttsynth under slackware. Voxin would be quite alot 
>> > > harder
>> > > to get working under slackware so you better get ttsynth.
>> > > I've also prepended the commands with '$ ' in case my email client 
>> > > tries to
>> > > wrap commands to the next line. So you'll be able to see where each 
>> > > line
>> > > begins.
>> > > You will need to run all the commands as root. You also need to have 
>> > > alien
>> > > installed.
>> > > If you don't want to find, download, compile and install alien and 
>> > > all the
>> > > dependencies from source to your copy of slackware then you might 
>> > > want to
>> > > download GRML and use it only to run the alien commands.
>> > > --------------------
>> > > $ wget
>> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
>> > > $ ldconfig
>> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
>> > > $ installpkg ttsynthcore-1.0.tgz
>> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
>> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
>> > > $ ldconfig
>> > > $ I know it's doable because I helped a friend set up their copy of 
>> > > ttsynth
>> > > on their slackware box.
>> > > I forget if it was slackware version 11 or 12 but I think the process 
>> > > would
>> > > be the same for eather one.
>> > > I've not ever seen any instructions on the speakup list on how to do 
>> > > it so
>> > > I'll write down what I did here.
>> > > Lucky for you I saved the commands I enterd to a text file so I'd 
>> > > know how
>> > > it was done although I'm using voxin which I got for $5 and am 
>> > > running it
>> > > under debian.
>> > > Note: this is for ttsynth under slackware. Voxin would be quite alot 
>> > > harder
>> > > to get working under slackware so you better get ttsynth.
>> > > I've also prepended the commands with '$ ' in case my email client 
>> > > tries to
>> > > wrap commands to the next line. So you'll be able to see where each 
>> > > line
>> > > begins.
>> > > You will need to run all the commands as root. You also need to have 
>> > > alien
>> > > installed.
>> > > If you don't want to find, download, compile and install alien and 
>> > > all the
>> > > dependencies from source to your copy of slackware then you might 
>> > > want to
>> > > download GRML and use it to run the alien commands.
>> > > --------------------
>> > > $ wget
>> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
>> > > $ ldconfig
>> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
>> > > $ installpkg ttsynthcore-1.0.tgz
>> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
>> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
>> > > $ ldconfig
>> > > $ mknod /dev/softsynth c 10 26
>> > > --------------------
>> > > Hope this helps.
>> > > ----- Original Message ----- 
>> > > From: "Michael Whapples" <mwhapples@aim.com>
>> > > To: <speakup@braille.uwo.ca>
>> > > Sent: Sunday, June 01, 2008 3:33 PM
>> > > Subject: IBMTTS on slackware
>> > >
>> > >
>> > >
>> > > > Hello,
>> > > > I know this has come up before, but I can't remember any actual 
>> > > > final
>> > > > conclusion.
>> > > >
>> > > > Whilst I thought espeak was fast enough, I found I had to use a 
>> > > > windows
>> > > > machine last week, and it reminded me how I do actually use 
>> > > > eloquence in
>> > > > windows faster than I have espeak. This has got me thinking whether 
>> > > > I
>> > > > should get IBMTTS for linux, but I have a few questions.
>> > > >
>> > > > I know that IBMTTS requires an old compatibility library, which I 
>> > > > am
>> > > > unsure is provided in slackware. So how could I go about trying to 
>> > > > get
>> > > > this library? Does anyone know of a suitable slackware package for 
>> > > > it?
>> > > > If not how might I go about providing this myself from source (I 
>> > > > had a
>> > > > look around for the source code I might need, but all libstdc++ 
>> > > > seems to
>> > > > have numbers such as 6.0.x etc much highrt than what the TTSynth 
>> > > > site
>> > > > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package 
>> > > > from a
>> > > > different distribution, eg. I remember back in the days when I used
>> > > > trplayer, I could use rpm2tgz to convert the realplayer 8 package 
>> > > > into a
>> > > > slackware package and it worked fine, but I suspect that for 
>> > > > libstdc++
>> > > > compatibility libraries things may not be so simple.
>> > > >
>> > > > This brings me on to another question, whether to use voxin or 
>> > > > ttsynth?
>> > > > The ttsynth website says there won't be any support provided, so I 
>> > > > guess
>> > > > this means if I buy ttsynth and can't get it working then I am on 
>> > > > my own
>> > > > and may have wasted money on it. Might things be better with voxin,
>> > > > their website says that voxin includes the libstdc++ compatibility
>> > > > library (I guess for debian or ubuntu as those are the distros
>> > > > mentioned).
>> > > >
>> > > > Alternatively I am wondering whether it would be best save the 
>> > > > money and
>> > > > stick with espeak as it is good and works, where as ibmtts sounds 
>> > > > like I
>> > > > may hit all sorts of compatibility issues and potentially have no
>> > > > support from the seller.
>> > > >
>> > > > Michael Whapples
>> > > >
>> > > > _______________________________________________
>> > > > Speakup mailing list
>> > > > Speakup@braille.uwo.ca
>> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> > >
>> > >
>> > >
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: IBMTTS on slackware

[Nick Stockton]

By the way I'd expect less support than you get with ttsynth if you go with 
voxin *grin*.
Before I baut Voxin I sent an email asking if there was any differences 
between ttsynth and voxin besides the name and the price and I got a email 
back with a single line saying I should ask on the speakup list *lol*.
I guess when something is $5 you shouldn't expect people to really put their 
hearts in to selling it to you but I don't think it would have taken long to 
send a message back with a couple of differences between the two.
Any how in case you want to know the main differenses between voxin and 
ttsynth are
voxin came in a tar file with an install script that installed the files 
stored in a incrypted image and included debian and ubuntu .deb packages for 
installing the speech-dispatcher module and gnome speech drivers but they 
were already out of date by the time I had gotten them.
Voxin did not come with the libs and header files from the IBMTTS SDK 
included which are needed for installing the ttsynth-say, 
spk-connect-ttsynth and the gnome speech driver so I had to download and 
install them manualy.
ttsynth comes in boath rpm and deb files, includes the files from the SDK 
needed for compiling ttsynth-say spk-connect-ttsynth and the gnome speech 
driver and the install files wern't incrypted so you can use alien just to 
convert and install on slackware.
*grin* that did not take long to write at all.
I went ahead and got voxin anyway as I guessed that it would be the same 
product rebranded and thought it would install better beeing in a tar ball 
rather than ttsynth's rpm and deb packages.
I was quite rong how ever I didn't know that the install files were stored 
in an incrypted image that was mounted using the install script and I didn't 
know that it would be missing the SDK which I think should have been 
included in with the voxin package instead of a bunch of outdated binarys 
stored in debian packages.
I was able to make voxin work with slackware after a while but I'd say that 
ttsynth had the better packages and I should have payed the extra $35 to get 
it as it would have saved me lots of trouble.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, June 02, 2008 4:09 PM
Subject: Re: IBMTTS on slackware


>I am happy enough recompiling the kernel, but I have just checked the
> slackware 12.1 configuration and it appears this is already done,
> cryptoloop is a module and aes options seem to be compiled in.
>
> I think my next step is to contact voxin and get a copy.
>
> Michael Whapples
> On Mon, 2008-06-02 at 11:39 -0400, Alex Snow wrote:
>> Voxin requires a kernel recompile to build the cryptoloop and aes
>> modules.
>> On Mon, Jun 02, 2008 at 01:42:05PM +0100, Michael Whapples
>> wrote:
>> > Good to hear that it is possible. Can I ask why you say voxin will be
>> > more of a problem? Considering the significant difference in price I
>> > would prefer to get voxin if possible. Its the high price of TTSynth
>> > which had made me question so much whether it would be worth the money,
>> > the question wasn't so high for voxin until you said that it might be
>> > more difficult on slackware. Might it be less painful if I were to use
>> > GRML for certain parts of voxin's install?
>> >
>> > I may discuss things with the voxin people to see if I could get them 
>> > to
>> > help me sort out a slackware version of voxin.
>> >
>> > Michael Whapples
>> > On Sun, 2008-06-01 at 18:01 -0400, Nick Stockton wrote:
>> > > I know it's doable because I helped a friend set up their copy of 
>> > > ttsynth on
>> > > their slackware box a while back.
>> > > I forget if it was slackware version 11 or 12 but I think the process 
>> > > would
>> > > be the same for eather one.
>> > > I've not ever seen any instructions on the speakup list on how to do 
>> > > it so
>> > > I'll write down what I did here.
>> > > Lucky for you I saved the commands I enterd to a text file so I'd 
>> > > know how
>> > > it was done although I'm using voxin which I got for $5 and am 
>> > > running it
>> > > under debian.
>> > > Note: this is for ttsynth under slackware. Voxin would be quite alot 
>> > > harder
>> > > to get working under slackware so you better get ttsynth.
>> > > I've also prepended the commands with '$ ' in case my email client 
>> > > tries to
>> > > wrap commands to the next line. So you'll be able to see where each 
>> > > line
>> > > begins.
>> > > You will need to run all the commands as root. You also need to have 
>> > > alien
>> > > installed.
>> > > If you don't want to find, download, compile and install alien and 
>> > > all the
>> > > dependencies from source to your copy of slackware then you might 
>> > > want to
>> > > download GRML and use it only to run the alien commands.
>> > > --------------------
>> > > $ wget
>> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
>> > > $ ldconfig
>> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
>> > > $ installpkg ttsynthcore-1.0.tgz
>> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
>> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
>> > > $ ldconfig
>> > > $ I know it's doable because I helped a friend set up their copy of 
>> > > ttsynth
>> > > on their slackware box.
>> > > I forget if it was slackware version 11 or 12 but I think the process 
>> > > would
>> > > be the same for eather one.
>> > > I've not ever seen any instructions on the speakup list on how to do 
>> > > it so
>> > > I'll write down what I did here.
>> > > Lucky for you I saved the commands I enterd to a text file so I'd 
>> > > know how
>> > > it was done although I'm using voxin which I got for $5 and am 
>> > > running it
>> > > under debian.
>> > > Note: this is for ttsynth under slackware. Voxin would be quite alot 
>> > > harder
>> > > to get working under slackware so you better get ttsynth.
>> > > I've also prepended the commands with '$ ' in case my email client 
>> > > tries to
>> > > wrap commands to the next line. So you'll be able to see where each 
>> > > line
>> > > begins.
>> > > You will need to run all the commands as root. You also need to have 
>> > > alien
>> > > installed.
>> > > If you don't want to find, download, compile and install alien and 
>> > > all the
>> > > dependencies from source to your copy of slackware then you might 
>> > > want to
>> > > download GRML and use it to run the alien commands.
>> > > --------------------
>> > > $ wget
>> > > http://http.us.debian.org/debian/pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ alien -t -c -k libstdc++2.10-glibc2.2_2.95.4-27_i386.deb
>> > > $ installpkg libstdc++2.10-glibc2.2-2.95.4.tgz
>> > > $ ldconfig
>> > > $ alien -t -c -k ttsynthcore-1.0-i386.deb
>> > > $ installpkg ttsynthcore-1.0.tgz
>> > > $ ln -s /opt/IBM/ibmtts/lib/enu50.so /usr/lib/enu50.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/enumfilt.so /usr/lib/enumfilt.so
>> > > $ ln -s /opt/IBM/ibmtts/lib/ssmlfilter.so /usr/lib/ssmlfilter.so
>> > > $ cp /opt/IBM/ibmtts/inc/* /usr/include/
>> > > $ ldconfig
>> > > $ mknod /dev/softsynth c 10 26
>> > > --------------------
>> > > Hope this helps.
>> > > ----- Original Message ----- 
>> > > From: "Michael Whapples" <mwhapples@aim.com>
>> > > To: <speakup@braille.uwo.ca>
>> > > Sent: Sunday, June 01, 2008 3:33 PM
>> > > Subject: IBMTTS on slackware
>> > >
>> > >
>> > >
>> > > > Hello,
>> > > > I know this has come up before, but I can't remember any actual 
>> > > > final
>> > > > conclusion.
>> > > >
>> > > > Whilst I thought espeak was fast enough, I found I had to use a 
>> > > > windows
>> > > > machine last week, and it reminded me how I do actually use 
>> > > > eloquence in
>> > > > windows faster than I have espeak. This has got me thinking whether 
>> > > > I
>> > > > should get IBMTTS for linux, but I have a few questions.
>> > > >
>> > > > I know that IBMTTS requires an old compatibility library, which I 
>> > > > am
>> > > > unsure is provided in slackware. So how could I go about trying to 
>> > > > get
>> > > > this library? Does anyone know of a suitable slackware package for 
>> > > > it?
>> > > > If not how might I go about providing this myself from source (I 
>> > > > had a
>> > > > look around for the source code I might need, but all libstdc++ 
>> > > > seems to
>> > > > have numbers such as 6.0.x etc much highrt than what the TTSynth 
>> > > > site
>> > > > suggests, 2.9.6 or 2.9.5). Could it be possible to use a package 
>> > > > from a
>> > > > different distribution, eg. I remember back in the days when I used
>> > > > trplayer, I could use rpm2tgz to convert the realplayer 8 package 
>> > > > into a
>> > > > slackware package and it worked fine, but I suspect that for 
>> > > > libstdc++
>> > > > compatibility libraries things may not be so simple.
>> > > >
>> > > > This brings me on to another question, whether to use voxin or 
>> > > > ttsynth?
>> > > > The ttsynth website says there won't be any support provided, so I 
>> > > > guess
>> > > > this means if I buy ttsynth and can't get it working then I am on 
>> > > > my own
>> > > > and may have wasted money on it. Might things be better with voxin,
>> > > > their website says that voxin includes the libstdc++ compatibility
>> > > > library (I guess for debian or ubuntu as those are the distros
>> > > > mentioned).
>> > > >
>> > > > Alternatively I am wondering whether it would be best save the 
>> > > > money and
>> > > > stick with espeak as it is good and works, where as ibmtts sounds 
>> > > > like I
>> > > > may hit all sorts of compatibility issues and potentially have no
>> > > > support from the seller.
>> > > >
>> > > > Michael Whapples
>> > > >
>> > > > _______________________________________________
>> > > > Speakup mailing list
>> > > > Speakup@braille.uwo.ca
>> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> > >
>> > >
>> > >
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: IBMTTS on slackware

[Michael Whapples]

On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
> By the way I'd expect less support than you get with ttsynth if you go with 
> voxin *grin*.
I had come to the conclusion before that I couldn't get less support
than ttsynth has, as on the ttsynth site it says that no personal
support for the product will be given. So I came to the decission that
it is best to pay less and chance support than pay more (much more) and
know that there won't be personal support for it.
> Before I baut Voxin I sent an email asking if there was any differences 
> between ttsynth and voxin besides the name and the price and I got a email 
> back with a single line saying I should ask on the speakup list *lol*.
One thing I think might be different between the two is that ttsynth
provides the speakup connector (by the sound of it, it provides it
directly rather than working through speech-dispatcher, is that true and
how does it compare to going through speech-dispatcher).
> I guess when something is $5 you shouldn't expect people to really put their 
> hearts in to selling it to you but I don't think it would have taken long to 
> send a message back with a couple of differences between the two.
> Any how in case you want to know the main differenses between voxin and 
> ttsynth are
> voxin came in a tar file with an install script that installed the files 
> stored in a incrypted image and included debian and ubuntu .deb packages for 
> installing the speech-dispatcher module and gnome speech drivers but they 
> were already out of date by the time I had gotten them.
> Voxin did not come with the libs and header files from the IBMTTS SDK 
> included which are needed for installing the ttsynth-say, 
> spk-connect-ttsynth and the gnome speech driver so I had to download and 
> install them manualy.
> ttsynth comes in boath rpm and deb files, includes the files from the SDK 
> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome speech 
> driver and the install files wern't incrypted so you can use alien just to 
> convert and install on slackware.
That encryption part is now getting me, I keep trying to enter the
passphrase and it keeps saying its wrong. I am sure slackware is
providing all the encryption stuff (cryptoloop as a module and aes
compiled in (although I have recompiled a kernel with it as a module as
well)) and I have tried installing it in GRML and get the same. I have
contacted oralux for support on this, lets see what my response is.
> *grin* that did not take long to write at all.
> I went ahead and got voxin anyway as I guessed that it would be the same 
> product rebranded and thought it would install better beeing in a tar ball 
> rather than ttsynth's rpm and deb packages.
> I was quite rong how ever I didn't know that the install files were stored 
> in an incrypted image that was mounted using the install script and I didn't 
> know that it would be missing the SDK which I think should have been 
> included in with the voxin package instead of a bunch of outdated binarys 
> stored in debian packages.
> I was able to make voxin work with slackware after a while but I'd say that 
> ttsynth had the better packages and I should have payed the extra $35 to get 
> it as it would have saved me lots of trouble.
May be I should have followed your advice, but I made the same
conclusions you had (with the extra one that surely the encryption won't
be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could you
enlighten me on the encryption problem?

Re: IBMTTS on slackware

[Nick Stockton]

Well the file can be extracted with debian and ubuntu so what you could do 
is edit the install script and see what commands it is using to mount the 
image.
Then you can mount that file under Ubuntu or Maybe GRML I think it should 
work too.
then copy the stuff in the mounted dir to a tempory folder and then umount 
and delete the image.
After that copy the extracted files back to the place where the image had 
been mounted I think it's the mnt dir in the voxin directory.
then edit the installer script and remove the mount and umount commands.
After that I think it would then copy the files from the dir with out 
mounting anything and you can just make a tar ball of that package and just 
use that one if you ever have to install again and junk the one you got from 
voxin's site.
I think ttsynth is the better package but I guess when buying cheep I got 
what I payed for but at least it does work on my debian system now that I've 
stopped using slackware.
I think slackware is the most stable of all the gnu/linux flavors but I got 
tired of having to google for packages and then googling all the packages 
they needed to run and compiling/installing/configuring them so I use debian 
now.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, June 03, 2008 6:36 PM
Subject: Re: IBMTTS on slackware


> On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
>> By the way I'd expect less support than you get with ttsynth if you go 
>> with
>> voxin *grin*.
> I had come to the conclusion before that I couldn't get less support
> than ttsynth has, as on the ttsynth site it says that no personal
> support for the product will be given. So I came to the decission that
> it is best to pay less and chance support than pay more (much more) and
> know that there won't be personal support for it.
>> Before I baut Voxin I sent an email asking if there was any differences
>> between ttsynth and voxin besides the name and the price and I got a 
>> email
>> back with a single line saying I should ask on the speakup list *lol*.
> One thing I think might be different between the two is that ttsynth
> provides the speakup connector (by the sound of it, it provides it
> directly rather than working through speech-dispatcher, is that true and
> how does it compare to going through speech-dispatcher).
>> I guess when something is $5 you shouldn't expect people to really put 
>> their
>> hearts in to selling it to you but I don't think it would have taken long 
>> to
>> send a message back with a couple of differences between the two.
>> Any how in case you want to know the main differenses between voxin and
>> ttsynth are
>> voxin came in a tar file with an install script that installed the files
>> stored in a incrypted image and included debian and ubuntu .deb packages 
>> for
>> installing the speech-dispatcher module and gnome speech drivers but they
>> were already out of date by the time I had gotten them.
>> Voxin did not come with the libs and header files from the IBMTTS SDK
>> included which are needed for installing the ttsynth-say,
>> spk-connect-ttsynth and the gnome speech driver so I had to download and
>> install them manualy.
>> ttsynth comes in boath rpm and deb files, includes the files from the SDK
>> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome speech
>> driver and the install files wern't incrypted so you can use alien just 
>> to
>> convert and install on slackware.
> That encryption part is now getting me, I keep trying to enter the
> passphrase and it keeps saying its wrong. I am sure slackware is
> providing all the encryption stuff (cryptoloop as a module and aes
> compiled in (although I have recompiled a kernel with it as a module as
> well)) and I have tried installing it in GRML and get the same. I have
> contacted oralux for support on this, lets see what my response is.
>> *grin* that did not take long to write at all.
>> I went ahead and got voxin anyway as I guessed that it would be the same
>> product rebranded and thought it would install better beeing in a tar 
>> ball
>> rather than ttsynth's rpm and deb packages.
>> I was quite rong how ever I didn't know that the install files were 
>> stored
>> in an incrypted image that was mounted using the install script and I 
>> didn't
>> know that it would be missing the SDK which I think should have been
>> included in with the voxin package instead of a bunch of outdated binarys
>> stored in debian packages.
>> I was able to make voxin work with slackware after a while but I'd say 
>> that
>> ttsynth had the better packages and I should have payed the extra $35 to 
>> get
>> it as it would have saved me lots of trouble.
> May be I should have followed your advice, but I made the same
> conclusions you had (with the extra one that surely the encryption won't
> be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could you
> enlighten me on the encryption problem?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 3156 (20080603) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
> 

Re: IBMTTS on slackware

[Michael Whapples]

Well your experience seems slightly diffeent with the voxin people, I
got a version of it sent to me which had the encrypted partition removed
when I had contacted them with the problem of the pass phrase not
working.

Yes it would have been nice to have had the packages up to date, but as
I am using slackware I expected to need to compile the supporting
applications anyway for either TTSynth or voxin. There are a couple of
things I am noticing between the different drivers. the
speech-dispatcher one seems to very quickly decide to spell things,
where as the gnome-speech one seems to work a lot more naturally (eg. I
have the list set to digest mode and it comes from
speakup-request@braille.uwo.ca, with speech-dispatcher it spells out the
request word, where as gnome-speech says each word). Thinking about
gnome-speech, when I recompiled it to include IBMTTS I noticed it also
has a driver for eloquence. Why has viavoice become most talked about on
linux, and which is most up to date with current libraries (as up to
date as they may be, which uses the least obsolete), what are the
differences, etc?

From
Michael Whapples
On Tue, 2008-06-03 at 20:27 -0400, Nick Stockton wrote:
> Well the file can be extracted with debian and ubuntu so what you could do 
> is edit the install script and see what commands it is using to mount the 
> image.
> Then you can mount that file under Ubuntu or Maybe GRML I think it should 
> work too.
> then copy the stuff in the mounted dir to a tempory folder and then umount 
> and delete the image.
> After that copy the extracted files back to the place where the image had 
> been mounted I think it's the mnt dir in the voxin directory.
> then edit the installer script and remove the mount and umount commands.
> After that I think it would then copy the files from the dir with out 
> mounting anything and you can just make a tar ball of that package and just 
> use that one if you ever have to install again and junk the one you got from 
> voxin's site.
> I think ttsynth is the better package but I guess when buying cheep I got 
> what I payed for but at least it does work on my debian system now that I've 
> stopped using slackware.
> I think slackware is the most stable of all the gnu/linux flavors but I got 
> tired of having to google for packages and then googling all the packages 
> they needed to run and compiling/installing/configuring them so I use debian 
> now.
> ----- Original Message ----- 
> From: "Michael Whapples" <mwhapples@aim.com>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Tuesday, June 03, 2008 6:36 PM
> Subject: Re: IBMTTS on slackware
> 
> 
> 
> > On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
> >> By the way I'd expect less support than you get with ttsynth if you go 
> >> with
> >> voxin *grin*.
> > I had come to the conclusion before that I couldn't get less support
> > than ttsynth has, as on the ttsynth site it says that no personal
> > support for the product will be given. So I came to the decission that
> > it is best to pay less and chance support than pay more (much more) and
> > know that there won't be personal support for it.
> >> Before I baut Voxin I sent an email asking if there was any differences
> >> between ttsynth and voxin besides the name and the price and I got a 
> >> email
> >> back with a single line saying I should ask on the speakup list *lol*.
> > One thing I think might be different between the two is that ttsynth
> > provides the speakup connector (by the sound of it, it provides it
> > directly rather than working through speech-dispatcher, is that true and
> > how does it compare to going through speech-dispatcher).
> >> I guess when something is $5 you shouldn't expect people to really put 
> >> their
> >> hearts in to selling it to you but I don't think it would have taken long 
> >> to
> >> send a message back with a couple of differences between the two.
> >> Any how in case you want to know the main differenses between voxin and
> >> ttsynth are
> >> voxin came in a tar file with an install script that installed the files
> >> stored in a incrypted image and included debian and ubuntu .deb packages 
> >> for
> >> installing the speech-dispatcher module and gnome speech drivers but they
> >> were already out of date by the time I had gotten them.
> >> Voxin did not come with the libs and header files from the IBMTTS SDK
> >> included which are needed for installing the ttsynth-say,
> >> spk-connect-ttsynth and the gnome speech driver so I had to download and
> >> install them manualy.
> >> ttsynth comes in boath rpm and deb files, includes the files from the SDK
> >> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome speech
> >> driver and the install files wern't incrypted so you can use alien just 
> >> to
> >> convert and install on slackware.
> > That encryption part is now getting me, I keep trying to enter the
> > passphrase and it keeps saying its wrong. I am sure slackware is
> > providing all the encryption stuff (cryptoloop as a module and aes
> > compiled in (although I have recompiled a kernel with it as a module as
> > well)) and I have tried installing it in GRML and get the same. I have
> > contacted oralux for support on this, lets see what my response is.
> >> *grin* that did not take long to write at all.
> >> I went ahead and got voxin anyway as I guessed that it would be the same
> >> product rebranded and thought it would install better beeing in a tar 
> >> ball
> >> rather than ttsynth's rpm and deb packages.
> >> I was quite rong how ever I didn't know that the install files were 
> >> stored
> >> in an incrypted image that was mounted using the install script and I 
> >> didn't
> >> know that it would be missing the SDK which I think should have been
> >> included in with the voxin package instead of a bunch of outdated binarys
> >> stored in debian packages.
> >> I was able to make voxin work with slackware after a while but I'd say 
> >> that
> >> ttsynth had the better packages and I should have payed the extra $35 to 
> >> get
> >> it as it would have saved me lots of trouble.
> > May be I should have followed your advice, but I made the same
> > conclusions you had (with the extra one that surely the encryption won't
> > be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could you
> > enlighten me on the encryption problem?
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > __________ Information from ESET Smart Security, version of virus 
> > signature database 3156 (20080603) __________
> >
> > The message was checked by ESET Smart Security.
> >
> > http://www.eset.com
> >
> > 
> 
> 
> 

Re: IBMTTS on slackware

[Nick Stockton]

Funny that you should menchen that because I've noticed speech-dispatcher 
spelling stuff sometimes.
I still use it though because on my old desktop gnome-speech has alot more 
lag than speech-dispatcher and I couldnt get the IBMTTS gnome-speech server 
to use alsa.
I was thinking that maybe I hadn't played around with it enough as I had 
just set it up to try gnome and see what it was like as I use speakup for 
most stuff apart from web browsing, audio editing and voice chat.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, June 04, 2008 5:33 PM
Subject: Re: IBMTTS on slackware


> Well your experience seems slightly diffeent with the voxin people, I
> got a version of it sent to me which had the encrypted partition removed
> when I had contacted them with the problem of the pass phrase not
> working.
>
> Yes it would have been nice to have had the packages up to date, but as
> I am using slackware I expected to need to compile the supporting
> applications anyway for either TTSynth or voxin. There are a couple of
> things I am noticing between the different drivers. the
> speech-dispatcher one seems to very quickly decide to spell things,
> where as the gnome-speech one seems to work a lot more naturally (eg. I
> have the list set to digest mode and it comes from
> speakup-request@braille.uwo.ca, with speech-dispatcher it spells out the
> request word, where as gnome-speech says each word). Thinking about
> gnome-speech, when I recompiled it to include IBMTTS I noticed it also
> has a driver for eloquence. Why has viavoice become most talked about on
> linux, and which is most up to date with current libraries (as up to
> date as they may be, which uses the least obsolete), what are the
> differences, etc?
>
> From
> Michael Whapples
> On Tue, 2008-06-03 at 20:27 -0400, Nick Stockton wrote:
>> Well the file can be extracted with debian and ubuntu so what you could 
>> do
>> is edit the install script and see what commands it is using to mount the
>> image.
>> Then you can mount that file under Ubuntu or Maybe GRML I think it should
>> work too.
>> then copy the stuff in the mounted dir to a tempory folder and then 
>> umount
>> and delete the image.
>> After that copy the extracted files back to the place where the image had
>> been mounted I think it's the mnt dir in the voxin directory.
>> then edit the installer script and remove the mount and umount commands.
>> After that I think it would then copy the files from the dir with out
>> mounting anything and you can just make a tar ball of that package and 
>> just
>> use that one if you ever have to install again and junk the one you got 
>> from
>> voxin's site.
>> I think ttsynth is the better package but I guess when buying cheep I got
>> what I payed for but at least it does work on my debian system now that 
>> I've
>> stopped using slackware.
>> I think slackware is the most stable of all the gnu/linux flavors but I 
>> got
>> tired of having to google for packages and then googling all the packages
>> they needed to run and compiling/installing/configuring them so I use 
>> debian
>> now.
>> ----- Original Message ----- 
>> From: "Michael Whapples" <mwhapples@aim.com>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Tuesday, June 03, 2008 6:36 PM
>> Subject: Re: IBMTTS on slackware
>>
>>
>>
>> > On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
>> >> By the way I'd expect less support than you get with ttsynth if you go
>> >> with
>> >> voxin *grin*.
>> > I had come to the conclusion before that I couldn't get less support
>> > than ttsynth has, as on the ttsynth site it says that no personal
>> > support for the product will be given. So I came to the decission that
>> > it is best to pay less and chance support than pay more (much more) and
>> > know that there won't be personal support for it.
>> >> Before I baut Voxin I sent an email asking if there was any 
>> >> differences
>> >> between ttsynth and voxin besides the name and the price and I got a
>> >> email
>> >> back with a single line saying I should ask on the speakup list *lol*.
>> > One thing I think might be different between the two is that ttsynth
>> > provides the speakup connector (by the sound of it, it provides it
>> > directly rather than working through speech-dispatcher, is that true 
>> > and
>> > how does it compare to going through speech-dispatcher).
>> >> I guess when something is $5 you shouldn't expect people to really put
>> >> their
>> >> hearts in to selling it to you but I don't think it would have taken 
>> >> long
>> >> to
>> >> send a message back with a couple of differences between the two.
>> >> Any how in case you want to know the main differenses between voxin 
>> >> and
>> >> ttsynth are
>> >> voxin came in a tar file with an install script that installed the 
>> >> files
>> >> stored in a incrypted image and included debian and ubuntu .deb 
>> >> packages
>> >> for
>> >> installing the speech-dispatcher module and gnome speech drivers but 
>> >> they
>> >> were already out of date by the time I had gotten them.
>> >> Voxin did not come with the libs and header files from the IBMTTS SDK
>> >> included which are needed for installing the ttsynth-say,
>> >> spk-connect-ttsynth and the gnome speech driver so I had to download 
>> >> and
>> >> install them manualy.
>> >> ttsynth comes in boath rpm and deb files, includes the files from the 
>> >> SDK
>> >> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome 
>> >> speech
>> >> driver and the install files wern't incrypted so you can use alien 
>> >> just
>> >> to
>> >> convert and install on slackware.
>> > That encryption part is now getting me, I keep trying to enter the
>> > passphrase and it keeps saying its wrong. I am sure slackware is
>> > providing all the encryption stuff (cryptoloop as a module and aes
>> > compiled in (although I have recompiled a kernel with it as a module as
>> > well)) and I have tried installing it in GRML and get the same. I have
>> > contacted oralux for support on this, lets see what my response is.
>> >> *grin* that did not take long to write at all.
>> >> I went ahead and got voxin anyway as I guessed that it would be the 
>> >> same
>> >> product rebranded and thought it would install better beeing in a tar
>> >> ball
>> >> rather than ttsynth's rpm and deb packages.
>> >> I was quite rong how ever I didn't know that the install files were
>> >> stored
>> >> in an incrypted image that was mounted using the install script and I
>> >> didn't
>> >> know that it would be missing the SDK which I think should have been
>> >> included in with the voxin package instead of a bunch of outdated 
>> >> binarys
>> >> stored in debian packages.
>> >> I was able to make voxin work with slackware after a while but I'd say
>> >> that
>> >> ttsynth had the better packages and I should have payed the extra $35 
>> >> to
>> >> get
>> >> it as it would have saved me lots of trouble.
>> > May be I should have followed your advice, but I made the same
>> > conclusions you had (with the extra one that surely the encryption 
>> > won't
>> > be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could 
>> > you
>> > enlighten me on the encryption problem?
>> >
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >
>> > __________ Information from ESET Smart Security, version of virus
>> > signature database 3156 (20080603) __________
>> >
>> > The message was checked by ESET Smart Security.
>> >
>> > http://www.eset.com
>> >
>> >
>>
>>
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 3156 (20080603) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
> 

Re: IBMTTS on slackware

[Michael Whapples]

Hello,
I think (going from memory and not looking back at messages on the orca
list) some of the problems regarding speech-dispatcher and orca come
from is that the orca team and speech-dispatcher teams have slightly
different oppinions on what should do what. Gnome-speech is the main
supported output for speech in orca, I think the speech-dispatcher one
isn't officially supported.

As far as getting gnome-speech to use alsa, you will need to edit a file
(for viavoice it
is /usr/lib/bonobo/severs/GNOME_Speech_SynthesisDriver_Viavoice.server)
and edit the location attribute (I can't remember which XML tag it
belongs to, but that element also has an attribute type="exe") and
modify the value to include aoss (eg.
aoss /usr/bin/viavoice-synthesis-driver). NOTE: this also works for
espeak in gnome-speech.

Michael Whapples
On Fri, 2008-06-06 at 00:26 -0400, Nick Stockton wrote:
> Funny that you should menchen that because I've noticed speech-dispatcher 
> spelling stuff sometimes.
> I still use it though because on my old desktop gnome-speech has alot more 
> lag than speech-dispatcher and I couldnt get the IBMTTS gnome-speech server 
> to use alsa.
> I was thinking that maybe I hadn't played around with it enough as I had 
> just set it up to try gnome and see what it was like as I use speakup for 
> most stuff apart from web browsing, audio editing and voice chat.
> ----- Original Message ----- 
> From: "Michael Whapples" <mwhapples@aim.com>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Wednesday, June 04, 2008 5:33 PM
> Subject: Re: IBMTTS on slackware
> 
> 
> 
> > Well your experience seems slightly diffeent with the voxin people, I
> > got a version of it sent to me which had the encrypted partition removed
> > when I had contacted them with the problem of the pass phrase not
> > working.
> >
> > Yes it would have been nice to have had the packages up to date, but as
> > I am using slackware I expected to need to compile the supporting
> > applications anyway for either TTSynth or voxin. There are a couple of
> > things I am noticing between the different drivers. the
> > speech-dispatcher one seems to very quickly decide to spell things,
> > where as the gnome-speech one seems to work a lot more naturally (eg. I
> > have the list set to digest mode and it comes from
> > speakup-request@braille.uwo.ca, with speech-dispatcher it spells out the
> > request word, where as gnome-speech says each word). Thinking about
> > gnome-speech, when I recompiled it to include IBMTTS I noticed it also
> > has a driver for eloquence. Why has viavoice become most talked about on
> > linux, and which is most up to date with current libraries (as up to
> > date as they may be, which uses the least obsolete), what are the
> > differences, etc?
> >
> > From
> > Michael Whapples
> > On Tue, 2008-06-03 at 20:27 -0400, Nick Stockton wrote:
> >> Well the file can be extracted with debian and ubuntu so what you could 
> >> do
> >> is edit the install script and see what commands it is using to mount the
> >> image.
> >> Then you can mount that file under Ubuntu or Maybe GRML I think it should
> >> work too.
> >> then copy the stuff in the mounted dir to a tempory folder and then 
> >> umount
> >> and delete the image.
> >> After that copy the extracted files back to the place where the image had
> >> been mounted I think it's the mnt dir in the voxin directory.
> >> then edit the installer script and remove the mount and umount commands.
> >> After that I think it would then copy the files from the dir with out
> >> mounting anything and you can just make a tar ball of that package and 
> >> just
> >> use that one if you ever have to install again and junk the one you got 
> >> from
> >> voxin's site.
> >> I think ttsynth is the better package but I guess when buying cheep I got
> >> what I payed for but at least it does work on my debian system now that 
> >> I've
> >> stopped using slackware.
> >> I think slackware is the most stable of all the gnu/linux flavors but I 
> >> got
> >> tired of having to google for packages and then googling all the packages
> >> they needed to run and compiling/installing/configuring them so I use 
> >> debian
> >> now.
> >> ----- Original Message ----- 
> >> From: "Michael Whapples" <mwhapples@aim.com>
> >> To: "Speakup is a screen review system for Linux." 
> >> <speakup@braille.uwo.ca>
> >> Sent: Tuesday, June 03, 2008 6:36 PM
> >> Subject: Re: IBMTTS on slackware
> >>
> >>
> >>
> >> > On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
> >> >> By the way I'd expect less support than you get with ttsynth if you go
> >> >> with
> >> >> voxin *grin*.
> >> > I had come to the conclusion before that I couldn't get less support
> >> > than ttsynth has, as on the ttsynth site it says that no personal
> >> > support for the product will be given. So I came to the decission that
> >> > it is best to pay less and chance support than pay more (much more) and
> >> > know that there won't be personal support for it.
> >> >> Before I baut Voxin I sent an email asking if there was any 
> >> >> differences
> >> >> between ttsynth and voxin besides the name and the price and I got a
> >> >> email
> >> >> back with a single line saying I should ask on the speakup list *lol*.
> >> > One thing I think might be different between the two is that ttsynth
> >> > provides the speakup connector (by the sound of it, it provides it
> >> > directly rather than working through speech-dispatcher, is that true 
> >> > and
> >> > how does it compare to going through speech-dispatcher).
> >> >> I guess when something is $5 you shouldn't expect people to really put
> >> >> their
> >> >> hearts in to selling it to you but I don't think it would have taken 
> >> >> long
> >> >> to
> >> >> send a message back with a couple of differences between the two.
> >> >> Any how in case you want to know the main differenses between voxin 
> >> >> and
> >> >> ttsynth are
> >> >> voxin came in a tar file with an install script that installed the 
> >> >> files
> >> >> stored in a incrypted image and included debian and ubuntu .deb 
> >> >> packages
> >> >> for
> >> >> installing the speech-dispatcher module and gnome speech drivers but 
> >> >> they
> >> >> were already out of date by the time I had gotten them.
> >> >> Voxin did not come with the libs and header files from the IBMTTS SDK
> >> >> included which are needed for installing the ttsynth-say,
> >> >> spk-connect-ttsynth and the gnome speech driver so I had to download 
> >> >> and
> >> >> install them manualy.
> >> >> ttsynth comes in boath rpm and deb files, includes the files from the 
> >> >> SDK
> >> >> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome 
> >> >> speech
> >> >> driver and the install files wern't incrypted so you can use alien 
> >> >> just
> >> >> to
> >> >> convert and install on slackware.
> >> > That encryption part is now getting me, I keep trying to enter the
> >> > passphrase and it keeps saying its wrong. I am sure slackware is
> >> > providing all the encryption stuff (cryptoloop as a module and aes
> >> > compiled in (although I have recompiled a kernel with it as a module as
> >> > well)) and I have tried installing it in GRML and get the same. I have
> >> > contacted oralux for support on this, lets see what my response is.
> >> >> *grin* that did not take long to write at all.
> >> >> I went ahead and got voxin anyway as I guessed that it would be the 
> >> >> same
> >> >> product rebranded and thought it would install better beeing in a tar
> >> >> ball
> >> >> rather than ttsynth's rpm and deb packages.
> >> >> I was quite rong how ever I didn't know that the install files were
> >> >> stored
> >> >> in an incrypted image that was mounted using the install script and I
> >> >> didn't
> >> >> know that it would be missing the SDK which I think should have been
> >> >> included in with the voxin package instead of a bunch of outdated 
> >> >> binarys
> >> >> stored in debian packages.
> >> >> I was able to make voxin work with slackware after a while but I'd say
> >> >> that
> >> >> ttsynth had the better packages and I should have payed the extra $35 
> >> >> to
> >> >> get
> >> >> it as it would have saved me lots of trouble.
> >> > May be I should have followed your advice, but I made the same
> >> > conclusions you had (with the extra one that surely the encryption 
> >> > won't
> >> > be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could 
> >> > you
> >> > enlighten me on the encryption problem?
> >> >
> >> >
> >> > _______________________________________________
> >> > Speakup mailing list
> >> > Speakup@braille.uwo.ca
> >> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >> >
> >> > __________ Information from ESET Smart Security, version of virus
> >> > signature database 3156 (20080603) __________
> >> >
> >> > The message was checked by ESET Smart Security.
> >> >
> >> > http://www.eset.com
> >> >
> >> >
> >>
> >>
> >>
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > __________ Information from ESET Smart Security, version of virus 
> > signature database 3156 (20080603) __________
> >
> > The message was checked by ESET Smart Security.
> >
> > http://www.eset.com
> >
> > 
> 
> 
> 

Re: IBMTTS on slackware

[Nick Stockton]

*nods* I remember trying that but it didn't seem to work.
it was making the sound start out speaking a few words very fast then it 
would freez and not speak at all.
I kind of wonder if it was because I have my USB sound card set to output 
44,100HZ in /etc/asound.comf and viavoice would be using 22,000HZ.
When ever I get a faster computer I'll probbely try running gnome-speech 
again but at the momentgnome speech is not very responcive on my computer 
and speech-dispatcher is quite a bit more responcive.
I kind of wonder what is causing it to spell some words but not others 
though... Very strange.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, June 06, 2008 3:36 PM
Subject: Re: IBMTTS on slackware


> Hello,
> I think (going from memory and not looking back at messages on the orca
> list) some of the problems regarding speech-dispatcher and orca come
> from is that the orca team and speech-dispatcher teams have slightly
> different oppinions on what should do what. Gnome-speech is the main
> supported output for speech in orca, I think the speech-dispatcher one
> isn't officially supported.
>
> As far as getting gnome-speech to use alsa, you will need to edit a file
> (for viavoice it
> is /usr/lib/bonobo/severs/GNOME_Speech_SynthesisDriver_Viavoice.server)
> and edit the location attribute (I can't remember which XML tag it
> belongs to, but that element also has an attribute type="exe") and
> modify the value to include aoss (eg.
> aoss /usr/bin/viavoice-synthesis-driver). NOTE: this also works for
> espeak in gnome-speech.
>
> Michael Whapples
> On Fri, 2008-06-06 at 00:26 -0400, Nick Stockton wrote:
>> Funny that you should menchen that because I've noticed speech-dispatcher
>> spelling stuff sometimes.
>> I still use it though because on my old desktop gnome-speech has alot 
>> more
>> lag than speech-dispatcher and I couldnt get the IBMTTS gnome-speech 
>> server
>> to use alsa.
>> I was thinking that maybe I hadn't played around with it enough as I had
>> just set it up to try gnome and see what it was like as I use speakup for
>> most stuff apart from web browsing, audio editing and voice chat.
>> ----- Original Message ----- 
>> From: "Michael Whapples" <mwhapples@aim.com>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Wednesday, June 04, 2008 5:33 PM
>> Subject: Re: IBMTTS on slackware
>>
>>
>>
>> > Well your experience seems slightly diffeent with the voxin people, I
>> > got a version of it sent to me which had the encrypted partition 
>> > removed
>> > when I had contacted them with the problem of the pass phrase not
>> > working.
>> >
>> > Yes it would have been nice to have had the packages up to date, but as
>> > I am using slackware I expected to need to compile the supporting
>> > applications anyway for either TTSynth or voxin. There are a couple of
>> > things I am noticing between the different drivers. the
>> > speech-dispatcher one seems to very quickly decide to spell things,
>> > where as the gnome-speech one seems to work a lot more naturally (eg. I
>> > have the list set to digest mode and it comes from
>> > speakup-request@braille.uwo.ca, with speech-dispatcher it spells out 
>> > the
>> > request word, where as gnome-speech says each word). Thinking about
>> > gnome-speech, when I recompiled it to include IBMTTS I noticed it also
>> > has a driver for eloquence. Why has viavoice become most talked about 
>> > on
>> > linux, and which is most up to date with current libraries (as up to
>> > date as they may be, which uses the least obsolete), what are the
>> > differences, etc?
>> >
>> > From
>> > Michael Whapples
>> > On Tue, 2008-06-03 at 20:27 -0400, Nick Stockton wrote:
>> >> Well the file can be extracted with debian and ubuntu so what you 
>> >> could
>> >> do
>> >> is edit the install script and see what commands it is using to mount 
>> >> the
>> >> image.
>> >> Then you can mount that file under Ubuntu or Maybe GRML I think it 
>> >> should
>> >> work too.
>> >> then copy the stuff in the mounted dir to a tempory folder and then
>> >> umount
>> >> and delete the image.
>> >> After that copy the extracted files back to the place where the image 
>> >> had
>> >> been mounted I think it's the mnt dir in the voxin directory.
>> >> then edit the installer script and remove the mount and umount 
>> >> commands.
>> >> After that I think it would then copy the files from the dir with out
>> >> mounting anything and you can just make a tar ball of that package and
>> >> just
>> >> use that one if you ever have to install again and junk the one you 
>> >> got
>> >> from
>> >> voxin's site.
>> >> I think ttsynth is the better package but I guess when buying cheep I 
>> >> got
>> >> what I payed for but at least it does work on my debian system now 
>> >> that
>> >> I've
>> >> stopped using slackware.
>> >> I think slackware is the most stable of all the gnu/linux flavors but 
>> >> I
>> >> got
>> >> tired of having to google for packages and then googling all the 
>> >> packages
>> >> they needed to run and compiling/installing/configuring them so I use
>> >> debian
>> >> now.
>> >> ----- Original Message ----- 
>> >> From: "Michael Whapples" <mwhapples@aim.com>
>> >> To: "Speakup is a screen review system for Linux."
>> >> <speakup@braille.uwo.ca>
>> >> Sent: Tuesday, June 03, 2008 6:36 PM
>> >> Subject: Re: IBMTTS on slackware
>> >>
>> >>
>> >>
>> >> > On Mon, 2008-06-02 at 18:47 -0400, Nick Stockton wrote:
>> >> >> By the way I'd expect less support than you get with ttsynth if you 
>> >> >> go
>> >> >> with
>> >> >> voxin *grin*.
>> >> > I had come to the conclusion before that I couldn't get less support
>> >> > than ttsynth has, as on the ttsynth site it says that no personal
>> >> > support for the product will be given. So I came to the decission 
>> >> > that
>> >> > it is best to pay less and chance support than pay more (much more) 
>> >> > and
>> >> > know that there won't be personal support for it.
>> >> >> Before I baut Voxin I sent an email asking if there was any
>> >> >> differences
>> >> >> between ttsynth and voxin besides the name and the price and I got 
>> >> >> a
>> >> >> email
>> >> >> back with a single line saying I should ask on the speakup list 
>> >> >> *lol*.
>> >> > One thing I think might be different between the two is that ttsynth
>> >> > provides the speakup connector (by the sound of it, it provides it
>> >> > directly rather than working through speech-dispatcher, is that true
>> >> > and
>> >> > how does it compare to going through speech-dispatcher).
>> >> >> I guess when something is $5 you shouldn't expect people to really 
>> >> >> put
>> >> >> their
>> >> >> hearts in to selling it to you but I don't think it would have 
>> >> >> taken
>> >> >> long
>> >> >> to
>> >> >> send a message back with a couple of differences between the two.
>> >> >> Any how in case you want to know the main differenses between voxin
>> >> >> and
>> >> >> ttsynth are
>> >> >> voxin came in a tar file with an install script that installed the
>> >> >> files
>> >> >> stored in a incrypted image and included debian and ubuntu .deb
>> >> >> packages
>> >> >> for
>> >> >> installing the speech-dispatcher module and gnome speech drivers 
>> >> >> but
>> >> >> they
>> >> >> were already out of date by the time I had gotten them.
>> >> >> Voxin did not come with the libs and header files from the IBMTTS 
>> >> >> SDK
>> >> >> included which are needed for installing the ttsynth-say,
>> >> >> spk-connect-ttsynth and the gnome speech driver so I had to 
>> >> >> download
>> >> >> and
>> >> >> install them manualy.
>> >> >> ttsynth comes in boath rpm and deb files, includes the files from 
>> >> >> the
>> >> >> SDK
>> >> >> needed for compiling ttsynth-say spk-connect-ttsynth and the gnome
>> >> >> speech
>> >> >> driver and the install files wern't incrypted so you can use alien
>> >> >> just
>> >> >> to
>> >> >> convert and install on slackware.
>> >> > That encryption part is now getting me, I keep trying to enter the
>> >> > passphrase and it keeps saying its wrong. I am sure slackware is
>> >> > providing all the encryption stuff (cryptoloop as a module and aes
>> >> > compiled in (although I have recompiled a kernel with it as a module 
>> >> > as
>> >> > well)) and I have tried installing it in GRML and get the same. I 
>> >> > have
>> >> > contacted oralux for support on this, lets see what my response is.
>> >> >> *grin* that did not take long to write at all.
>> >> >> I went ahead and got voxin anyway as I guessed that it would be the
>> >> >> same
>> >> >> product rebranded and thought it would install better beeing in a 
>> >> >> tar
>> >> >> ball
>> >> >> rather than ttsynth's rpm and deb packages.
>> >> >> I was quite rong how ever I didn't know that the install files were
>> >> >> stored
>> >> >> in an incrypted image that was mounted using the install script and 
>> >> >> I
>> >> >> didn't
>> >> >> know that it would be missing the SDK which I think should have 
>> >> >> been
>> >> >> included in with the voxin package instead of a bunch of outdated
>> >> >> binarys
>> >> >> stored in debian packages.
>> >> >> I was able to make voxin work with slackware after a while but I'd 
>> >> >> say
>> >> >> that
>> >> >> ttsynth had the better packages and I should have payed the extra 
>> >> >> $35
>> >> >> to
>> >> >> get
>> >> >> it as it would have saved me lots of trouble.
>> >> > May be I should have followed your advice, but I made the same
>> >> > conclusions you had (with the extra one that surely the encryption
>> >> > won't
>> >> > be a problem) and I spent my $5 (actually 4.29 euro) on voxin. Could
>> >> > you
>> >> > enlighten me on the encryption problem?
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Speakup mailing list
>> >> > Speakup@braille.uwo.ca
>> >> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >> >
>> >> > __________ Information from ESET Smart Security, version of virus
>> >> > signature database 3156 (20080603) __________
>> >> >
>> >> > The message was checked by ESET Smart Security.
>> >> >
>> >> > http://www.eset.com
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >
>> > __________ Information from ESET Smart Security, version of virus
>> > signature database 3156 (20080603) __________
>> >
>> > The message was checked by ESET Smart Security.
>> >
>> > http://www.eset.com
>> >
>> >
>>
>>
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 3156 (20080603) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
> 

Re: IBMTTS on slackware

[Michael Whapples]

On Fri, 2008-06-06 at 20:46 -0400, Nick Stockton wrote:
> *nods* I remember trying that but it didn't seem to work.
> it was making the sound start out speaking a few words very fast then it 
> would freez and not speak at all.
Speaking fast in gnome-speech might be due to the fact that gnome-speech
seems to be able to reach much higher speeds than speech-dispatcher does
(on my system I need to set speech-dispatcher to full (99) in orca to
achieve what seems nearly fast enough where as whith gnome-speech I am
dropping it down to about 60 (although I may speech it up once I have
tuned it a bit better for pitch and such like)).
> I kind of wonder if it was because I have my USB sound card set to output 
> 44,100HZ in /etc/asound.comf and viavoice would be using 22,000HZ.
What was the rate of speech when using gnome-speech's test application
(test-speech)? If this seemed the fairly standard slow default speed
applications normally set then sample rate conversion is probably
occurring. It's quite common for alsa to resample for you, any device
you set up as plug or to use dmix will automatically resample for you.
> When ever I get a faster computer I'll probbely try running gnome-speech 
> again but at the momentgnome speech is not very responcive on my computer 
> and speech-dispatcher is quite a bit more responcive.
> I kind of wonder what is causing it to spell some words but not others 
> though... Very strange.
>From what I can tell, the following causes speech-dispatcher (when using
orca, when using speechd-up I think I got slightly different results):
If the word contains non-alphabetic characters (eg.
speakup-request@braille.uwo.ca gets some parts spelt)
If something has capitals in the midst of it (eg. java variable names or
method names, although the method names will have non-alphabetic
characters after it))

Those above rules probably could be improved upon to be more specific
but it's a starting point. Some words get spelt by gnome-speech, but
this is less frequent and I am still working when this occurs. I don't
remember espeak doing this so much so I don't think it's in the main
speech-dispatcher code just the ibmtts module or ibmtts itself.

Michael Whapples

Re: IBMTTS on slackware

[Nick Stockton]

I think I described it rong, damn dyslexia *grin*.
What I ment is that it sounded sped up sort of like a tape player that is 
sped up or when you raze the sampling rate of a recording in an audio 
editor.
I think the technical term would be "that alven and the chipmunks sound." 
*giggle*.
It would speak like that for a sec or two then it would stop speaking.
This was only when I modified it to use aoss for OSS emulation in alsa.
after changing it back to the way it was before it didn't have that problem.
----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 07, 2008 5:57 PM
Subject: Re: IBMTTS on slackware


> On Fri, 2008-06-06 at 20:46 -0400, Nick Stockton wrote:
>> *nods* I remember trying that but it didn't seem to work.
>> it was making the sound start out speaking a few words very fast then it
>> would freez and not speak at all.
> Speaking fast in gnome-speech might be due to the fact that gnome-speech
> seems to be able to reach much higher speeds than speech-dispatcher does
> (on my system I need to set speech-dispatcher to full (99) in orca to
> achieve what seems nearly fast enough where as whith gnome-speech I am
> dropping it down to about 60 (although I may speech it up once I have
> tuned it a bit better for pitch and such like)).
>> I kind of wonder if it was because I have my USB sound card set to output
>> 44,100HZ in /etc/asound.comf and viavoice would be using 22,000HZ.
> What was the rate of speech when using gnome-speech's test application
> (test-speech)? If this seemed the fairly standard slow default speed
> applications normally set then sample rate conversion is probably
> occurring. It's quite common for alsa to resample for you, any device
> you set up as plug or to use dmix will automatically resample for you.
>> When ever I get a faster computer I'll probbely try running gnome-speech
>> again but at the momentgnome speech is not very responcive on my computer
>> and speech-dispatcher is quite a bit more responcive.
>> I kind of wonder what is causing it to spell some words but not others
>> though... Very strange.
>>From what I can tell, the following causes speech-dispatcher (when using
> orca, when using speechd-up I think I got slightly different results):
> If the word contains non-alphabetic characters (eg.
> speakup-request@braille.uwo.ca gets some parts spelt)
> If something has capitals in the midst of it (eg. java variable names or
> method names, although the method names will have non-alphabetic
> characters after it))
>
> Those above rules probably could be improved upon to be more specific
> but it's a starting point. Some words get spelt by gnome-speech, but
> this is less frequent and I am still working when this occurs. I don't
> remember espeak doing this so much so I don't think it's in the main
> speech-dispatcher code just the ibmtts module or ibmtts itself.
>
> Michael Whapples
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 3156 (20080603) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
> 

Re: IBMTTS on slackware

[Tomas Cerha]

Nick Stockton wrote:
> Funny that you should menchen that because I've noticed
> speech-dispatcher spelling stuff sometimes.

Yes, that's because the Speech Dispatcher's IBMTTS output module doesn't
turn of the IBMTTS internal dictionary, while Gnome Speech does.  There
was a recent discussion on that on Speech Dispatcher list and we hope to
have this optional for the next release.

Best regards, Tomas

Re: IBMTTS on slackware

[Nick Stockton]

*smile* Very cool!
Thanks for letting me know.
*starts to wate excitedly for the next releace, when ever that is*
----- Original Message ----- 
From: "Tomas Cerha" <cerha@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, June 09, 2008 2:20 AM
Subject: Re: IBMTTS on slackware


> Nick Stockton wrote:
>> Funny that you should menchen that because I've noticed
>> speech-dispatcher spelling stuff sometimes.
>
> Yes, that's because the Speech Dispatcher's IBMTTS output module doesn't
> turn of the IBMTTS internal dictionary, while Gnome Speech does.  There
> was a recent discussion on that on Speech Dispatcher list and we hope to
> have this optional for the next release.
>
> Best regards, Tomas
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 3156 (20080603) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
> 

Re: IBMTTS on slackware

[Janina Sajka]

Also responding to an older post ...

Nick Stockton writes:
>  ... I couldnt get the IBMTTS gnome-speech 
> server to use alsa.

Actually, it can't use also. But, it can use alsa's oss emmulation,
aoss.

Re: IBMTTS on slackware

[Frank Carmickle]

Just to clarify.  If you use the speakup connector then it is using alsa directly.  

--FC


On Mon, Jun 09, Janina Sajka wrote:
> Also responding to an older post ...
> 
> Nick Stockton writes:
> >  ... I couldnt get the IBMTTS gnome-speech 
> > server to use alsa.
> 
> Actually, it can't use also. But, it can use alsa's oss emmulation,
> aoss.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>