2018-05-17, 11:21
Thanks for sharing a fix to stop Kodi from listing the NVDA Controller as orphaned.
Problem is that NVDA still doesn't show up as a "Default TTs Engine" for the Kodi screenreader to use, as you already pointed out.
Just wish there was something that could be done to force Kodi v17.6 to use a voice other then the default MSAPI one (Think it's David.) Can a hack be created for enabling an option under the Kodi Screenreader CP listing all MSAPI voices currently installed under your copy of Windows? Then I could just select another one. Maybe tell the Kodi screenreader to use the default MSAPI voice set in the Windows settings -> Speech -> Text to Speech grouping instead? I'm using Windows 10 1803 by the way.
Wonder if this anoyance will be fixed in Kodi v18 Leia?
Problem is that NVDA still doesn't show up as a "Default TTs Engine" for the Kodi screenreader to use, as you already pointed out.
Just wish there was something that could be done to force Kodi v17.6 to use a voice other then the default MSAPI one (Think it's David.) Can a hack be created for enabling an option under the Kodi Screenreader CP listing all MSAPI voices currently installed under your copy of Windows? Then I could just select another one. Maybe tell the Kodi screenreader to use the default MSAPI voice set in the Windows settings -> Speech -> Text to Speech grouping instead? I'm using Windows 10 1803 by the way.
Wonder if this anoyance will be fixed in Kodi v18 Leia?