RE: [Mobile Speak Pocket] New podcast uploaded tonight.

"Rick Alfaro" <rick.alfaro@xxxxxxxxxxx> · Sat, 26 May 2007 16:36:18 -0400

Vic,

Try the Fonix DecTalk tts instead.  Believe me, much more responsive and way
smaller foot print.  Also way easier to understand but of course that is
subjective.

--Warmest regards,

--Rick Alfaro
--rick.alfaro@xxxxxxxxxxx

-----Original Message-----
From: msp_mailing-bounces@xxxxxxxxxxxxxx
[mailto:msp_mailing-bounces@xxxxxxxxxxxxxx] On Behalf Of Victor Tsaran
Sent: Saturday, May 26, 2007 2:32 AM
To: Deanne Fernandez; 'Shane Jackson'; msp_mailing@xxxxxxxxxxxxxx; Geoff
Stephens
Cc: blindcasting@xxxxxxxxxxxxx
Subject: Re: [Mobile Speak Pocket] New podcast uploaded tonight.

Funny that you say that... I am just trying a 30-day license of
Mobilespeak on my Nokia N95, since it's the only player in town,
and find that all those Akoppelas do not compare to Eloquence.
First of all, they are slower, in my opinion, and second, they
exagerate speech to much, thus making it difficult to operate
the phone.
I wonder why Code Factory decided to abandon Eloquence TTS.
Regards,
Vic

--- Deanne Fernandez <dcm2005@xxxxxxxxxxxxx> wrote:

> I agree that Eloquence is much easier to understand than the
> voices offered for MSP or MSS.  I am currently using Loquendo
> Dave for US English.  I'm still trying to learn how to put
> more than one voice on my phone without paying for more than
> one license.  I, too, can't understand certain words, even
> after reviewing them several times.  I haven't yet figured out
> how to spell words on my motorola Q.  I wouldn't mind a
> slightly slow response time with Eloquence if I could
> understand the speech better.  Sometimes, even when I know
> what Loquendo Dave is saying, the word still doesn't sound
> llike an actual word.
> Deanne
>   ----- Original Message ----- 
>   From: Geoff Stephens 
>   To: 'Shane Jackson' ; msp_mailing@xxxxxxxxxxxxxx 
>   Cc: blindcasting@xxxxxxxxxxxxx 
>   Sent: Friday, May 25, 2007 7:18 PM
>   Subject: Re: [Mobile Speak Pocket] New podcast uploaded
> tonight.
> 
> 
>   I have been showing my 8525 to various blind people since
> I'm a new MSP user and am anxious to let people know how
> usable and intuitive Code Factory has made these devices. 
> Veteran synthesized speech users as well as newbies agree that
> the speech makes MSP a less than appealing solution.  In fact,
> many seem to become completely disinterested in all the rest
> of the demonstration after they hear the Fonix speech.  It
> seems that everybody wants Eloquence.  I truly believe Code
> Factory could sell significantly more copies of MSP if
> Eloquence was available.
> 
>   I have tried to condition myself to Fonix but I have to
> admit that it is still difficult for me after a month and a
> half of use.  I'm not very productive with it.  I will live
> with it because I have to do so.  I generally use arate of 19.
>  I frequently have to go back and review words I did not
> understand.  I use eloquence at a much faster rate (75 percent
> of maximum with JAWS for example) and do not have any problem
> reading at that rate.
> 
>   I have seen arguments on this list about the responsiveness
> of Fonix.  I support those who contend that it is not very
> responsive.  It is difficult to provide support for that
> argument since there are many factors to consider including
> the device and the screen reader.  How are we to know how
> responsive Eloquence would be with MSP if we haven't used it? 
> I don't know how to qualify it except to say I suspect it
> would be bettter.
> 
>   I didn't listen to the entire podcast but skimmed through it
> and wanted to let you know that the keys above the QWERTY
> keyboard are the left and right soft keys in case you want to
> use them in the future.  I was forced to do  so a couple of
> weeks ago when the front keyboard on my 8525 stopped working. 
> I have since received a replacement and it is working fine.  I
> have continued the habit of using the soft keys on the QWERTY
> keyboard when it is open.  For a long time I did not realize
> that those keys were actually keys.  I thought they were part
> of the communication that must occur to let the device know
> when the keyboard is opened and closed.  They are a little
> awkward to press at first but they work very well.
> 
> 
>
----------------------------------------------------------------------------
--
> 
> 
>   [Note: If you wish to post your reply to the list, use the
> "Reply All", rather than the "Reply", option of your email
> client.]
>   _______________________________________________
>   msp_mailing list
>   msp_mailing@xxxxxxxxxxxxxx
>  
>
http://list.codefactory.es/mailman/listinfo/codefactory.es.msp_mailing
> > [Note: If you wish to post your reply to the list, use the
> "Reply All", rather than the "Reply", option of your email
> client.]
> _______________________________________________
> msp_mailing list
> msp_mailing@xxxxxxxxxxxxxx
>
http://list.codefactory.es/mailman/listinfo/codefactory.es.msp_mailing
> 

[Note: If you wish to post your reply to the list, use the "Reply All",
rather than the "Reply", option of your email client.]
_______________________________________________
msp_mailing list
msp_mailing@xxxxxxxxxxxxxx
http://list.codefactory.es/mailman/listinfo/codefactory.es.msp_mailing

Other related posts: