[Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

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

[Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

Brian Gaff Lineone downstairs

----- Original Message -----
From: "Brian Gaff Lineone downstairs" <[hidden email]>
To: <[hidden email]>
Sent: Friday, March 19, 2010 1:15 PM
Subject: [nvda] Re: For all those looking for Sapi4 problem, please read


> Hi, just wondering if there is a list somewhere which matches the trunc
> and main snap numbers?
> I am trying to figure out the dates, and unfortunately, although the
> changelogs exist, they are  in the main numbering system, and more than
> that, some dates in the  screens seem to suggest that  some changes in
> earlier numbered snaps are after  rather   than before the ones already
> seen.
>
> Looking at this one..
>
> [main,3353]
>
> 5 weeks
>
> James Teh <[hidden email]>
>
>
>
> speech: Add REASON_FOCUSENTERED which now gets used by event_focusEntered
> instead of calling speakObjectProperties directly. Aside from being
> cleaner (isolating this code to speech), this also means that settings
> such as report object descriptions are honoured for focus entered.
>
>
>
>
>
>
>
> It suggests 15th of Feb, but a few snaps before seem to have dates of the
> 16th.
>
>
>
> Brian
>
> ----- Original Message -----
> From: " brian gafff (Line One)" <[hidden email]>
> To: "NVDA screen reader support list" <[hidden email]>;
> "News and discussion for NVDA (NonVisual Desktop Access),a free and open
> source screen reader for Microsoft Windows" <[hidden email]>;
> "nvda mailing list" <[hidden email]>
> Sent: Friday, March 19, 2010 11:49 AM
> Subject: [nvda] For all those looking for Sapi4 problem, please read
>
>
>> Hi folks, The change which made some machines not like some sapi4 voices
>> happened between 9th and 15th February.
>>
>> Between snaps trunxx25 and snap truncxx69.
>>
>> I seem to have a gap in snaps for those few days, but this should make it
>> easier to see where the problems happened I think.
>>
>> If anyone has got snaps between those and can make them available, I have
>> a couple of days in which I'm happy to try them out with a machine that
>> gives the fatal errors, which cannot be good to have, as Murphy will
>> dictate that it will pop up and bute us later on!
>>
>>
>> Cheers.
>>
>> 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!
>>
>> Remember that open source software is community supported! Please donate
>> if you can because even a little can help a lot:
>> http://www.nvaccess.org/wiki/Donate
>> To post messages to the list send email to
>> [hidden email]
>> To modify your NVDA Email settings or view archives go to:
>> http://www.freelists.org/list/nvda
>> Thank you for your continued support of Nonvisual Desktop Access, an open
>> source free screen reader for Microsoft Windows:
>> http://www.nvda-project.org/
>> NVDA Snapshot Downloader:
>> http://nvdasd.webra-system.sk/
>> Get SkypeTalking for NVDA:
>> http://skypetalking.googlecode.com/
>>
>
>
> Remember that open source software is community supported! Please donate
> if you can because even a little can help a lot:
> http://www.nvaccess.org/wiki/Donate
> To post messages to the list send email to
> [hidden email]
> To modify your NVDA Email settings or view archives go to:
> http://www.freelists.org/list/nvda
> Thank you for your continued support of Nonvisual Desktop Access, an open
> source free screen reader for Microsoft Windows:
> http://www.nvda-project.org/
> NVDA Snapshot Downloader:
> http://nvdasd.webra-system.sk/
> Get SkypeTalking for NVDA:
> http://skypetalking.googlecode.com/
>




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

Brian Gaff Lineone downstairs
Disregard my comments on dates running backwards, its me trying to be too
clever by calculating the snap numbers from trac to main and not doing my
sums right. However the bit posted is the last bit of work done on the 15th
of Feb as far as I can say, but as I do not have the snaps to test till the
9th, I'm still  not sure.

Brian
----- Original Message -----
From: "Brian Gaff Lineone downstairs" <[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, March 19, 2010 1:17 PM
Subject: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4
problem,please read


>
> ----- Original Message -----
> From: "Brian Gaff Lineone downstairs" <[hidden email]>
> To: <[hidden email]>
> Sent: Friday, March 19, 2010 1:15 PM
> Subject: [nvda] Re: For all those looking for Sapi4 problem, please read
>
>
>> Hi, just wondering if there is a list somewhere which matches the trunc
>> and main snap numbers?
>> I am trying to figure out the dates, and unfortunately, although the
>> changelogs exist, they are  in the main numbering system, and more than
>> that, some dates in the  screens seem to suggest that  some changes in
>> earlier numbered snaps are after  rather   than before the ones already
>> seen.
>>
>> Looking at this one..
>>
>> [main,3353]
>>
>> 5 weeks
>>
>> James Teh <[hidden email]>
>>
>>
>>
>> speech: Add REASON_FOCUSENTERED which now gets used by event_focusEntered
>> instead of calling speakObjectProperties directly. Aside from being
>> cleaner (isolating this code to speech), this also means that settings
>> such as report object descriptions are honoured for focus entered.
>>
>>
>>
>>
>>
>>
>>
>> It suggests 15th of Feb, but a few snaps before seem to have dates of the
>> 16th.
>>
>>
>>
>> Brian
>>
>> ----- Original Message -----
>> From: " brian gafff (Line One)" <[hidden email]>
>> To: "NVDA screen reader support list" <[hidden email]>;
>> "News and discussion for NVDA (NonVisual Desktop Access),a free and open
>> source screen reader for Microsoft Windows"
>> <[hidden email]>; "nvda mailing list" <[hidden email]>
>> Sent: Friday, March 19, 2010 11:49 AM
>> Subject: [nvda] For all those looking for Sapi4 problem, please read
>>
>>
>>> Hi folks, The change which made some machines not like some sapi4 voices
>>> happened between 9th and 15th February.
>>>
>>> Between snaps trunxx25 and snap truncxx69.
>>>
>>> I seem to have a gap in snaps for those few days, but this should make
>>> it easier to see where the problems happened I think.
>>>
>>> If anyone has got snaps between those and can make them available, I
>>> have a couple of days in which I'm happy to try them out with a machine
>>> that gives the fatal errors, which cannot be good to have, as Murphy
>>> will dictate that it will pop up and bute us later on!
>>>
>>>
>>> Cheers.
>>>
>>> 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!
>>>
>>> Remember that open source software is community supported! Please donate
>>> if you can because even a little can help a lot:
>>> http://www.nvaccess.org/wiki/Donate
>>> To post messages to the list send email to
>>> [hidden email]
>>> To modify your NVDA Email settings or view archives go to:
>>> http://www.freelists.org/list/nvda
>>> Thank you for your continued support of Nonvisual Desktop Access, an
>>> open source free screen reader for Microsoft Windows:
>>> http://www.nvda-project.org/
>>> NVDA Snapshot Downloader:
>>> http://nvdasd.webra-system.sk/
>>> Get SkypeTalking for NVDA:
>>> http://skypetalking.googlecode.com/
>>>
>>
>>
>> Remember that open source software is community supported! Please donate
>> if you can because even a little can help a lot:
>> http://www.nvaccess.org/wiki/Donate
>> To post messages to the list send email to
>> [hidden email]
>> To modify your NVDA Email settings or view archives go to:
>> http://www.freelists.org/list/nvda
>> Thank you for your continued support of Nonvisual Desktop Access, an open
>> source free screen reader for Microsoft Windows:
>> http://www.nvda-project.org/
>> NVDA Snapshot Downloader:
>> http://nvdasd.webra-system.sk/
>> Get SkypeTalking for NVDA:
>> http://skypetalking.googlecode.com/
>>
>
>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev
>




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

James Teh
Err... I provided you with an experimental sapi4 driver to test (see
previous messages). Have you given this a shot?

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] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

Brian Gaff Lineone downstairs
I never saw it, I wwonder if Google ate it.
The bloomin  Virgin email keeps losing the messages as some attaches are
deleted. Did you send it to this address or one of the blueyonder ones. This
one should be OK as its outside of Googles clutches, so I'm a bit worried if
its been deleted silently.

Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[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, March 19, 2010 2:57 PM
Subject: Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4
problem, please read


> Err... I provided you with an experimental sapi4 driver to test (see
> previous messages). Have you given this a shot?
>
> 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


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



This is a cuddly message, no virus seen!
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2755 - Release Date: 03/18/10
19:33:00




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4 problem, please read

Brian Gaff Lineone downstairs
In reply to this post by James Teh
Hi, James, just nipped onto Imap and its there, so I've grabbed it. Not sure
what the pop3 server did with it, but worry not, I've got it now.

I'll go away and have a look

Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[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, March 19, 2010 2:57 PM
Subject: Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4
problem, please read


> Err... I provided you with an experimental sapi4 driver to test (see
> previous messages). Have you given this a shot?
>
> 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


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



This is a cuddly message, no virus seen!
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2755 - Release Date: 03/18/10
19:33:00




Reply | Threaded
Open this post in threaded view
|

[Nvda-dev] Sapi4 new driver and log

Brian Gaff Lineone downstairs
In reply to this post by James Teh
OK, on a quick test on the portable version of the release beta it seems to
work OK  at least as far as cursoring around the list is concerned
I attach that log.


I assume as that folder is empty, that the  driver there replaces an inbuilt
one  now.
Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[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, March 19, 2010 2:57 PM
Subject: Re: [Nvda-dev] Fw: [nvda] Re: For all those looking for Sapi4
problem, please read


> Err... I provided you with an experimental sapi4 driver to test (see
> previous messages). Have you given this a shot?
>
> 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

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



This is a cuddly message, no virus seen!
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2755 - Release Date: 03/18/10
19:33:00

sapi4new driver_nvda.log (23K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Sapi4 new driver and log

James Teh
On 20/03/2010 2:23 AM, Brian Gaff Lineone downstairs wrote:
> OK, on a quick test on the portable version of the release beta it seems
> to work OK at least as far as cursoring around the list is concerned
> I attach that log.
The "Release() called too many times" message is generated when the
synthesiser tries to release an object that we gave it more times than
it should, which is extremely broken behaviour. It should only release
as many times as it acquires, but it seems to release more, which would
normally cause our object to die prematurely, causing all sorts of
trouble. The hack I've implemented here tries to forceably stop the
object from dying until we're ready for it to die.

What I don't understand is why this doesn't cause crashes in other
screen readers or programs that use SAPI4. Has anyone tested any of
these synths with other programs?

Just to clarify, does this happen for you personally with all SAPI4
synths or just Orpheus? Also, is this perhaps an older version of
Orpheus? We found a demo of Orpheus distributed by some other company (I
forget the name), but couldn't reproduce the problem with that version.

> I assume as that folder is empty, that the driver there replaces an
> inbuilt one now.
Correct.

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] Sapi4 new driver and log

Brian Gaff Lineone downstairs
This time difference has meant i have slept since my last message.
The Orpheus I'm using came with  my version of Supernova, which started life
as 5.21, but was upgraded to 6.23 at some point. I have a later Hal, but the
version with that is sapi5 not 4, so its going to be fairly old in any case.
However the Sapi5 one is very slow on my machine, much more than 4.


I also notice that every installer for a voice comes with another archive of
the Sapi installers, and at times you will see the this file is older than
the existing file message.

The only voice it seems not to happen on inat all, ids LH. The Microsoft
ones are better, in that when they die, they tend to just not say anything,
not creat the error. The  unknown legality from the archive called
Outloud.zip is not too bad, but once again can die the silent death.

Its really Orpheus which seemed to be the most annoying.
I've not had a silent crash either since I put in the driver, but will
switch in sapi4 later on for reading some web stuff, and see if its still
OK, I can olso try it on other  machines.

The dodgy archive called viavoice, a cut down US only version, is very very
bad by the way, it crashes like Orpheus.

I'm thinking that other people may well have various versions of the sapi
driver, various versions of different voices, making the possibilities for
mixing and matching rather large with strange results.

I think the most annoying thing about the crash is that it remains crashed.
Thus you cannot select a good synth, without restarting nvda and being very
careful!

Brian

[hidden email]
Brian Gaff's other account.

----- Original Message -----
From: "James Teh" <[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, March 19, 2010 5:37 PM
Subject: Re: [Nvda-dev] Sapi4 new driver and log


> On 20/03/2010 2:23 AM, Brian Gaff Lineone downstairs wrote:
>> OK, on a quick test on the portable version of the release beta it seems
>> to work OK at least as far as cursoring around the list is concerned
>> I attach that log.
> The "Release() called too many times" message is generated when the
> synthesiser tries to release an object that we gave it more times than
> it should, which is extremely broken behaviour. It should only release
> as many times as it acquires, but it seems to release more, which would
> normally cause our object to die prematurely, causing all sorts of
> trouble. The hack I've implemented here tries to forceably stop the
> object from dying until we're ready for it to die.
>
> What I don't understand is why this doesn't cause crashes in other
> screen readers or programs that use SAPI4. Has anyone tested any of
> these synths with other programs?
>
> Just to clarify, does this happen for you personally with all SAPI4
> synths or just Orpheus? Also, is this perhaps an older version of
> Orpheus? We found a demo of Orpheus distributed by some other company (I
> forget the name), but couldn't reproduce the problem with that version.
>
>> I assume as that folder is empty, that the driver there replaces an
>> inbuilt one now.
> Correct.
>
> 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


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



This is a cuddly message, no virus seen!
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2758 - Release Date: 03/19/10
22:07:00




Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Sapi4 new driver and log

Brian Gaff Lineone downstairs
In reply to this post by James Teh
Hi, the new driver seems to work OK on my three machines.

I will bring two things to your attention however.

If for example, you leave the voices dialogue open and open the synth
dialogue and set it to something else, say, Espeak and hit enter, the voice
selection is still set to sapi4 and thus errors ocur as you cursor up and
down as the voices are invalid for the synth.
Of course you would need to be barking mad to do this, so a barking mad log
is attached.

The other thing is that the sequence of synths is changed with the new
driver, but I doubt this matters.

Note in the log that only some of the Orpheus voices are misbehaving this
morning. Seems to be a bit random.

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: "James Teh" <[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, March 19, 2010 5:37 PM
Subject: Re: [Nvda-dev] Sapi4 new driver and log


> On 20/03/2010 2:23 AM, Brian Gaff Lineone downstairs wrote:
>> OK, on a quick test on the portable version of the release beta it seems
>> to work OK at least as far as cursoring around the list is concerned
>> I attach that log.
> The "Release() called too many times" message is generated when the
> synthesiser tries to release an object that we gave it more times than
> it should, which is extremely broken behaviour. It should only release
> as many times as it acquires, but it seems to release more, which would
> normally cause our object to die prematurely, causing all sorts of
> trouble. The hack I've implemented here tries to forceably stop the
> object from dying until we're ready for it to die.
>
> What I don't understand is why this doesn't cause crashes in other
> screen readers or programs that use SAPI4. Has anyone tested any of
> these synths with other programs?
>
> Just to clarify, does this happen for you personally with all SAPI4
> synths or just Orpheus? Also, is this perhaps an older version of
> Orpheus? We found a demo of Orpheus distributed by some other company (I
> forget the name), but couldn't reproduce the problem with that version.
>
>> I assume as that folder is empty, that the driver there replaces an
>> inbuilt one now.
> Correct.
>
> 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

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



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2759 - Release Date: 03/20/10
07:33:00

voice select bug-nvda.log (61K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Sapi4 new driver and log

mk360
In reply to this post by Brian Gaff Lineone downstairs
    Wenas master,

    A raíz de tanto mensaje sobre sapi 4 que se ha generado me surje una
duda ¿has escuchado la voz de orpheus en inglés? si lo has hecho ¿es mejor
que la en español? porque recuerdo que cuando la usé era realmente mala, al
punto que si hubiese conocido espeak habría usado esa, y en esos tiempos yo
venía del ciber...
----- Original Message -----
From: "Brian Gaff Lineone downstairs" <[hidden email]>
To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
source screen reader for Microsoft Windows" <[hidden email]>
Sent: Saturday, March 20, 2010 6:14 AM
Subject: Re: [Nvda-dev] Sapi4 new driver and log


> This time difference has meant i have slept since my last message.
> The Orpheus I'm using came with  my version of Supernova, which started
> life as 5.21, but was upgraded to 6.23 at some point. I have a later Hal,
> but the version with that is sapi5 not 4, so its going to be fairly old in
> any case. However the Sapi5 one is very slow on my machine, much more than
> 4.
>
>
> I also notice that every installer for a voice comes with another archive
> of the Sapi installers, and at times you will see the this file is older
> than the existing file message.
>
> The only voice it seems not to happen on inat all, ids LH. The Microsoft
> ones are better, in that when they die, they tend to just not say
> anything, not creat the error. The  unknown legality from the archive
> called Outloud.zip is not too bad, but once again can die the silent
> death.
>
> Its really Orpheus which seemed to be the most annoying.
> I've not had a silent crash either since I put in the driver, but will
> switch in sapi4 later on for reading some web stuff, and see if its still
> OK, I can olso try it on other  machines.
>
> The dodgy archive called viavoice, a cut down US only version, is very
> very bad by the way, it crashes like Orpheus.
>
> I'm thinking that other people may well have various versions of the sapi
> driver, various versions of different voices, making the possibilities for
> mixing and matching rather large with strange results.
>
> I think the most annoying thing about the crash is that it remains
> crashed. Thus you cannot select a good synth, without restarting nvda and
> being very careful!
>
> Brian
>
> [hidden email]
> Brian Gaff's other account.
>
> ----- Original Message -----
> From: "James Teh" <[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, March 19, 2010 5:37 PM
> Subject: Re: [Nvda-dev] Sapi4 new driver and log
>
>
>> On 20/03/2010 2:23 AM, Brian Gaff Lineone downstairs wrote:
>>> OK, on a quick test on the portable version of the release beta it seems
>>> to work OK at least as far as cursoring around the list is concerned
>>> I attach that log.
>> The "Release() called too many times" message is generated when the
>> synthesiser tries to release an object that we gave it more times than
>> it should, which is extremely broken behaviour. It should only release
>> as many times as it acquires, but it seems to release more, which would
>> normally cause our object to die prematurely, causing all sorts of
>> trouble. The hack I've implemented here tries to forceably stop the
>> object from dying until we're ready for it to die.
>>
>> What I don't understand is why this doesn't cause crashes in other
>> screen readers or programs that use SAPI4. Has anyone tested any of
>> these synths with other programs?
>>
>> Just to clarify, does this happen for you personally with all SAPI4
>> synths or just Orpheus? Also, is this perhaps an older version of
>> Orpheus? We found a demo of Orpheus distributed by some other company (I
>> forget the name), but couldn't reproduce the problem with that version.
>>
>>> I assume as that folder is empty, that the driver there replaces an
>>> inbuilt one now.
>> Correct.
>>
>> 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
>
>
> --------------------------------------------------------------------------------
>
>
>
> This is a cuddly message, no virus seen!
> Checked by AVG - www.avg.com
> Version: 9.0.791 / Virus Database: 271.1.1/2758 - Release Date: 03/19/10
> 22:07:00
>
>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev 



Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Sapi4 new driver and log

mk360
In reply to this post by Brian Gaff Lineone downstairs
    Sorry for the previous message, I forgot to change que mail :P.

    Regards,
    mk.
----- Original Message -----
From: "Brian Gaff Lineone downstairs" <[hidden email]>
To: "News and discussion for NVDA (NonVisual Desktop Access),a free and open
source screen reader for Microsoft Windows" <[hidden email]>
Sent: Saturday, March 20, 2010 6:14 AM
Subject: Re: [Nvda-dev] Sapi4 new driver and log


> This time difference has meant i have slept since my last message.
> The Orpheus I'm using came with  my version of Supernova, which started
> life as 5.21, but was upgraded to 6.23 at some point. I have a later Hal,
> but the version with that is sapi5 not 4, so its going to be fairly old in
> any case. However the Sapi5 one is very slow on my machine, much more than
> 4.
>
>
> I also notice that every installer for a voice comes with another archive
> of the Sapi installers, and at times you will see the this file is older
> than the existing file message.
>
> The only voice it seems not to happen on inat all, ids LH. The Microsoft
> ones are better, in that when they die, they tend to just not say
> anything, not creat the error. The  unknown legality from the archive
> called Outloud.zip is not too bad, but once again can die the silent
> death.
>
> Its really Orpheus which seemed to be the most annoying.
> I've not had a silent crash either since I put in the driver, but will
> switch in sapi4 later on for reading some web stuff, and see if its still
> OK, I can olso try it on other  machines.
>
> The dodgy archive called viavoice, a cut down US only version, is very
> very bad by the way, it crashes like Orpheus.
>
> I'm thinking that other people may well have various versions of the sapi
> driver, various versions of different voices, making the possibilities for
> mixing and matching rather large with strange results.
>
> I think the most annoying thing about the crash is that it remains
> crashed. Thus you cannot select a good synth, without restarting nvda and
> being very careful!
>
> Brian
>
> [hidden email]
> Brian Gaff's other account.
>
> ----- Original Message -----
> From: "James Teh" <[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, March 19, 2010 5:37 PM
> Subject: Re: [Nvda-dev] Sapi4 new driver and log
>
>
>> On 20/03/2010 2:23 AM, Brian Gaff Lineone downstairs wrote:
>>> OK, on a quick test on the portable version of the release beta it seems
>>> to work OK at least as far as cursoring around the list is concerned
>>> I attach that log.
>> The "Release() called too many times" message is generated when the
>> synthesiser tries to release an object that we gave it more times than
>> it should, which is extremely broken behaviour. It should only release
>> as many times as it acquires, but it seems to release more, which would
>> normally cause our object to die prematurely, causing all sorts of
>> trouble. The hack I've implemented here tries to forceably stop the
>> object from dying until we're ready for it to die.
>>
>> What I don't understand is why this doesn't cause crashes in other
>> screen readers or programs that use SAPI4. Has anyone tested any of
>> these synths with other programs?
>>
>> Just to clarify, does this happen for you personally with all SAPI4
>> synths or just Orpheus? Also, is this perhaps an older version of
>> Orpheus? We found a demo of Orpheus distributed by some other company (I
>> forget the name), but couldn't reproduce the problem with that version.
>>
>>> I assume as that folder is empty, that the driver there replaces an
>>> inbuilt one now.
>> Correct.
>>
>> 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
>
>
> --------------------------------------------------------------------------------
>
>
>
> This is a cuddly message, no virus seen!
> Checked by AVG - www.avg.com
> Version: 9.0.791 / Virus Database: 271.1.1/2758 - Release Date: 03/19/10
> 22:07:00
>
>
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev