-
Notifications
You must be signed in to change notification settings - Fork 116
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
Uncaught TypeError in audio-processor.js #15
Comments
What browser are you using? Any chance you can try with Chrome? |
Thx for the quick response. Yes, I'm using chrome currently. |
If that can help, I have the same issue, Win11 PRO; OS: Win32, Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 |
For a quick fix you can apply - #17 (comment) |
also since it was mentioned in the other thread, here is my server output in case helpful:
|
The output looks good and the progress bar you see is the warmup stage of WhisperSpeech. Let me know if the workaround that I posted works for you. We are currently setting up a Windows machine to replicate the issue. |
Here's a video with that workaround. It seems to be working, except I don't hear any text to speech (probably not surprising considering the bug i worked around). but still.. progress! output.mp4 |
I can see in the console that the connection to |
Thanks! I went ahead and tried again, restarting everything. This time it did work. The audio was a bit more delayed than in your video, but it did all work. So presumably in my last test I just needed to either wait for a warm up or the 8888 port forwarding somehow didn't work. |
What GPU do you use? |
I’m on a 4090 and so was expecting it to be pretty snappy. As far as I can
tell the gpu is being utilized but it’s definitely not as responsive as in
your video.
…On Wed, Jan 31, 2024 at 8:49 PM Marcus Edel ***@***.***> wrote:
What GPU do you use?
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFLVAUES27KNB5IWXQAO23YRMND7AVCNFSM6AAAAABCQRZ3MCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRQGUYDOMBWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We are going to add latency outputs for each step to the demo tomorrow, so we compare it easier. The video was recorded on a 4090, so you should see very similar results. |
Nice - happy to help test those latency #'s when they're in.
…On Wed, Jan 31, 2024 at 9:32 PM Marcus Edel ***@***.***> wrote:
We are going to add latency outputs for each step to the demo tomorrow, so
we compare it easier. The video was recorded on a 4090, so you should see
very similar results.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFLVATALUTG3E3HUJZHMPDYRMSFHAVCNFSM6AAAAABCQRZ3MCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRQGU2DONBQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
i am using the same GPU on windows, did u use this command to run the docker:? |
Getting this. I'm trying to view the page on windows while running it in WSL. Everything else seems OK.
Uncaught TypeError: Cannot read properties of undefined (reading 'set')
at AudioStreamProcessor.process (audio-processor.js:24:23)
process @ audio-processor.js:24
The text was updated successfully, but these errors were encountered: