New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The KMPlayer :a VideoPlayer maybe can help Nvda to read the Subtitles #3002
Comments
Comment 1 by k_kolev1985 on 2013-02-18 20:06 In what language are the subtitles loaded with the video? Because, if they are in a language not supported by the currently used TTS engine, they will be not read aloud (because the current TTS (voice) can't read them). Do they actually show on the screen? If not showing on the screen, they will not be read by the TTS engine. The toggle of showing/hiding subtitles is done via Alt+X while KMPlayer is in focus and if reading aloud of messages is turned on, you should here "Show subtitles". If you here "Hide subtitles" after pressing Alt+X, press it again. To select a diffrent TTS engine (voice), press F2 from within KMPlayer, tab twice to go to the tree-view of options categories, from there select "Subtitle processing" and if you here "collapsed", press right arrow to expand it. Then down arrow to the fourth item (i think it's called "Languages/TTS"), tab twice to go to the group of tabs (pages) of settings and press right arrow to select the tab "Text-To-Speech". Then tab a few times until you reach the first combo-box in this area. From within this combo-box, you can select from any SAPI5 voice that you have on your system to be used in KMPlayer for the reading aloud of subtitles and on-screen messages. The next 2 controls are sliders. The first one controls the voice speed, and the 2nd one - its volume. And yes - I think that thanks to its API, KMPlayer can be made to output the subtitles of a video to some other application (including NVDA). Actually, something similar has been done via an external application called "VoiSub". It takes the video subtitles from KMPlayer (Winamp is also supported) and gives them to the system default SAPI5 TTS engine (voice) or to the currently active screen reader. It supports NVDA as well. Here's the website from witch you can read more and download "VoiSub": |
Comment 2 by alyabani94 (in reply to comment 1) on 2013-02-19 00:06
|
Comment 3 by k_kolev1985 on 2013-02-19 07:38 Actually, in order for the subtitles to be read aloud, they have to be in text and not graphic format (in most cases - the external subtitles are in text (srt, sub, etc.) format). But in most cases, the embedded into the video subtitles are in graphic format and they can't be read. Use external (srt, sub, etc.) subtitles to make sure they will be read aloud. The video format doesn't matter. You've noticed that about MKV files, because most of the videos with embedded subtitles are MKV format. |
This sounds similar to the request in #2797 |
Hi, Two things: are there any updates to this, and can we contact the original poster? CC @k-kolev1985 |
cc: @nvdaes, @javidominguez |
Does anyone have any insights into the kmplayer bug introduced after version 3.7 that makes the TTS repeat? I can roll back to an earlier version but then some newer videos won't play. |
I cannot download the KM Player for Windows from the website. |
Reported by alyabani94 on 2013-02-18 12:36
Hello
i requested for a weak ago about supporting reading the subtitles on videoes with Nvda
i looked for a way that i can help you somehow to do it
i found a VideoPlayer called KMPlayer
http://www.kmpmedia.net/
maybe it will help Nvda to read the subtitles if you create an compatible or add an add-ons for it
because there are some options are interesting
on the Options menu
the options are
TTS: Read Subtitle but this option doesn't work when i activate it
TTS: Read Message when i activate this option the default speech of the Windows is speak it's the Sapi 5's speech
TTS: Read Title on Play Start it's the same thing with the TTS: Read Message
I hope this can help somehow to read the Subtitles with Nvda
and thanks
The text was updated successfully, but these errors were encountered: