> Maybe we look at getting sound working first?----Yes, of course. eg. `aplay sample.wav'I was concentrating on the complexity of TC's download & install OR install at boot..?Also, I: lame $1.wav $1.mp3; and listen to [TextToSpeech] on a different device.TC64 is good to fetch the text [by links URL] and `wily` to <clean> it.For TextToSpeech I've been using `festival`, but not via TC.TC's espeak-ng doesn't sound any better than 10 years ago; and althoughthe <data files> for the MBROLA improvement were d/l-ed, I get:"The specified espeak-ng voice does not exist." Since the "specified espeak-ng voice" to see if MBROLA is any betterthan plain-espeak, has a name, and possibly a non-default Path-to-the-file,I'm wondering if TC's having the files <sym-linked to loop-devices> is a problem. Can we assume that espeak-ng was only added to our repetoire AFTER it wasconfirmed as running on TC ?.... OK, I've noted the script to control the SoundPlayer, after the driver has been downloaded. But my priority is toget the claimed speech improvement from MBROLA. Thanks.

>] Can we assume that espeak-ng was only added to>] our repetoire AFTER it was>] confirmed as running on TC ?

> affirmative

I should have asked if the included mbrola refinementshave been confirmed ?My understanding is that although mbrola's <translator>is not included: its data [which gives better results] is.-> ls /usr/local/share/espeak-ng-data/mbrola_ph ==af1_phtrans ee1_phtrans hn1_phtrans it3_phtrans ... Trying to use mbrola, I use 2 args [after many tries]:-v <voice name> Use voice file of this name from espeak-ng-data/voices--path="<path>" Specifies the directory containing the espeak-ng-data directorybut always get <-v arg not found>.I was hoping that improved quality via mbrola-data, would allowme to avoid needing to: `chroot <slakware partition to run> festival`Thanks.

Sorry I've been away for a while.Am I seriously "outdated" ? -> uname -a ==Linux box 4.2.9-tinycore64 #1999 SMP Mon Jan 18 19:59:34 UTC 2016 x86_64 GNU/LinuxSummarising this thread so far: I use Festival TTS everyday, but from a mobile, while lying down, and notfrom a computer, hence no need for <install/test alsa...etc.>Probably espeak was originaly intended for operating at the computer.Of course TTS quality is very subjective, and comprehension changes whilelearning. Because I want to keep TC minimalist, I don't want to getinvolved in <building & gcc>. So under TC, I must <chroot non-TC Festival>.RPi having the advantage that it's not <forked>: has a binary/pre-compilednewer, version which seemed a bit better than my x86 ver2.1.

> .... see what you make of this> http://blog.michaelamerz.com/wordpress/> the-state-of-the-art-linux-text-to-speech-tts/> ...the blogger has elected to "we settled for Pico2Wave - with> a few updates"

OK, the 3 *.mp3 heard are inferior to my Festival 2.1, but usable.

The best quality that I've got is [here's an example of what theseMicro$pook users can't appreciate the need to be able to do - I'llnow look into my M$ partition to get the info; and do it from INSIDE,wily where I'm NOW composing this]: mount /dev/sda4 ; find /mnt/sda4/Users/Public/CRG -name TTS=> /mnt/sda4/Users/Public/CRG/Speech finds:---------"Description

This program uses SAPI voices for Text to speech from the commandline. its a simple tool written in C# Samples included for English and Japanese, but you will need a Japanese voice installed on your PC

[34]cmdSayIt Web Site"---------------This is an example of the power/use of `wily`: the ability tobranch-off and search [or even build/compile] other partitionsto get data for the text being composed, all seen on the SAME SCREEN.================> 3) What input file format must TTS be able to handle?

This is vitally important for proper text [not just short phrases]!Many, including the <Japanese-one> pause at each end-of-line, whichis intolerable. So I needed to delete all EOL, also some M$ specialchars [perhaps:$, %] which terminated the text, need to be removed,by a <text cleaning program>.

If you have first run /bin/sed using "sed" and then load the sed extension, "sed" will still run /bin/sed - due to hashing?

Yes, you are correct. I had forgotten about hashing and some of the subtle symptoms it can produce.

If you run sed, then install sed.tcz, then run sed again in the same terminal, the first version of sed will be run again. To getthe newly installed version to run, either execute hash -r , or open a new terminal to run it. Here is a thread from 6 years agothat covered this:http://forum.tinycorelinux.net/index.php/topic,13162.0.html

Summary. I: Started by asking if espeak-ng had been installed on TC. Since espeak is small compared to the monster-Festival that I use. Pointed that the text input to the TTS must be <clean> so that "can't" doesn't sound like "sea aye en tea", and related: Discovered that TC's sed [used to clean the text] is problematic. My 32bit compiled/build of Flite [the more compact version of Festival] only speaks the last <utterances>, was reported by a GoogSearch as: "we've fixed that problem now". Thanks for wasting my time !!I was going to ask about installing TC64's gcc to be able to compile/build the latest 64bit flite, but if [mere] sed is a problem: a big compile-build is unrealistic.If I want TC64 to be small [without even Xorg] I must forget TTS ?