[Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

James Teh
Hi all,

Given the huge amount of discussion on this topic, I've just posted an
article which explains the situation regarding NVDA and ETI-Eloquence:
http://www.nvda-project.org/blog/NVDAAndEloquenceSituation
Please read this article in full if you're interested in Eloquence and
NVDA. Please also pass this link on to anyone else who may be interested.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Allan
hi James,
if NV Access can get the license for the ETI Eloquence, i willing to pay even if it is 30AUD/copy for my personal use.
 
 
---
 
Allan
 
“THINK BEFORE YOU PRESS PRINT BUTTON”
Do you really need to print this e-mail?
----- Original Message -----
Sent: Thursday, June 17, 2010 10:31
Subject: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Hi all,

Given the huge amount of discussion on this topic, I've just posted an
article which explains the situation regarding NVDA and ETI-Eloquence:
http://www.nvda-project.org/blog/NVDAAndEloquenceSituation
Please read this article in full if you're interested in Eloquence and
NVDA. Please also pass this link on to anyone else who may be interested.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/

_______________________________________________
Nvda-dev mailing list
[hidden email]
http://lists.nvaccess.org/listinfo/nvda-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Devin Prater
Who really needs eloquence when we have the abandonware viavoice 4.0!
http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip





On 6/16/2010 9:48 PM, Allan wrote:
hi James,
if NV Access can get the license for the ETI Eloquence, i willing to pay even if it is 30AUD/copy for my personal use.
 
 
---
 
Allan
 
“THINK BEFORE YOU PRESS PRINT BUTTON”
Do you really need to print this e-mail?
----- Original Message -----
Sent: Thursday, June 17, 2010 10:31
Subject: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Hi all,

Given the huge amount of discussion on this topic, I've just posted an
article which explains the situation regarding NVDA and ETI-Eloquence:
http://www.nvda-project.org/blog/NVDAAndEloquenceSituation
Please read this article in full if you're interested in Eloquence and
NVDA. Please also pass this link on to anyone else who may be interested.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/

_______________________________________________
Nvda-dev mailing list
[hidden email]
http://lists.nvaccess.org/listinfo/nvda-dev
_______________________________________________ Nvda-dev mailing list [hidden email] http://lists.nvaccess.org/listinfo/nvda-dev

Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

James Teh
On 17/06/2010 1:31 PM, Devin Prater wrote:
> Who really needs eloquence when we have the abandonware viavoice 4.0!
> http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip
Did you not read the post at all? It is not abandonware. Just because it
is an older version does not make it abandonware.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Soronel Haetir
Addressing the registry issues specifically, it _is_ possible to load
registry hives at run-time, also the registry allows for symbolic
links (discouraged but present).  Or volatile keys which simply aren't
saved.

I've always found the registry a pain to deal with but it does offer
plenty of flexibility.


On 6/16/10, James Teh <[hidden email]> wrote:

> On 17/06/2010 1:31 PM, Devin Prater wrote:
>> Who really needs eloquence when we have the abandonware viavoice 4.0!
>> http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip
> Did you not read the post at all? It is not abandonware. Just because it
> is an older version does not make it abandonware.
>
> Jamie
>
> --
> James Teh
> Vice President
> NV Access Inc, ABN 61773362390
> Email: [hidden email]
> Web site: http://www.nvaccess.org/
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>


--
Soronel Haetir
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Brian Gaff Lineone downstairs
In reply to this post by Devin Prater
Is that legal either though, what is abandonware. Surely even if abandoned,
someone still has the copyright, unless expressly waived.

 Brian
Brian Gaff  [hidden email]- If you need to email me please send it
to
[hidden email]
Making sure the name 'Brian Gaff' is in the display name field.
Failure to do this may result in delays or message loss.

Some sacrifices are a fact of life in our junk mail  riddled world!
----- Original Message -----
From: "Devin Prater" <[hidden email]>
To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
source screen reader for Microsoft Windows" <[hidden email]>
Sent: Thursday, June 17, 2010 4:31 AM
Subject: Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained


> Who really needs eloquence when we have the abandonware viavoice 4.0!
> http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip
>
>
>
>
>
> On 6/16/2010 9:48 PM, Allan wrote:
>> hi James,
>> if NV Access can get the license for the ETI Eloquence, i willing to
>> pay even if it is 30AUD/copy for my personal use.
>> ---
>> Allan
>> "THINK BEFORE YOU PRESS PRINT BUTTON"
>> Do you really need to print this e-mail?
>> ----- Original Message -----
>> *From:* James Teh <mailto:[hidden email]>
>> *To:* NVDA support mailing list
>> <mailto:[hidden email]> ; NVDA development mailing
>> list <mailto:[hidden email]>
>> *Sent:* Thursday, June 17, 2010 10:31
>> *Subject:* [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained
>>
>> Hi all,
>>
>> Given the huge amount of discussion on this topic, I've just posted an
>> article which explains the situation regarding NVDA and ETI-Eloquence:
>> http://www.nvda-project.org/blog/NVDAAndEloquenceSituation
>> Please read this article in full if you're interested in Eloquence and
>> NVDA. Please also pass this link on to anyone else who may be interested.
>>
>> Jamie
>>
>> --
>> James Teh
>> Vice President
>> NV Access Inc, ABN 61773362390
>> Email: [hidden email] <mailto:[hidden email]>
>> Web site: http://www.nvaccess.org/
>>
>> _______________________________________________
>> Nvda-dev mailing list
>> [hidden email] <mailto:[hidden email]>
>> http://lists.nvaccess.org/listinfo/nvda-dev
>>
>>
>> _______________________________________________
>> Nvda-dev mailing list
>> [hidden email]
>> http://lists.nvaccess.org/listinfo/nvda-dev
>>
>
>


--------------------------------------------------------------------------------


> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.829 / Virus Database: 271.1.1/2942 - Release Date: 06/16/10
19:35:00




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Allan
In reply to this post by Devin Prater
but sir, the question is, is this viavoice legal to use with NVDA? if it is not legal, we also can use eloquence as well.
 
 
---
 
Allan
 
“THINK BEFORE YOU PRESS PRINT BUTTON”
Do you really need to print this e-mail?
----- Original Message -----
Sent: Thursday, June 17, 2010 11:31
Subject: Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Who really needs eloquence when we have the abandonware viavoice 4.0!
http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip





On 6/16/2010 9:48 PM, Allan wrote:
hi James,
if NV Access can get the license for the ETI Eloquence, i willing to pay even if it is 30AUD/copy for my personal use.
 
 
---
 
Allan
 
“THINK BEFORE YOU PRESS PRINT BUTTON”
Do you really need to print this e-mail?
----- Original Message -----
Sent: Thursday, June 17, 2010 10:31
Subject: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Hi all,

Given the huge amount of discussion on this topic, I've just posted an
article which explains the situation regarding NVDA and ETI-Eloquence:
http://www.nvda-project.org/blog/NVDAAndEloquenceSituation
Please read this article in full if you're interested in Eloquence and
NVDA. Please also pass this link on to anyone else who may be interested.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/

_______________________________________________
Nvda-dev mailing list
[hidden email]
http://lists.nvaccess.org/listinfo/nvda-dev
_______________________________________________ Nvda-dev mailing list [hidden email] http://lists.nvaccess.org/listinfo/nvda-dev


_______________________________________________
Nvda-dev mailing list
[hidden email]
http://lists.nvaccess.org/listinfo/nvda-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Devin Prater
In reply to this post by Soronel Haetir
Oh, I'm realy sorry, I must have skipped something. but, if Josh Kenidy
or however you spell his name, sorry, could make a festival like version
of eloquence by making recordings of eloquence and making a festival
voice out of them some how, could that be considered legal?



On 6/17/2010 12:45 AM, Soronel Haetir wrote:

> Addressing the registry issues specifically, it _is_ possible to load
> registry hives at run-time, also the registry allows for symbolic
> links (discouraged but present).  Or volatile keys which simply aren't
> saved.
>
> I've always found the registry a pain to deal with but it does offer
> plenty of flexibility.
>
>
> On 6/16/10, James Teh<[hidden email]>  wrote:
>    
>> On 17/06/2010 1:31 PM, Devin Prater wrote:
>>      
>>> Who really needs eloquence when we have the abandonware viavoice 4.0!
>>> http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip
>>>        
>> Did you not read the post at all? It is not abandonware. Just because it
>> is an older version does not make it abandonware.
>>
>> Jamie
>>
>> --
>> James Teh
>> Vice President
>> NV Access Inc, ABN 61773362390
>> Email: [hidden email]
>> Web site: http://www.nvaccess.org/
>>
>> _______________________________________________
>> Nvda-dev mailing list
>> [hidden email]
>> http://lists.nvaccess.org/listinfo/nvda-dev
>>
>>      
>
>    



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Geoff Shang
On Thu, 17 Jun 2010, Devin Prater wrote:

> Oh, I'm realy sorry, I must have skipped something. but, if Josh Kenidy or
> however you spell his name, sorry, could make a festival like version of
> eloquence by making recordings of eloquence and making a festival voice out
> of them some how, could that be considered legal?

I doubt it.

Geoff.



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

James Teh
In reply to this post by Soronel Haetir
On 17/06/2010 3:45 PM, Soronel Haetir wrote:
> Addressing the registry issues specifically, it _is_ possible to load
> registry hives at run-time
> Or volatile keys which simply aren't
> saved.
I didn't know about volatile registry keys; thanks for the pointer.
However, the problem is that we need to write to HKEY_LOCAL_MACHINE,
which, unless I'm mistaken, always requires admin privileges.

Jamie

--
James Teh
Vice President
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Alex H.
I know this is a really far-fetched idea, but what if we just say,
'the heck with commercial Eloquence' and write a very understandable
eloq clone open-source it, and port it for all platforms? Seems a lot
easier than trying to work with Neuance on an inactive product, and it
would squash all this talk about liscencing, and NVDA could use it and
even have it bundled like espeak!

Reality tells me though that if anybody was going to clone eloq it
would take a very long time, lots of energy and several large pots of
coffee per day.

Alex

On 6/18/10, James Teh <[hidden email]> wrote:

> On 17/06/2010 3:45 PM, Soronel Haetir wrote:
>> Addressing the registry issues specifically, it _is_ possible to load
>> registry hives at run-time
>> Or volatile keys which simply aren't
>> saved.
> I didn't know about volatile registry keys; thanks for the pointer.
> However, the problem is that we need to write to HKEY_LOCAL_MACHINE,
> which, unless I'm mistaken, always requires admin privileges.
>
> Jamie
>
> --
> James Teh
> Vice President
> NV Access Inc, ABN 61773362390
> Email: [hidden email]
> Web site: http://www.nvaccess.org/
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

mk360
    Hmmmm, what about patents?
----- Original Message -----
From: "Alex H." <[hidden email]>
To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
source screen reader for Microsoft Windows" <[hidden email]>
Sent: Friday, June 18, 2010 4:51 PM
Subject: Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained


>I know this is a really far-fetched idea, but what if we just say,
> 'the heck with commercial Eloquence' and write a very understandable
> eloq clone open-source it, and port it for all platforms? Seems a lot
> easier than trying to work with Neuance on an inactive product, and it
> would squash all this talk about liscencing, and NVDA could use it and
> even have it bundled like espeak!
>
> Reality tells me though that if anybody was going to clone eloq it
> would take a very long time, lots of energy and several large pots of
> coffee per day.
>
> Alex
>
> On 6/18/10, James Teh <[hidden email]> wrote:
>> On 17/06/2010 3:45 PM, Soronel Haetir wrote:
>>> Addressing the registry issues specifically, it _is_ possible to load
>>> registry hives at run-time
>>> Or volatile keys which simply aren't
>>> saved.
>> I didn't know about volatile registry keys; thanks for the pointer.
>> However, the problem is that we need to write to HKEY_LOCAL_MACHINE,
>> which, unless I'm mistaken, always requires admin privileges.
>>
>> Jamie
>>
>> --
>> James Teh
>> Vice President
>> NV Access Inc, ABN 61773362390
>> Email: [hidden email]
>> Web site: http://www.nvaccess.org/
>>
>> _______________________________________________
>> Nvda-dev mailing list
>> [hidden email]
>> http://lists.nvaccess.org/listinfo/nvda-dev
>>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev 



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Geoff Shang
Hi,

Truly, the only existing open source speech synthesiser which sets out to
fulfil the functions of synths like Elloquence is Espeak.  Given its
maturity, surely it'd be better to work on modifying that instead of
starting from scratch.

Geoff.



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Alex H.
In reply to this post by mk360
There's plenty of similar products that do the same thing, utilize
almost the same technology, etc. Behringer makes knock-off guitar
equipment that almost sounds as good as the real thing, so I don't
think patents would be a big issue,. Even if the synth had slightly
different parameters, it could still sound very much the same before
Neuance could get all cranky.

alex

On 6/18/10, mk360 <[hidden email]> wrote:

>     Hmmmm, what about patents?
> ----- Original Message -----
> From: "Alex H." <[hidden email]>
> To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
> source screen reader for Microsoft Windows" <[hidden email]>
> Sent: Friday, June 18, 2010 4:51 PM
> Subject: Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained
>
>
>>I know this is a really far-fetched idea, but what if we just say,
>> 'the heck with commercial Eloquence' and write a very understandable
>> eloq clone open-source it, and port it for all platforms? Seems a lot
>> easier than trying to work with Neuance on an inactive product, and it
>> would squash all this talk about liscencing, and NVDA could use it and
>> even have it bundled like espeak!
>>
>> Reality tells me though that if anybody was going to clone eloq it
>> would take a very long time, lots of energy and several large pots of
>> coffee per day.
>>
>> Alex
>>
>> On 6/18/10, James Teh <[hidden email]> wrote:
>>> On 17/06/2010 3:45 PM, Soronel Haetir wrote:
>>>> Addressing the registry issues specifically, it _is_ possible to load
>>>> registry hives at run-time
>>>> Or volatile keys which simply aren't
>>>> saved.
>>> I didn't know about volatile registry keys; thanks for the pointer.
>>> However, the problem is that we need to write to HKEY_LOCAL_MACHINE,
>>> which, unless I'm mistaken, always requires admin privileges.
>>>
>>> Jamie
>>>
>>> --
>>> James Teh
>>> Vice President
>>> NV Access Inc, ABN 61773362390
>>> Email: [hidden email]
>>> Web site: http://www.nvaccess.org/
>>>
>>> _______________________________________________
>>> Nvda-dev mailing list
>>> [hidden email]
>>> http://lists.nvaccess.org/listinfo/nvda-dev
>>>
>>
>> _______________________________________________
>> Nvda-dev mailing list
>> [hidden email]
>> http://lists.nvaccess.org/listinfo/nvda-dev
>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Bill Cox
In reply to this post by Alex H.

I believe this is not far fetched.  What is requiered is for visually impaired developers to work together as volunteers.  I believe there are more than enough of us to write everything we need.

I am working with some people from Vinux.  We are making a new foundation, with the goal of organizing programmers with disabilities around the world to help build the next generation of accessible software. I think projects like NVDA demonstrait what is possible.  Replacing Eloquence with something better is high on the list, but may take multuple years.  We will need volunteer willing to specialise.

Bill

On Jun 18, 2010 4:52 PM, "Alex H." <[hidden email]> wrote:

I know this is a really far-fetched idea, but what if we just say,
'the heck with commercial Eloquence' and write a very understandable
eloq clone open-source it, and port it for all platforms? Seems a lot
easier than trying to work with Neuance on an inactive product, and it
would squash all this talk about liscencing, and NVDA could use it and
even have it bundled like espeak!

Reality tells me though that if anybody was going to clone eloq it
would take a very long time, lots of energy and several large pots of
coffee per day.

Alex

On 6/18/10, James Teh <[hidden email]> wrote:
> On 17/06/2010 3:45 PM, Soronel Haetir wrote:
>> Addressing the registry issues specifically, it _is_ possible to load
>> registry hives at run-time
>> Or volatile keys which simply aren't
>> saved.
> I didn't know about volatile registry keys; thanks for the pointer.
> However, the problem is that we need to write to HKEY_LOCAL_MACHINE,
> which, unless I'm mistaken, always requires admin privileges.
>
> Jamie
>
> --
> James Teh
> Vice President
> NV Access Inc, ABN 61773362390
> Email: [hidden email]
> Web site: http://www.nvaccess.org/
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>

_______________________________________________
Nvda-dev mailing list
[hidden email]
http://lists.nvaccess.org/listinfo/nvda-dev

Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Halim Sahin
Hi,
It's always same with the eti eloquence.
Most people of the blind community want  eloquence and is not willing to
try other synths or want to improove existing ones.
The facts are:
cloning eloquence will take several years if you have speechsynthesis
experts working on it as their daily work.
The result could sound different than eloquence and many people will
complain if it isn't the same.

My suggestion is work together with Jonathan Duddington for improoving
espeak.
It is opensource and (is usable) if you want to use something different
than eloquence.
BTW.: it supports more languages than eloquence and doesn't need an old
listdc++ under linux :-).

I am now using espeak on my primary machine ssince nov 2009.
I used eloquence before :-).




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Bill Cox
Hi, Halim.

On Sat, Jun 19, 2010 at 2:13 AM, Halim Sahin <[hidden email]> wrote:
> Hi,
> It's always same with the eti eloquence.
> Most people of the blind community want  eloquence and is not willing to
> try other synths or want to improove existing ones.

Espeak is a good synth, and I personally like it.  However, espeak was
not tuned for high speed comprehensibility.  I have read that the
Eloquence devs are the only people who ever did proper studies on high
speed comprehension, so it's no surprise their synth is best for that.
 This is not just a matter of taste.  It's a clear highly measurable
difference.  Eloquence can literally be understood at about 2X the
best rate possible from espeak.

This is an issue that matters to the blind, and probably only the
blind.  That's why no one is bothering to build us a new TTS engine
that's usable at high speed.  It's important enough to justify forming
a team of volunteer developers to address the problem.

> The facts are:
> cloning eloquence will take several years if you have speechsynthesis
> experts working on it as their daily work.

We don't have to start from scratch.  The mbrola voices aren't bad at
low speed, using the espeak front-end.  We may only have to work on
the back end.  Espeak is only a 46K line program in C++.  Writing that
much code will not be difficult.  The problem isn't writing the code,
it's knowing what code to write.  There are multiple good TTS engines
that are no longer actively developed, because there isn't a market
for them.  The developers have naturally moved on, including some of
the Eloquence guys.  All we need is some good advisers who are experts
in this field, people who know what to write.  We can do the rest.

> The result could sound different than eloquence and many people will
> complain if it isn't the same.

People will always complain about voices!  If we have an alternative
that is just as productive, then we can just let them whine.  Espeak
is not there yet.

> My suggestion is work together with Jonathan Duddington for improoving
> espeak.
> It is opensource and (is usable) if you want to use something different
> than eloquence.
> BTW.: it supports more languages than eloquence and doesn't need an old
> listdc++ under linux :-).

Agreed.  Espeak has many excellent attributes.  If we could make it
comprehensible at high speed, it could replace the need for Eloquence.

This importance of such an effort is hard to over-state.  I can't ask
people to drop to half of their current productivity just because I
prefer that they avoid closed source software.  Eloquence is a key
enabling technology for many blind people, including a lot of the best
blind programmers who we need involved in FOSS accessible software
development.

Another key project will be writing a Naturally Speaking replacement
for those who can't type.  We don't need to match the latest and
greatest continuous speech recognition.  Naturally Speaking is
designed for writers who like to dictate rather than type, rather than
for people who can't type.  What's needed is a solid discreet
recognition engine that is context aware, and which can be used to
fairly rapidly control the desktop and applications, and to write
programs.  Productivity for the typing impaired has not significantly
improved since about 1996.  As soon as there was a mass commercial
market, Dragon Systems dropped the needs of the typing impaired like a
hot potato.

Bill


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Halim Sahin
Hi Bill,

On Sa, Jun 19, 2010 at 08:27:27 -0400, Bill Cox wrote:
> We don't have to start from scratch.  The mbrola voices aren't bad at
> low speed,

You know that mbrola is closed source?
Afaik it's not allowed to distribute the voices.
So you can't ship these with your favourite distribution!
BR.
Halim



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

Brian Gaff Lineone downstairs
In reply to this post by Devin Prater
In blindcooltech, I notice a review of a way to make yourself into a voice,
so I assume it depeends on getting the voice, yours or some other thing to
say the things neeed.
 I must say though I was not convinced by the demo that it was going to be
of much use other than to annoy your friends.

 Brian
----- Original Message -----
From: "Devin Prater" <[hidden email]>
To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
source screen reader for Microsoft Windows" <[hidden email]>
Sent: Thursday, June 17, 2010 6:29 PM
Subject: Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained


> Oh, I'm realy sorry, I must have skipped something. but, if Josh Kenidy or
> however you spell his name, sorry, could make a festival like version of
> eloquence by making recordings of eloquence and making a festival voice
> out of them some how, could that be considered legal?
>
>
>
> On 6/17/2010 12:45 AM, Soronel Haetir wrote:
>> Addressing the registry issues specifically, it _is_ possible to load
>> registry hives at run-time, also the registry allows for symbolic
>> links (discouraged but present).  Or volatile keys which simply aren't
>> saved.
>>
>> I've always found the registry a pain to deal with but it does offer
>> plenty of flexibility.
>>
>>
>> On 6/16/10, James Teh<[hidden email]>  wrote:
>>
>>> On 17/06/2010 1:31 PM, Devin Prater wrote:
>>>
>>>> Who really needs eloquence when we have the abandonware viavoice 4.0!
>>>> http://dl.dropbox.com/u/1942830/ViaVoice%20OutLoud.zip
>>>>
>>> Did you not read the post at all? It is not abandonware. Just because it
>>> is an older version does not make it abandonware.
>>>
>>> Jamie
>>>
>>> --
>>> James Teh
>>> Vice President
>>> NV Access Inc, ABN 61773362390
>>> Email: [hidden email]
>>> Web site: http://www.nvaccess.org/
>>>
>>> _______________________________________________
>>> Nvda-dev mailing list
>>> [hidden email]
>>> http://lists.nvaccess.org/listinfo/nvda-dev
>>>
>>>
>>
>>
>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] NVDA and ETI-Eloquence: The Situation Explained

David Picón Álvarez
In reply to this post by Bill Cox
From: "Bill Cox" <[hidden email]>

> We don't have to start from scratch.  The mbrola voices aren't bad at
> low speed, using the espeak front-end.  We may only have to work on
> the back end.  Espeak is only a 46K line program in C++.  Writing that
> much code will not be difficult.  The problem isn't writing the code,
> it's knowing what code to write.  There are multiple good TTS engines


My understanding is that mbrola voices have licencing issues. If people are
going to bother doing all the effort required to get a decent free (as in
speech) synth, it may as well be actually free.

Also I think it is a very difficult problem, it would probably take more
research than most software projects do. Speaking of which, I wonder if the
voxforge dataset could be useful in this regard.

Regards,
--David.



12