JAWS and Eloquence
___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
JAWS and Eloquence
Listers, I know that this is a list devoted to our beloved Window-Eyes, and die-hards like you and me, so excuse having to bring up the fish. As it is, I am an occasional user of said screen reader, but for me there has been a major turnoff since the very first time I attempted to befriend the thing . It goes as follows. And I really hope that some of you have dealt with this issue successfully. It would seem that the folks who write the codes for JAWS have chosen to muck with their version of the Eloquence synthesizer, and by doing so, have messed up the pacing of it's delivery. The problem as I have experienced it is the matter of how Eloquence manages sentences. Instead of an appropriate pausing between sentences, JAWS Eloquence takes no pause at all for periods, but continues in a kind of blue streak affect that doesn't give one even enough time to digest the sentence as its own entity, you might say. I definitely prefer WE's pacing when it comes to sentences in particular. I'm not talking about a pregnant pause between sentences like you would get if you set it up to make such pauses, but a more natural pause in the manner of the Window-Eyes presentation. I hope this is all making sense, but it seems to me that some of you Eloquence users might know just what I am talking about, and also how to solve the problem. But who knows, maybe JAWS has simply created through their own version of Eloquence this issue, and that their is no solution at all other than a slight rewrite of their code which I'm sure I would have to move heaven and earth to convince them to do. Speaking of code, when I use my Code Factory Eloquence, the sentence pacing is correct, but they have their speed settings such that it goes a step either above or below my preferred reading level. I don't consider myself to be a total slow-poke when it comes to reading, though I like to set my reading speed at 41 when using Window-Eyes, a leisurely pace for me, but I am not quite sure of the exact speed that WE would indicate if they had been using Code Factory as their default version of Eloquence. Anyway, if some kind user would please tell me if indeed there is or is not a solution for this, and for me anyway, major issue, I would really appreciate hearing from you. Unfortunately, I'm going to have to get serious about learning JAWS, as my yearly subscription started in September of last year, but WE is still working reasonably for the apps I most often use, though less and less so it seems with each new update. But, I'm going to have to decide if it is worth paying that annual subscription fee to maintain it, or start focusing on NVDA or Narrator as my screen reader of choice. A big thanks in advance for any advice you all might have on this issue, Larry ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: JAWS and Eloquence
This has not really bothered me. I turned on WE and did notice the difference. I also tried NVDA with Eloquence and it is like JAWS with no pauses. Maybe it was WE that changed Eloquence to have the pauses? - Original Message - From: "Larry Higgins via Talk" To: "WindowEyes List" Cc: "Larry Higgins" Sent: Monday, March 1, 2021 11:15 AM Subject: JAWS and Eloquence Listers, I know that this is a list devoted to our beloved Window-Eyes, and die-hards like you and me, so excuse having to bring up the fish. As it is, I am an occasional user of said screen reader, but for me there has been a major turnoff since the very first time I attempted to befriend the thing . It goes as follows. And I really hope that some of you have dealt with this issue successfully. It would seem that the folks who write the codes for JAWS have chosen to muck with their version of the Eloquence synthesizer, and by doing so, have messed up the pacing of it's delivery. The problem as I have experienced it is the matter of how Eloquence manages sentences. Instead of an appropriate pausing between sentences, JAWS Eloquence takes no pause at all for periods, but continues in a kind of blue streak affect that doesn't give one even enough time to digest the sentence as its own entity, you might say. I definitely prefer WE's pacing when it comes to sentences in particular. I'm not talking about a pregnant pause between sentences like you would get if you set it up to make such pauses, but a more natural pause in the manner of the Window-Eyes presentation. I hope this is all making sense, but it seems to me that some of you Eloquence users might know just what I am talking about, and also how to solve the problem. But who knows, maybe JAWS has simply created through their own version of Eloquence this issue, and that their is no solution at all other than a slight rewrite of their code which I'm sure I would have to move heaven and earth to convince them to do. Speaking of code, when I use my Code Factory Eloquence, the sentence pacing is correct, but they have their speed settings such that it goes a step either above or below my preferred reading level. I don't consider myself to be a total slow-poke when it comes to reading, though I like to set my reading speed at 41 when using Window-Eyes, a leisurely pace for me, but I am not quite sure of the exact speed that WE would indicate if they had been using Code Factory as their default version of Eloquence. Anyway, if some kind user would please tell me if indeed there is or is not a solution for this, and for me anyway, major issue, I would really appreciate hearing from you. Unfortunately, I'm going to have to get serious about learning JAWS, as my yearly subscription started in September of last year, but WE is still working reasonably for the apps I most often use, though less and less so it seems with each new update. But, I'm going to have to decide if it is worth paying that annual subscription fee to maintain it, or start focusing on NVDA or Narrator as my screen reader of choice. A big thanks in advance for any advice you all might have on this issue, Larry ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/loyrg2845%40gmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: JAWS and Eloquence
This may indeed not be an issue for every Eloquence user, to each his own. However, although I wasn't even aware that NVDA came with Eloquence, if I use Code Factory's version of Eloquence, the pauses are the same as WE. The only issue I have with CF is that it goes a step above and a step below my preferred reading speed, but I have ways of getting around that. I can use Goldwave's text to speech to create .mp3 files for listening to long stretches for books and such. What can I say?, if most people actually prefer to have their speech delivery this way, then more power to them, but for me, it takes a heck of a lot of getting used too. On 3/2/2021 5:06 AM, Loy Green via Talk wrote: This has not really bothered me. I turned on WE and did notice the difference. I also tried NVDA with Eloquence and it is like JAWS with no pauses. Maybe it was WE that changed Eloquence to have the pauses? - Original Message - From: "Larry Higgins via Talk" To: "WindowEyes List" Cc: "Larry Higgins" Sent: Monday, March 1, 2021 11:15 AM Subject: JAWS and Eloquence Listers, I know that this is a list devoted to our beloved Window-Eyes, and die-hards like you and me, so excuse having to bring up the fish. As it is, I am an occasional user of said screen reader, but for me there has been a major turnoff since the very first time I attempted to befriend the thing . It goes as follows. And I really hope that some of you have dealt with this issue successfully. It would seem that the folks who write the codes for JAWS have chosen to muck with their version of the Eloquence synthesizer, and by doing so, have messed up the pacing of it's delivery. The problem as I have experienced it is the matter of how Eloquence manages sentences. Instead of an appropriate pausing between sentences, JAWS Eloquence takes no pause at all for periods, but continues in a kind of blue streak affect that doesn't give one even enough time to digest the sentence as its own entity, you might say. I definitely prefer WE's pacing when it comes to sentences in particular. I'm not talking about a pregnant pause between sentences like you would get if you set it up to make such pauses, but a more natural pause in the manner of the Window-Eyes presentation. I hope this is all making sense, but it seems to me that some of you Eloquence users might know just what I am talking about, and also how to solve the problem. But who knows, maybe JAWS has simply created through their own version of Eloquence this issue, and that their is no solution at all other than a slight rewrite of their code which I'm sure I would have to move heaven and earth to convince them to do. Speaking of code, when I use my Code Factory Eloquence, the sentence pacing is correct, but they have their speed settings such that it goes a step either above or below my preferred reading level. I don't consider myself to be a total slow-poke when it comes to reading, though I like to set my reading speed at 41 when using Window-Eyes, a leisurely pace for me, but I am not quite sure of the exact speed that WE would indicate if they had been using Code Factory as their default version of Eloquence. Anyway, if some kind user would please tell me if indeed there is or is not a solution for this, and for me anyway, major issue, I would really appreciate hearing from you. Unfortunately, I'm going to have to get serious about learning JAWS, as my yearly subscription started in September of last year, but WE is still working reasonably for the apps I most often use, though less and less so it seems with each new update. But, I'm going to have to decide if it is worth paying that annual subscription fee to maintain it, or start focusing on NVDA or Narrator as my screen reader of choice. A big thanks in advance for any advice you all might have on this issue, Larry ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/loyrg2845%40gmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/larryhiggins22%40comcast.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or op
RE: JAWS and Eloquence
Larry, There might be an answer for this because there are a number of different settings within JAWS that affects punctuation. I would second the suggestion that somebody else made that you contact Vispero Technical Support and raise your question there. Ironically, they have made some changes to the interface to Eloquence in the most recent versions of JAWS involving the volume. This won't get you there completely, but when I turn punctuation off, I find that there are still no pauses, but the voice inflection seems to indicate the end of a sentence. Best regards, Steve Jacobson Original Message- From: Talk On Behalf Of Larry Higgins via Talk Sent: Tuesday, March 2, 2021 6:36 AM To: Loy Green via Talk Cc: Larry Higgins Subject: Re: JAWS and Eloquence This may indeed not be an issue for every Eloquence user, to each his own. However, although I wasn't even aware that NVDA came with Eloquence, if I use Code Factory's version of Eloquence, the pauses are the same as WE. The only issue I have with CF is that it goes a step above and a step below my preferred reading speed, but I have ways of getting around that. I can use Goldwave's text to speech to create .mp3 files for listening to long stretches for books and such. What can I say?, if most people actually prefer to have their speech delivery this way, then more power to them, but for me, it takes a heck of a lot of getting used too. On 3/2/2021 5:06 AM, Loy Green via Talk wrote: > This has not really bothered me. I turned on WE and did notice the > difference. I also tried NVDA with Eloquence and it is like JAWS with no > pauses. Maybe it was WE that changed Eloquence to have the pauses? > - Original Message - > From: "Larry Higgins via Talk" > To: "WindowEyes List" > Cc: "Larry Higgins" > Sent: Monday, March 1, 2021 11:15 AM > Subject: JAWS and Eloquence > > > Listers, > > I know that this is a list devoted to our beloved Window-Eyes, and > die-hards like you and me, so excuse having to bring up the fish. > > As it is, I am an occasional user of said screen reader, but for me > there has been a major turnoff since the very first time I > attempted to befriend the thing . It goes as follows. And I > really hope that some of you have dealt with this issue successfully. > > It would seem that the folks who write the codes for JAWS have chosen to > muck with their version of the Eloquence synthesizer, and by doing so, > have messed up the pacing of it's delivery. > > The problem as I have experienced it is the matter of how Eloquence > manages sentences. Instead of an appropriate pausing between sentences, > JAWS Eloquence takes no pause at all for periods, but continues in a > kind of blue streak affect that doesn't give one even enough > time to digest the sentence as its own entity, you might say. > > I definitely prefer WE's pacing when it comes to sentences in > particular. I'm not talking about a pregnant pause between sentences > like you would get if you set it up to make such pauses, but a more > natural pause in the manner of the Window-Eyes presentation. > > > I hope this is all making sense, but it seems to me that some of you > Eloquence users might know just what I am talking about, and also how to > solve the problem. But who knows, maybe JAWS has simply created through > their own version of Eloquence this issue, > and that their is no solution at all other than a slight rewrite of > their code which I'm sure I would have to move heaven and earth to > convince them to do. > > Speaking of code, when I use my Code Factory Eloquence, the sentence > pacing is correct, but they have their speed settings such that it goes > a step either above or below my preferred reading level. > I don't consider myself to be a total slow-poke when it comes to > reading, though I like to set my reading speed at 41 when using > Window-Eyes, a leisurely pace for me, but I am not quite sure of the > exact speed that WE would indicate if they had been using Code Factory > as their default version of Eloquence. > > Anyway, if some kind user would please tell me if indeed there is or is > not a solution for this, and for me anyway, major issue, I would really > appreciate hearing from you. > > Unfortunately, I'm going to have to get serious about learning JAWS, as > my yearly subscription started in September of last year, but WE is > still working reasonably for the apps I most often use, though less and > less so it seems with each new update. But, I'm going to have to decide > if it is worth paying that annual subscription fee to maintain it, or > start focusing on NVDA or Narrator as my screen reader of choice. > > A big than
