Ok, so this is extremely strange. I've tested things again and it seems
like the speech sometimes is interrupted when moving to a new line in
the midle of a line but not always. It seems it is more likely to
interrupt the speech at the beginning of a line. So if I move between
two lines quicly it gets interrupted but if I wait a second the speech
will not be interrupted when I move to a new line.
It is difficult to know where this error originates, but we can at least
exclude some options.
I can send a brltty log-file if you just tell me what commandline flags
to send to brltty in order to get the write logfile.
I can also test to call functions on libespeak-ng.so. If you tell me
what functions brltty are using and in which order, I can test to call
them from python and see if the problem is still there.
Best regards,
Tage
On 12/5/2019 11:08 AM, Dave Mielke wrote:
[quoted lines by Tage Johansson on 2019/12/05 at 08:50 +0100]
How ever, then I found another problem. All speech messages are
enqueued. So
if I walk two lines quickly, brltty speaks the first line done
before it
starts to speak the second line. I have set "say line mode" to
immediate.
This is probably a bug and I would be very pleased if it could be
fixed.
Are you sure you're using the latest development code? I just tested
this and
the previous line is ineeed stopped before the next line is spoken.
Perhaps
this was a bug in an older release.
I ran the following:
$ make clean
$ git pull
$ ./configure --with-espeak=no
$ make
$ sudo ./run-brltty
Yes, that all looks good. When you run brltty, which version does it
say it's
running?
One thing I might add, though, is that, for the general case, it'd be
better
to do:
make distclean
git pull origin
./autogen
./configure
this matters the most when, for example, configure has been changed.
While this
doesn't happen that often, you never know when it will.
The problem is more precisely that the speech isn't interrupted when
I move
to a new line. The lines are not enqueued as I said before. For
example. Let
say brltty reads a very long line and I walk 10 lines away. Brltty
doesn't
stop to speak the first line until it is done, but when it is done
with the
first line, it will start to speak the current line I'm at and not
all lines
in between.
Yes, I understood that. So far, I've been unable to make that happen.
I edited
a large file with the line numbers showing, and, as I quickly scroled
through
it, I heard a bunch of truncated line numbers followed by the final
line fully
spoken.
Perhaps others can give this a try.
I expect brltty to interrupt the speech immediately when I move to a new
line.
Yes, I agree with you. That's certainly how it should be working.
It is very strange if this is different on different systems. Maybe it
is a problem in espeak-ng. I'm using espeak-ng 1.50.
I'm using 1.49.2.
I'm willing to help as much as possible to fix this problem because it is
very annoying.
And I sure do want to fix whatever the problem is.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty
