<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16821"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=392433320-28062011><FONT color=#0000ff
size=2 face=Arial>Thank you Ed. Your clarifications and perspective are
invaluable. I had no idea all Dectalk code has the ability to sing and always
will. Wow!</FONT></SPAN></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT> </DIV>
<DIV><SPAN class=392433320-28062011></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT size=2>I<SPAN class=392433320-28062011> also want to express
an oppinion regarding SAPI Dectalk. Since all Dectalk code can sing, I would
rather buy a SAPI Dectalk that can sing rather than a SAPI bundled
with a special Speak window. This way, the customer gets everything in one
package.</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=392433320-28062011></SPAN><SPAN
class=392433320-28062011></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>B<SPAN
class=392433320-28062011>lake</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> dectalk-bounces@bluegrasspals.com
[mailto:dectalk-bounces@bluegrasspals.com] <B>On Behalf Of </B>ebruckert
Bruckert<BR><B>Sent:</B> Tuesday, June 28, 2011 3:51 PM<BR><B>To:</B> DECtalk
Discussions<BR><B>Subject:</B> Re: [DECtalk] TEST<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>For clarity, no singing code has ever been or will be removed from DECtalk,
because I'm the only one that knows how to do it and I wouldn't. So any version
released will work with both sat and by definition dapi</DIV>
<DIV>sso speak will work, say will work etc. </DIV>
<DIV> my hypothesis is that if you install
sapi from Corine then overtime, we can supply different versions of DECtalk and
you can take your pick. <BR><BR></DIV>
<DIV class=gmail_quote>On Tue, Jun 28, 2011 at 3:42 PM, Jayson Smith <SPAN
dir=ltr><<A
href="mailto:ratguy@insightbb.com">ratguy@insightbb.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Hi,<BR><BR>Ed, I started this message nearly an hour ago but
then got called away.<BR>Therefore, I haven't read anything others might have
said since.<BR><BR>Please stay, we need you. I hate to put it like that, but
it seems that in<BR>all this, you have the historical perspective, and also
the experience of<BR>creating DECtalk versions after Dennis passed
away.<BR><BR>Here's an idea I just came up with. This would hopefully satisfy
all sides<BR>involved. Release the SAPI, without the singing and other
advanced<BR>capabilities if that is for some reason needed. But also offer to
more<BR>advanced users a Speak window which uses the newly developed software,
but<BR>with all features enabled. Obviously I have no idea if Enable is
removing<BR>code from the actual DECtalk DLL or rendering it inoperative in
order to<BR>disable the advanced functions, or keeping the DECtalk DLL intact
and fixing<BR>the SAPI so there's no way the end user can access those
functions. If the<BR>DECtalk DLL is a full, uncrippled DECtalk, my thought
would be to create a<BR>new Speak window, using modern programming techniques
in order to insure<BR>accessibility as well as compatibility for years to
come. The thing is, the<BR>new Speak window wouldn't be any good on its own.
It would need the DECtalk<BR>DLL. So where do you get that? Of course! By
buying the SAPI.<BR>Just my thoughts.<BR><FONT color=#888888>Jayson<BR></FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR>----- Original Message -----<BR>From: "ebruckert Bruckert"
<<A href="mailto:edbruckert@gmail.com">edbruckert@gmail.com</A>><BR>To:
"DECtalk Discussions" <<A
href="mailto:dectalk@bluegrasspals.com">dectalk@bluegrasspals.com</A>><BR>Sent:
Tuesday, June 28, 2011 2:37 PM<BR>Subject: Re: [DECtalk] TEST<BR><BR><BR>OK
guys enough. I am a little tired of the misinformation and confusion
and<BR>blaming going on. What careens money has done really is get this
SAPI<BR>portion working. I'm trying to get some old DLLs working. I do not get
any<BR>monetary compensation so I can't have any evil intent as you purport
to<BR>other people. You mentioned putting it old klatttalk setttings, which by
the<BR>way there aren't any. The synthesizer Digital Equipment Corporation
received<BR>from Dennis was incomplete. It had only the pH files for handling
phonemic<BR>input and the vocal tract model, it did not even have letter to
sound rules<BR>which were functional. As a point of interest historically 4.3
was one of<BR>the favorite versions and it was done by me as Dennis was dead.
Singing –<BR>the code for singing is the same as it was when Dennis finished
it with one<BR>exception. The original version used a physics music scale
which turns out<BR>to be slightly different than the musicians music scale.
Other than that the<BR>singing code has never changed, except for enhanced
version of singing which<BR>was done on a special Hebrew cantering product.
There is a danger clearly<BR>expressed in the manual that if you muck around
with parameters especially<BR>gain parameters things can get strange and these
are version specific<BR>because to achieve maximum quality a long program was
run to calculate each<BR>filter gain in the vocal track for every single
voice. The incompatibility<BR>results from a mathematical issue not anything
else. Due to platform<BR>restrictions we weren't able to go to a floating
point calculation which<BR>would've solved all these problems.<BR>I am slow
because I'm almost blind myself but I said a long time ago that it<BR>was my
goal to make sure you hit a DECtalk it was reasonable not identical.<BR>I say
this because I sat there with 4.3 code in front of me comparing it to<BR>the
code I was working on including pitch tracks and other measurements
and<BR>just plain looking at the code and although they were very very close
people<BR>preferred what they've gotten used to. Many of the changes that
occurred<BR>were a result of Microsoft constantly changing things it was
impossible for<BR>many different reasons for the original code to be compiled
and there are<BR>also reasons why it was very difficult to determine what the
code actually<BR>did and what it was supposed to do. There were many instances
where the code<BR>obviously didn't do what Dennis's comments said it was
supposed to do other<BR>things were even legal C constructs in that you could
not tell how the<BR>compiler would handle the ambiguous statements.<BR>
I've been laying back waiting for some of the smoke and
dust to<BR>settle Now my real question is should I get to work or should I go
away. The<BR>detailed issues are more complicated than either of Corine her
any of you<BR>really know. I had programmers leave because they found
the complexity of<BR>the whole darn thing to intimidating.<BR>As a tiny
example, if a data entry error is made in the locus data, that can<BR>create a
significant problem causing the synthesizer to squeal forever and<BR>yet be
incredibly difficult to find.<BR> His forests beat goes
it's really just a program to shovel stuff to<BR>DECtalk so it can be posted
anywhere it was an example of how to talk to<BR>DECtalk. Like everything else
the value is not in speak but is in the<BR>knowledge of how to program it for
singing. And it's only useful if you<BR>happen to have a DECtalk already is
the DECtalk DLL cannot be distributed<BR>freely and speak doesn't talk sappy
it only talks to eight DECtalk. It uses<BR>the DECtalk application interface,
sapi is simply a mapping of a universally<BR>defined set of commands for
Windows into device specific commands. So if<BR>people want I can send out
some samples of something I've worked on<BR>following normal procedures we
only work on one voice until we were ready to<BR>release because of the tuning
issues.<BR><BR>On Tue, Jun 28, 2011 at 1:33 PM, <<A
href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>> wrote:<BR><BR>>
**<BR>> *Ok, and I just got an email from Corine who still doesn't get it.
She's<BR>> saying that if anyone wants to sing using Dectalk, she's
sending everyone<BR>> to<BR>> me for a free speak window.*<BR>>
**<BR>> *Uh, there's already an updated version of Windows 7 that the speak
window<BR>> won't run on. What happens when a future Windows doesn't
include virtual<BR>> XP? What if everything switches to a droid
platform? I already can't get<BR>> speak running on certain
computers.*<BR>> **<BR>> *Who do I call when I can't get the speak
window working for people? This<BR>> is not fare to me.*<BR>>
**<BR>> **<BR>> *SNOOPI BOTTEN *<BR>> **<BR>> In a
message dated 6/28/2011 1:18:52 P.M. Eastern Daylight Time,<BR>> <A
href="mailto:ratguy@insightbb.com">ratguy@insightbb.com</A>
writes:<BR>><BR>> Hi,<BR>><BR>> I actually wasn't responding to
that last message, but that's the one I<BR>> hit<BR>><BR>> reply to.
I was actually responding to your thought yesterday that you<BR>>
might<BR>> have been removed from the list for your earlier comments.
That's not<BR>> going<BR>><BR>> to happen.<BR>>
Jayson<BR>><BR>> ----- Original Message -----<BR>> From: <<A
href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>><BR>> To: <<A
href="mailto:dectalk@bluegrasspals.com">dectalk@bluegrasspals.com</A>><BR>>
Sent: Tuesday, June 28, 2011 12:58 PM<BR>> Subject: Re: [DECtalk]
TEST<BR>><BR>><BR>> > You miss understood me. I'm not
concerned about being removed from the<BR>> > list. Corine
in no way wants anyone to see the prototype. So I was<BR>> >
saying,<BR>> > the link to the prototype will only work until
Corine tells Dave to<BR>> > take<BR>><BR>> > it<BR>>
> down. Or, the site my crash.<BR>> ><BR>>
><BR>> > SNOOPI BOTTEN<BR>> ><BR>> ><BR>> > In a
message dated 6/28/2011 11:10:06 A.M. Eastern Daylight Time,<BR>> > <A
href="mailto:ratguy@insightbb.com">ratguy@insightbb.com</A> writes:<BR>>
><BR>> > Hi,<BR>> ><BR>> > Let me just repeat something
after all this discussion. Snoopi, you are<BR>> > not<BR>> >
being removed from this list. I am the only person on Earth with
the<BR>> > authority to remove people from this list or do any
other<BR>> > administrative<BR>> > job. And as far as I'm
concerned, this whole discussion is valuable.<BR>> >
Nobody<BR>> > will be removed from this list for anything they said or
may say on<BR>> > this<BR>> > topic.<BR>> ><BR>>
> I want to state something else too. As I see it, there are
several<BR>> > schools<BR>> > of DECtalk users and fans. There are
some who like the DECtalk speech<BR>> and<BR>> > probably would
use it with their screen reader if they could, or maybe<BR>> >
use<BR>> > it along with a text to MP3 program such as Text Aloud,
but don't have<BR>> > any<BR>> > other more elaborate use for it.
Then there are those who think it's<BR>> cool<BR>> > that
DECtalk can sing and do all this neat stuff and enjoy listening
to<BR>> > others' creations, but don't have a clue how to actually
make DECtalk<BR>> > do<BR>> > any<BR>> > of those things.
Then there are probably several classes of more<BR>> advanced<BR>>
> DECtalk users who, at the high end, could probably transcribe
arbitrary<BR>> > text<BR>> > into phonemes in their sleep.
These are the people making the elaborate<BR>> > DECtalk songs and
skits. And finally, there are the users with<BR>> >
disabilities<BR>> > requiring them to use DECtalk to speak and/or
sing. These users almost<BR>> > certainly fit into all the
previous classes of users I've discussed. I<BR>> > fit<BR>> >
somewhere in the third class of users, the more advanced
DECtalkists.<BR>> > So<BR>> > as<BR>> > you can see, this
SAPI is obviously targeted toward the more basic<BR>> >
user,<BR>> > who<BR>> > just wants to use it with their
screen reader or other SAPI-enabled<BR>> > applications, nothing
more.<BR>> ><BR>> > Regarding the Speak windows, yes it's true
that new hardware and new<BR>> > operating systems might come
along under which the Speak windows won't<BR>> > run.<BR>> >
However, all is not truly lost even then. As long as, say, a
virtual<BR>> > machine<BR>> > running XP can run under whatever
native hardware/OS is being used,<BR>> Speak<BR>> > can then be
run under that. Not the most ideal solution I do admit, but<BR>> >
still, it's better than nothing.<BR>> ><BR>> > I personally
would like to see the SAPI provide all DECtalk's features,<BR>> >
but<BR>> > it's clear to me that, for whatever reason, that's not going
to happen.<BR>> > Jayson<BR>> ><BR>> > ----- Original
Message -----<BR>> > From: <<A
href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>><BR>> > To: <<A
href="mailto:dectalk@bluegrasspals.com">dectalk@bluegrasspals.com</A>><BR>>
> Sent: Tuesday, June 28, 2011 9:21 AM<BR>> > Subject: Re:
[DECtalk] TEST<BR>> ><BR>> ><BR>> >> _<A
href="http://davesvideoservicesco.startlogic.com/test2/_"
target=_blank>http://davesvideoservicesco.startlogic.com/test2/_</A><BR>>
>> (<A href="http://davesvideoservicesco.startlogic.com/test2/"
target=_blank>http://davesvideoservicesco.startlogic.com/test2/</A>)<BR>>
>><BR>> >> Ok, we have an unstable prototype that keeps
crashing. I'm forcing<BR>> > Dave<BR>> >> to keep
it up until Corine tells him to remove it. It talks, but
I<BR>> >> haven't<BR>> >> been able to get it to say
anything this morning.<BR>> >><BR>> >> Basically
the plan is to reset it to Klattalk settings but call it<BR>>
>> Dectalk<BR>> >> Classic. And, it won't sing.<BR>>
>><BR>> >><BR>> >> SNOOPI BOTTEN<BR>>
>><BR>> >><BR>> >> In a message dated 6/28/2011
8:42:05 A.M. Eastern Daylight Time,<BR>> >> <A
href="mailto:bmisch2002@gmail.com">bmisch2002@gmail.com</A> writes:<BR>>
>><BR>> >> so how is that version coming along and
are the other languages going<BR>> > to<BR>> >> be included
or just us english?<BR>> >><BR>> >><BR>> >>
On Jun 27, 2011, at 6:33 PM, FRIDO ORDEMANN wrote:<BR>>
>><BR>> >><BR>> >><BR>> >><BR>> >>
There are other users of DECtalk than those who use it for
singing.<BR>> >><BR>> >><BR>> >>
____________________________________<BR>> >> From:
"_Dectalk@aol.com_ (mailto:<A
href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>) "
<_Dectalk@aol.com_<BR>> >> (mailto:<A
href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>) ><BR>> >> To:
_dectalk@bluegrasspals.com_ (mailto:<A
href="mailto:dectalk@bluegrasspals.com">dectalk@bluegrasspals.com</A>)<BR>>
>> Sent: Mon, June 27, 2011 2:10:43 PM<BR>> >>
Subject: Re: [DECtalk] TEST<BR>> >><BR>> >>
Actually I was scared I was removed for exploding on the list
last<BR>> > night.<BR>> >> I also find it odd that Corine
never apologized for her misleading<BR>> >> post.<BR>>
>> I'm still in total shock at how her post was worded.
And to post<BR>> >> that<BR>> > on<BR>> >> the
list when we all have a speak window or other form of
Dectalk.<BR>> > Heck,<BR>> >> if<BR>> >> I did
have a singing SAPI, why would anyone buy her non-singing<BR>>
> version?<BR>> >><BR>> >> That post just totally made no
sense to me. I still feel bad about<BR>> >>
my<BR>> >> response, but I was and still am
angry.<BR>> >><BR>> >><BR>> >> SNOOPI
BOTTEN<BR>> >><BR>> >><BR>> >> In a message dated
6/27/2011 1:22:03 P.M. Eastern Daylight Time,<BR>> >>
_linuxx64.bashsh@gmail.com_ (mailto:<A
href="mailto:linuxx64.bashsh@gmail.com">linuxx64.bashsh@gmail.com</A>)
writes:<BR>> >><BR>> >> Your message came
through. It's all good.<BR>> >><BR>> >> Alex<BR>>
>><BR>> >> On 6/27/2011 12:58 PM, _Dectalk@aol.com_
(mailto:<A href="mailto:Dectalk@aol.com">Dectalk@aol.com</A>)<BR>> >
wrote:<BR>> >> My mail got too full, so I'm just making sure
everything is ok.<BR>> >><BR>> >><BR>>
>> SNOOPI BOTTEN<BR>> >><BR>> >><BR>> >>
_______________________________________________<BR>> >><BR>>
>> DECtalk mailing list<BR>> >><BR>> >>
_DECtalk@bluegrasspals.com_ (mailto:<A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A>)<BR>>
>><BR>> >> _<A
href="http://bluegrasspals.com/mailman/listinfo/dectalk_"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk_</A><BR>>
>> (<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A>)<BR>>
>><BR>> >><BR>> >><BR>> >><BR>> >>
--<BR>> >> Sent via Thunderbird.<BR>> >><BR>>
>><BR>> >>
_______________________________________________<BR>> >> DECtalk
mailing list<BR>> >> _DECtalk@bluegrasspals.com_
(mailto:<A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A>)<BR>>
>> _<A href="http://bluegrasspals.com/mailman/listinfo/dectalk_"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk_</A><BR>>
>> (<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A>)<BR>>
>><BR>> >><BR>> >><BR>> >><BR>>
>><BR>> >><BR>> >>
_______________________________________________<BR>> >> DECtalk
mailing list<BR>> >> _DECtalk@bluegrasspals.com_
(mailto:<A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A>)<BR>>
>> _<A href="http://bluegrasspals.com/mailman/listinfo/dectalk_"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk_</A><BR>>
>> (<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A>)<BR>>
>><BR>> >><BR>> >><BR>> >><BR>>
>><BR>> >> =<BR>> >><BR>> >>
_______________________________________________<BR>> >> DECtalk
mailing list<BR>> >> <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
>> <A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>>
>><BR>> >><BR>> ><BR>> ><BR>> ><BR>>
----------------------------------------------------------------------------<BR>>
> ----<BR>> ><BR>> ><BR>> >>
_______________________________________________<BR>> >> DECtalk
mailing list<BR>> >> <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
>> <A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>>
>><BR>> ><BR>> >
_______________________________________________<BR>> > DECtalk mailing
list<BR>> > <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
> <A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>>
><BR>> ><BR>><BR>><BR>><BR>>
--------------------------------------------------------------------------------<BR>><BR>><BR>>
> _______________________________________________<BR>> > DECtalk
mailing list<BR>> > <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
> <A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>>
><BR>><BR>> _______________________________________________<BR>>
DECtalk mailing list<BR>> <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>><BR>><BR>>
_______________________________________________<BR>> DECtalk mailing
list<BR>> <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>><BR>><BR><BR><BR><BR></DIV></DIV>--------------------------------------------------------------------------------<BR>
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR>>
_______________________________________________<BR>> DECtalk mailing
list<BR>> <A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR>>
<A href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR>><BR><BR>_______________________________________________<BR>DECtalk
mailing list<BR><A
href="mailto:DECtalk@bluegrasspals.com">DECtalk@bluegrasspals.com</A><BR><A
href="http://bluegrasspals.com/mailman/listinfo/dectalk"
target=_blank>http://bluegrasspals.com/mailman/listinfo/dectalk</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>