View Single Post
Old 12-14-2020, 04:30 PM   #19
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by Uncle Robin View Post
That's right, as I said: "They were not showing up in my Calibre list when I posted these screenshots two days ago, then they appeared" (e.a.) That's why it's weird, I have no idea where they came from.

EDIT:

Here's the relevant entry from the json

tts_sapi": {
"rate": 2,
"voice": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\ Voices\\Tokens\\ScanSoftTom_Dri20_22kHz"

As expected, the problem is that Calibre viewer's Read Aloud is lookng for a key that isn't there, and never was. Can I just delete that entry from the json to force Calibre to ask me to choose one?
I don't know whether it's safe to delete the whole "tts_sapi" entry but there's no reason why you couldn't change the entry to:
Code:
"tts_sapi": {},
i.e. remove the content between the curly brackets {}.
jackie_w is offline   Reply With Quote