Closed bartman081523 closed 1 year ago
Thank you for your wonderful contribution! I will review and test, and if all is OK, I will post as 1.6.2. Many thanks for your help, and if you want to contribute further, I would be happy to share some of the next donations with you.
Many thanks for your help, and if you want to contribute further, I would be happy to share some of the next donations with you.
I will contribute what I can, thank you too.
The abrupt stopping of speechrec after 2-3 messages is gone, but now I have another error after ca. 7 speechrec messages.
content.js:99 Uncaught DOMException: Failed to execute 'start' on 'SpeechRecognition': recognition has already started. at CN_SayOutLoud (chrome-extension://apppenpkkmfffmkbfidchbmolggnohoj/content.js:99:30) at CN_CheckNewMessages (chrome-extension://apppenpkkmfffmkbfidchbmolggnohoj/content.js:504:5)
This error appears and then there is no speech rec possible anymore.
Many thanks for your help, and if you want to contribute further, I would be happy to share some of the next donations with you. I will contribute what I can, thank you too.
The abrupt stopping of speechrec after 2-3 messages is gone, but now I have another error after ca. 7 speechrec messages.
content.js:99 Uncaught DOMException: Failed to execute 'start' on 'SpeechRecognition': recognition has already started. at CN_SayOutLoud (chrome-extension://apppenpkkmfffmkbfidchbmolggnohoj/content.js:99:30) at CN_CheckNewMessages (chrome-extension://apppenpkkmfffmkbfidchbmolggnohoj/content.js:504:5)
This error appears and then there is no speech rec possible anymore.
You may want to use a try/catch block around the .start() call ? this would usually do the trick. Dirty but efficient
can you test the pr at this stage? for me the speech rec still works, after I tested 20 received speech recs.
I will do my best to try it soon but I can't today (busy at work) I usually do my Talk to ChatGPT work on weekends as it's a personal side project.
Take your time, my intenttion was not to hassle you. in the meantime I will implement and try with the catch/try block around the start() call. I will try to develop a fix for the speech rec stop and push to this patch-3 branch.
Hi, mine doest speak back at all - as in no voice just texts back
Hi, mine doest speak back at all - as in no voice just texts back
are you talking about changes made by @bartman081523 ? or just the standard v2.6.1 version?
Hi, mine doest speak back at all - as in no voice just texts back
are you talking about changes made by @bartman081523 ? or just the standard v2.6.1 version?
@C-Nedelcu please take your time until you review. I have no problem waiting a few weeks.
I have cloned from scratch with git clone -b patch-3 https://github.com/bartman081523/talk-to-chatgpt.git
and loaded the extension in chrome and it works like intended (for me).
Of course there is the message "Not starting SpeechRecognition because CN_IS_LISTENING is true" after every message, but this only catches another error, that I dont know how to patch, so that too works like intended. The speechrec is not stopping after ca. 3 received messages, but hears at least for 30 messages, here is the console log for 30 received messages:
I have reviewed the changes and they all look good. I am going to test for a while personally and then I will publish as v2.6.2 :)
Had a long discussion with ChatGPT and it worked great, seemed perfectly stable to me. Pushing v2.6.2 to the stores now. Thank you very much bartman081523 !
Fix erroneus Speechrec stop. Sometimes after reading the message, the Speechrec was stopping. Fix by GPT-4 (works for me, error is gone)