-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Clicking/clipping and bad audio quality in demo. #60
Comments
Something changed with the way scriptprocessor work it seems - as the data is still being piped via the scriptprocessor API. But yes, I also noticed an extreme deprecation of audio quality with glitches and so-on over the past month, however it was working fine before. |
Same here |
maybe that's why // console log |
+1 |
@Kagami, can you take a look at this and point us the directions to solve / improve it? I'll be glad to submit a pull request. Also, can you confirm its related to "The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead" warning? |
+1 I have noticed that this issue seems to be more pronounced on Chrome for Windows. It also works significantly better in Chrome Canary, so maybe there is a fix coming to Chrome soon? |
Has anybody found a fix or workaround for this? |
Any updates on this? |
i have the same problem, but for me the problem occur when i receive notification in my machine in the same time that i am recording the audio, with this my voice is bad... I don't know if this can be resolved. |
I suspect this will never be fixed. We ended up sending audio files to the cloud to be converted. |
Recently I've started to notice extremely low quality audio, including clicking/clipping in both the version of vmsg I'm using as well as the online demo. I thought it was my mic but I tried it on multiple computers/phones, and also recorded the audio using Audacity and in audacity it comes back free of any artifacts. Has anyone else noticed this?
The text was updated successfully, but these errors were encountered: