Sukaritat
commented
1 year ago So this is not just me. What's worse, after much fiddling, late last night I had been able to get version 2.6 working in so far that it had always been able to recognize my voice, but with some random button pressing I could get the input that was written or transcribed in the "inbox" submitted or sent to Chatgpt for processing in other words a work around to the "send" problem that had crashed 2.6. But when I awoke this morning it just my luck that the Chrome store decided to approve 2.6.1 and that action made version 2.6.0 disappear. Now the only version available is 2.6.1 and as I wrote yesterday, and as a reviewer wrote today (6-5-23) on the Chrome Store review page, this new update no longer recognizes any voice commands. I know you just updated the app, but the problem your update was targeted to fix seems unrelated to the problem I am having and that Rully is having as well. I understand a fix may take time and not be so easy, but can you validate that the problem I and others are having getting any functioning voice recognition to happen a probable malfunction of a change made by Open ai and not a problem with a user's local settings. Thanks.
C-Nedelcu
nyngwang
kerkradio
I can't get 2.6.1 to work with my microphone despite all evidence showing that the mic is working. The extension has permission and the chrome browser shows that the page is using the mic. I will note that when installing the extension, I was not asked by the app for permission to use the microphone as your instructions on the home page instructed that I would be. When I go to the speech recognition test page to test the mic, everything works fine.
When I go back to using 2.6.0 I notice that the mic works, however nothing I do seems to allow me to "send" or "submit" any information that is entered into the chatgpt "in box" regardless of the input method (keyboard or voice). The long and short of it is that the 2.6 version will recognize the mic and pick up voice inputs, but won't allow the user to send the information to be processed, but version 2.6.1 for some reason will not activate the mic recognition.
I have only one clue which is when inspecting the chrome extension page, the 2.6.1 version shows an error. It appears on line 858 : const { set: valueSetter } = Object.getOwnPropertyDescriptor(element, 'value') || {}
It seems to have something to do with the Elevenlabs voice listings. I have never selected that option before in 2.6.0 or in 2.6.1. I should also tell you that I have uninstalled and reinstalled the (or I should say loaded or packed and unloaded or unpacked) the .6.1 extension several times, closed and reopened chrome several times and even rebooted and restarted my computer several times and continue to see the same behavior. I have keep the 2.6.0 extension installed throughout this experience, however all of my attempts to get 2.6.1 working properly have been done so with that version of the extension enabled and the 2.6.0 version of the extension disabled, except for one attempt during which, with the page closed, I enabled both versions in the chrome extension management settings page and then opened the chatgpt page. When I did so, the 2.6.0 version of Talk-to-Chatgpt was displayed showing itself to win-out in the battle for dominance between the two.
Question, in the chrome microphone permissions page, should I being seeing some indication of a permission that is specific to the Talk-to-Chatgpt extension as opposed to a permission that applies to all of chat.openai.com:443? The permission settings page lists that site as having 10 cookies associated with it, but doesn't give me any details about them. Similarly, somewhere else in the settings area that page/address is listed with an asterisk (https://chat.openai.com*) but still no further details are provided. Am I barking up the wrong tree thinking this has something to do with the permissions setting? I even tried to "reset" the permissions and start from scratch with the "install" to no avail. Help, I feel like Captain Picard yanked suddenly out of the Nexus.