Well i told you what i think about you and your way of thinking in the message above so from me no mor comments on none of your posts. ----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Monday, April 14, 2008 1:06 PMSubject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting Introduction
I already have that book. Have you read it?Do you think that covers all the things that the guys that made Eloquence, AT&T Natural Voices, DEC Talk know, in order to be able to make a synthesizer at least as good as those?You got a problem man. I told that this information is good to have, and I told that it would require much more information than that book you are talking about, in order to be able to create a real good synthesizer. Don't you agree? Or you think that most blind programmers are lazy enough and don't want to read just that book for beeing able to create a synthesizer?I know another good programmer that might still be a member of this list, which is much more interested in this subject than me and who knows much more than me about synthesizers, and he would have already made one until now if that book would have been enough.Octavian----- Original Message ----- From: "Mario Percinic" <mario.percinic@xxxxxxxxx>To: <programmingblind@xxxxxxxxxxxxx> Sent: Monday, April 14, 2008 11:27 AMSubject: RE: Fritz Will Be Digging Into This - Window-Eyes Scripting IntroductionLol man you are really starting to be funny. Again for who knows how many times you are concluding something without complete imformation.So next time before you start making conclusions, , checkout google and thebook called "MAPI,SAPI and TAPI Developer's Guide" -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Octavian RasnitaSent: Monday, April 14, 2008 9:51 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting IntroductionThat information, which I think it can also be found on Microsoft's site, isgood to have, but it would be also helpful to have as much information aboutcreating a voice synthesizer. Creating a SAPI voice talks about the SAPI standard, but it would be also important to know the ways of creating synthesizers, how to compose thesounds, or how to join phonems, how to adjust the pitch, tone, how to parse the text for changing the sound parameters based on the grammar, and so on.Octavian----- Original Message ----- From: "Mario Percinic" <mario.percinic@xxxxxxxxx>To: <programmingblind@xxxxxxxxxxxxx> Sent: Monday, April 14, 2008 8:57 AM Subject: RE: Fritz Will Be Digging Into This - Window-Eyes Scripting IntroductionSure my friend, let me just brows thru my very big archive of ebooks and i'll send it to you. Don't worry it will be today :) -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of inthaneelf Sent: Monday, April 14, 2008 2:14 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting IntroductionMario, in your last message, you said "I have the documentation about SAPIsynths and how to make them, I can send you the book about it." would you send me that book/information please, there have been folks looking for information like that out here, smile. thanks, inthane ----- Original Message ----- From: "Mario Percinic" <mario.percinic@xxxxxxxxx> To: <programmingblind@xxxxxxxxxxxxx> Sent: Sunday, April 13, 2008 4:07 PM Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting IntroductionWell since you brought up some very good questions,let me break this message into logical pieces and give you the answers. ----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx> To: <programmingblind@xxxxxxxxxxxxx> Sent: Sunday, April 13, 2008 9:26 PM Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting Introduction"Yes, of course I am lazy. So? Is this a problem? :-)"No ofcourse not, everyone chooses its own way. I was just stating how the situation in general works with blind popularity, no matter in what country you are. Ok ofcourse, in smaller countrys like Romania or Croatia in my case, the situation is harder but than the person has to see if the solution can be adapted for your language considering the best results, financial situation, amount of people who work on the project, timing, knoledge etc."I don't think I can build a software synthesizer at least as good as US Eloquence by just reading the documentation and making research, without knowing C/C++."Correct, but i never said that. When i said that you can checkout espeak, i thought that you will find the documentation and the web page considering the thinks you did in the past. In order to make better improvements for espeak you really don't need to know c plus plus, ok if you know it better for you, but still you can see what sounds wrong and what you can do to make it sound better or to pronounce different characters or words, and also make different voices which really can sound completely different."There are more romanian synthesizers, but I don't like any of them, and they all are made by software companies that have more goodprogrammers.One of them sounds pretty good but is very slow responsive, another one sounds like a robot and it doesn't work at a higher rate, another one sounds very very bad (the one which is made by the german company Baum, that company that made Gnopernicus screen reader for Linux, and Virgo screen reader for Windows)."If some company has more developers employed that doesn't need to mean anything. In my case, software solutions which were made by an individual showed up as better because the developer really showed more interest that his aplication works with all screen readers,languages, protocols etc.I worked on almost all software synth development exept Check wintalker voice which is also have adapted for Croatian language. I told you to try and join espeak development team for Romanian mainly because espeak is right now used under windows as a sapi 5, as a stand alone portable version in windows screen reader called nvda, and orca for linux and also it can work with mac. So lots of platforms are supported, just because its author is very open minded and accepts lots of suggestion as long as the person knows language rules and something about computer usage. If you need more info about speech synths you can contact me privately and i'll write you more about it."Even if I would know C/C++, I don't think that it would be easy enough to create a better synthesizer than US Eloquence. And by the way, where can we find documentation about how to create a synthesizer at least as good and fast as Eloquence? I am asking this, because you seem to be very well informed..."I have the documentation about sapi synths and how to make them, i can send you the book about it. Eloquence as far as i'm aware came out from IBM's via voice which became eloquence at the later time. Eloquence belongs to the group of formant speech synthesizers and that explains one of the sides why is it so responsive. Mario __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind__________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind__________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind__________View the list's information and change your settings at //www.freelists.org/list/programmingblind
__________View the list's information and change your settings at //www.freelists.org/list/programmingblind