You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -168,11 +168,10 @@ in Visual Studio.
168
168
169
169
## Known problems
170
170
171
-
After using the read-aloud function for about 20 pages, you will hear a crackling in the audio output.
171
+
Using Windows 7, after using the read-aloud function for about 20 pages, you will hear a crackling in the audio output.
172
172
This is due to a memory leak that is known to Microsoft since the year 2010. (Congratulations, Microsoft!).
173
173
See for instance [this post](https://social.microsoft.com/Forums/en-US/ee7bd34f-20c2-4a75-9d5a-a0c5e7f1a9b2/memory-leak-with-speechsynthesizer-please-help?forum=Offtopic) and [this post](https://stackoverflow.com/questions/10707187/memory-leak-in-net-speech-synthesizer).
174
174
Stopping and restarting speech will not help. Instead, you need to close LediReader and
175
175
open it again.
176
176
177
-
I'm working on this problem now, and try to use Windows 10 speech synthesis directly, using the
178
-
Windows 10 UWP APIs. This will of course only get rid of the problem under Windows 10.
177
+
With Windows 10, this problem has disappeared, since the speech synthesis uses the Windows 10 UWP API.
0 commit comments