davidacm / NVDA-IBMTTS-Driver

This project is aimed at developing and maintaining the NVDA IBMTTS driver. IBMTTS is a synthesizer similar to Eloquence. Please send your ideas and contributions here!
GNU General Public License v2.0
56 stars 23 forks source link

Strange problem when using different profile with different synthesizer. #97

Open narayan-b-raikar opened 1 year ago

narayan-b-raikar commented 1 year ago

I am experiencing a strange problem when using IBM Eloquence TTS with another synthesizer. That is, I have set a different NVDA profile with a different synthesizer on my computer. Eg - I have set a profile with IBM TTS Eloquence synthesizer in file explorer, desktop etc., I have set a profile with espeak synthesizer in microsoft word and other word processing applications. When I switch from a profile with IBM eloquence synthesizer to a profile with Espeak synthesizer, Means - when I open any application with a profile set with Espeak synthesizer from a file explorer with a profile set with IBM TTS Eloquence, then NVDA does not respond properly. NVDA completely loses its focus. It is not possible to get the output log information from this. So I request you to find a solution to this problem as soon as possible. Thank you.

narayan-b-raikar commented 1 year ago

I am experiencing a strange problem when using IBM Eloquence TTS with another synthesizer. That is, I have set a different NVDA profile with a different synthesizer on my computer. Eg - I have set a profile with IBM TTS Eloquence synthesizer in file explorer, desktop etc., I have set a profile with espeak synthesizer in microsoft word and other word processing applications. When I switch from a profile with IBM eloquence synthesizer to a profile with Espeak synthesizer, Means - when I open any application with a profile set with Espeak synthesizer from a file explorer with a profile set with IBM TTS Eloquence, then NVDA does not respond properly. NVDA completely loses its focus. To gain back its focus, I have to restart NVDA. So that, It is not possible to get the output log information from this. So I request you to find a solution to this problem as soon as possible. Thank you.

davidacm commented 1 year ago

Hi @narayan-b-raikar, "as soon as possible don't mean immediately", this is a free software and I don't receive donations for it. Coding is not easy and I can't dedicate full time to it.

But I tried to replicate your issue and I was unable to do it. This issue is not present using NVDA in this computer.

Did you tried with other synths? E.G. by setting one core in file explorer and Espeak in word.

Can you set NVDA in debug mode and see if something is present in the log? To get the log of a previous session do this:

Press windows + r, and in the dialog write this:

%temp%\nvda-old.log

Press enter and the log should be opened with the notepad.

Also, please tell me the software versions of the programs involved. Windows version, NVDA version, and the editors version (like word or other) where you are experimenting this issue.

I tried the following steps:

  1. I created an automatic profile for word 2019 and I set it to use Espeak TTS.
  2. I set the general profile to IBMTTS.
  3. I opened a document in word, and a folder in explorer.
  4. I changed the focus between the file explorer and word. Nothing happened.

I tried by setting a profile for file explorer, too.

I tried with other aps, like vs code, excel, and notepad++.

narayan-b-raikar commented 1 year ago

Thank you for your quick reply. I apologise for using word "as soon as posible".

Actually, This problem doesn't happen always. It only happens when I try to open such application for the first time after opening windows. I will try to get log information And will send you very soon. Thank you.

narayan-b-raikar commented 1 year ago

Now I am sending Log information. nvda-old.log Note, I was also facing this problem in previous version of NVDA That is: NVDA V 2023.1.

davidacm commented 1 year ago

Hi @narayan-b-raikar, I don't see something related with IBMTTS in the log. But I see a possible cause in one of the lines of the log. I'm not sure, but I Uploaded here an experimental package to see if the issue is fixed. Please try with this version, disable the auto update feature to avoid automatic update to the current stable version.

I have some questions for you:

  1. can you try the following tests?
    • You have a lot of add-ons and some of them are causing errors. So, Try to get the issue with all other add-ons disabled.
    • Test if the issue occurs with another TTS, for example windows One Core and Espeak.
  2. Can you accurately describe the steps to generate the issue?
narayan-b-raikar commented 1 year ago

Thanks for your immediate reply. This problem only happens occasionally, but sometimes it reoccurs. So, it is not possible to know the exact cause of this problem. And I also reported this problem to NVDA developers that there must be some problem in NVDA Screen-reader, which may cause this problem. But they are also unable to know the exact cause of this problem. I will try this experimental build and will inform you regarding this issue.

Now I am trying to answer your question.

  1. can you try the following tests? ◦ You have a lot of add-ons and some of them are causing errors. So, try to get the issue with all other add-ons disabled. – Yes. I thought the same but cannot figure out which addon is causing this problem. And I also checked this by disabling all addons so many times. But the cause of this problem is not known. This problem appears since I updated NVDA to version 2023.1.

◦ Test if the issue occurs with another TTS, for example windows One Core and Espeak. – I have already checked with Sapi 5 synthesizer and Espeak. But I did not face such problem anywhere.

  1. Can you accurately describe the steps to generate the issue? - When you start the computer, then, open NVDA. Open Word or any other application from the Start menu which has profile set with different synthesizer from current IBM Eloquence synthesizer. That is it.

I will try to get log info about this issue by disabling All other addons. Thank you for giving your time for this problem. Regards.

narayan-b-raikar commented 1 year ago

I tried to download experimental build which you had uploaded. But, this link is not working. Can you provide this link again?

davidacm commented 1 year ago

Hi @narayan-b-raikar, the link is working properly. To download it, do the following steps:

  1. open the link.
  2. once the link is opened, press nvda + f2 to ignore the next key, release the keys, and then press the letter "s".
  3. the download should start, and you can see the file in the downloads folder.

I hope this works for you.

narayan-b-raikar commented 1 year ago

Okay thank you I downloaded successfully will check and inform you thank youfrom Dr narayan B RaikarOn 20-Jul-2023 12:38 pm, David CM @.***> wrote: Hi @narayan-b-raikar, the link is working properly. To download it, do the following steps: open the link.once the link is opened, press nvda + f2 to ignore the next key, release the keys, and then press the letter "s".the download should start, and you can see the file in the downloads folder. I hope this works for you.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

narayan-b-raikar commented 1 year ago

Hi, I am successfully Installed IBM TTS with eloquence. I have checked many times. But, there has been no problem so far. And also NVDA respond correctly now while switching varrious application which has different synthesizer, by Alt+Tab key. This was also one of the problem in previous build. Anyway, Thanks once again. I will try to let you know if any problem occurs in the future. Thank you for your immediate response and cooperation. regards.

narayan-b-raikar commented 6 months ago

Hi, Previously, I have mentioned the problem which has been faced while switching diferent application profile which has different synthosizer. That problem has been solved on temporery build. At that time, I thaught that This solution may not occur on next stable releases. But, after updating latest build, that is v 2023.12, I am facing same problem now. Can you solve this on next build?