[DECtalk] something i heard
Dectalk at aol.com
Dectalk at aol.com
Mon May 9 10:49:19 EDT 2011
Actually, does anyone have or know how to create a 4.40 installer that
will do the file association?
SNOOPI BOTTEN
In a message dated 5/9/2011 10:40:32 A.M. Eastern Daylight Time,
ratguy at insightbb.com writes:
Hi,
Probably what really needs to happen when it comes right down to it is
that
the Speak window needs to be rewritten from scratch. That program, in one
form or another, has been around for quite some time. Technology changes,
and Speak probably hasn't kept up. Unfortunately, the only Speak window I
know of which actually uses a dectalk.dll is the most recent one, for the
so-nicknamed DECtalk 86. All the others I've seen appear to have the
actual
DECtalk code included within the Speak executable. My thought is that, if
you had a dectalk.dll and knew how it worked, you could write a replica
Speak window from scratch, in a language of your choice.
Jayson
----- Original Message -----
From: <Dectalk at aol.com>
To: <dectalk at bluegrasspals.com>
Sent: Monday, May 09, 2011 7:34 AM
Subject: Re: [DECtalk] something i heard
> it needs the commands. Let me emplane why. Most of you on this list
> just
> make Dectalk sing for fun. People who can't talk, have no other way of
> singing, Dectalk is the only way they have to sing. I'm one of them,
but
> only one of many. Today I'm trying to finish "THE HALLELUJAH CHORUS"
in
> 4
> part harmony so 4 people with Dectalk can all sing together. I wanted
> more
> parts but I can't find a version of sheet music that has more than 4
> parts.
>
> In any event, there is a serious problem coming up. I have no idea why,
> but the 4.40 speak window will not install in the latest update of
> Windows
> 7, the en files will not associate with the speak window. I now have 3
> known computers that the speak window will not run on.
>
> Blake and I have posted about this several times but it keeps getting
> ignored. Guys, if we don't solve this problem, and if any of you ever
> switch
> computers, you might not be able to run Dectalk.
>
>
> SNOOPI BOTTEN
>
>
> In a message dated 5/8/2011 11:58:43 P.M. Eastern Daylight Time,
> bmisch2002 at gmail.com writes:
>
> thanks both of you for this project. maybe when you guys get the code
> compiled wright, or the wright code at all, you can make a sapi version
> of
> dectalk that is better than the stuff already put out there. maybe a
sapi
> dectalk with not just voices but commands and everything.
>
> On May 8, 2011, at 12:46 PM, Blake Roberts wrote:
>
>> Ed,
>> Thanks for the clarification and your dedication to, like Corine, not
> give
>> up on Dectalk.
>> Blake
>>
>> -----Original Message-----
>> From: dectalk-bounces at bluegrasspals.com
>> [mailto:dectalk-bounces at bluegrasspals.com] On Behalf Of ebruckert
> Bruckert
>> Sent: Sunday, May 08, 2011 12:42 PM
>> To: DECtalk Discussions
>> Subject: Re: [DECtalk] something i heard
>>
>> I'm sorry I have to set the record straight. I am the one that
supplied
>> Kareem with code and there was confusion because they hadn't been
> compiled
>> in a while and I knew they needed fixing and I don't think that was
>> truly
>> understood and no I didn't get a single penny. Neither am I giving up I
> need
>> a decent DECtalk as well this went down the rat hole for various
reasons
> and
>> I'm not giving up I want one I don't want to play a blame game however.
> But
>> nobody intentionally did anything wrong period.
>>
>>
>> On Sun, May 8, 2011 at 12:33 PM, Michael Hansen <amtk62 at gmail.com>
>> wrote:
>>
>>
>> So basicly, if I understand this right, someone in essence took
>> advantage of Corine's lack of DECtalk knowledge and sold her a code
>> to
>> Fonix Talk--or something very nearly like it--and said it was good?
>> How aweful.
>>
>> It's all starting to make sense now. Corine, I for one am very
>> sorry
>> for contributing to your company's public humiliation on this
>> mailing
>> list. It appears Fonix is the one to blame, and if they really did
>> screw you guys over (I know you can never say that publicly) then
>> that
>> is a real shame. Thank you for trying, and thank you for
>> withholding
>> this release.
>>
>> Best,
>> Michael Hansen
>>
>>
>> On 5/8/11, Dectalk at aol.com <Dectalk at aol.com> wrote:
>> > Yes but guys, can we be sensitive here for Corine? She cares so
>> much that
>> > she put a lot of money into this. She was sold a bad code and
>> has no way
>> > to get a refund. This is both happy and sad news. We should all
>> deeply
>> > thank her for trying.
>> >
>> >
>> > SNOOPI BOTTEN
>> >
>> >
>> > In a message dated 5/8/2011 11:37:11 A.M. Eastern Daylight Time,
>> > beroberts at hughes.net writes:
>> >
>> > Alex did a fantastic job creating the Dectalk vs. FonixTalk file
>> that
>> > Jayson
>> > shared. Excellent job on production, Alex.
>> > I agree with Jayson about Dectalk 86 sounding more like FonixTalk
>> than
>> > Dectalk. It is certainly good news that Enable wil not be
>> marketing
>> > Dectalk
>> > 86.
>> > Blake
>> > -----Original Message-----
>> > From: dectalk-bounces at bluegrasspals.com
>> > [mailto:dectalk-bounces at bluegrasspals.com] On Behalf Of Jayson
>> Smith
>> > Sent: Sunday, May 08, 2011 11:05 AM
>> > To: DECtalk Discussions
>> > Subject: Re: [DECtalk] something i heard
>> >
>> > I have to sort of agree with this, although Corine has stated
>> that the
>> > so-nicknamed DECtalk 86 doesn't use FonixTalk. To hear a sample of
>> the real
>> > FonixTalk, listen to the following file.
>> > http://www.q-audio.net/d/18754
>> > I think DECtalk 86 sounds more like FonixTalk than it does any
>> version of
>> > DECtalk including 4.64 or 5.0.
>> > Jayson
>> >
>> > ----- Original Message -----
>> > From: "Brandon Misch" <bmisch2002 at gmail.com>
>> > To: "DECtalk Discussions" <dectalk at bluegrasspals.com>
>> > Sent: Saturday, May 07, 2011 7:26 PM
>> > Subject: [DECtalk] something i heard
>> >
>> >
>> >> Hey guys i let someone hear a demo of the speak window for the
>> sapi
>> >> dectalk that enable is selling and that person said that this is
>> based
>> > on
>> >> fonix talk. don't know if anyone came up with that yet.
>> >>
>> >>
>> >> _______________________________________________
>> >> DECtalk mailing list
>> >> DECtalk at bluegrasspals.com
>> >> http://bluegrasspals.com/mailman/listinfo/dectalk
>> >
>> > _______________________________________________
>> > DECtalk mailing list
>> > DECtalk at bluegrasspals.com
>> > http://bluegrasspals.com/mailman/listinfo/dectalk
>> >
>> > _______________________________________________
>> > DECtalk mailing list
>> > DECtalk at bluegrasspals.com
>> > http://bluegrasspals.com/mailman/listinfo/dectalk
>> >
>> >
>> _______________________________________________
>> DECtalk mailing list
>> DECtalk at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/dectalk
>>
>>
>>
>>
>> _______________________________________________
>> DECtalk mailing list
>> DECtalk at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/dectalk
>
>
> _______________________________________________
> DECtalk mailing list
> DECtalk at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/dectalk
>
>
----------------------------------------------------------------------------
----
> _______________________________________________
> DECtalk mailing list
> DECtalk at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/dectalk
>
_______________________________________________
DECtalk mailing list
DECtalk at bluegrasspals.com
http://bluegrasspals.com/mailman/listinfo/dectalk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/dectalk/attachments/20110509/388461aa/attachment.html>
More information about the Dectalk
mailing list