Samuel Thibault schrieb am 15.01.2017, 15:36 +0100:
>Eric Scheibler, on Fri 13 Jan 2017 13:04:24 +0100, wrote:
>> I'am not absolutely sure about that. Could you upload a new version with a
>> default value of 20 or
>> even 10 ms just for testing purposes?
>
>I
Samuel Thibault schrieb am 12.01.2017, 3:50 +0100:
>Samuel Thibault, on Thu 12 Jan 2017 03:27:24 +0100, wrote:
>> I'm very surprised to see this 200 value, which means 200ms, while
>> studies have shown that "interactivity" is usually seen bad by humans
>> beyond 100ms.
>>
>> One thing we can do
Samuel Thibault schrieb am 10.01.2017, 22:18 +0100:
>Eric Scheibler, on Sun 08 Jan 2017 09:05:09 +0100, wrote:
>> 1. The monotonous speech output persists.
>
>I dug a bit and found the issue, reported upstream, and have uploaded a fixed
>version.
Confirmed.
>> 2. Th
Samuel Thibault schrieb am 08.01.2017, 0:21 +0100:
>Could you try the latest version, 1.49.0+dfsg-4?
I've removed the old espeak packages entirely and installed espeak-ng,
espeak-ng-data:amd64,
espeak-ng-espeak and libespeak-ng1:amd64 all in version 1.49.0+dfsg-4.
Unchanged:
1. The monotonous
Hello Samuel,
Samuel Thibault schrieb am 02.01.2017, 20:56 +0100:
>Can you please test with the latest version libespeak-ng, 1.49.0+dfsg-3?
Same problem.
First I've updated espeak-ng, espeak-ng-data and libespeak-ng1 to version
1.49.0+dfsg-3 (unstable).
Then I started brltty from the testing r
Control: reassign 848016 brltty-espeak
I still can confirm these issues (Debian testing, Brltty 5.4-3 and
brltty-espeak 5.4-3). They also
occur after a fresh installation of Debian testing (minimal installation).
Especially the speech
delay is a serious problem and should be addressed before t
6 matches
Mail list logo