Web audio api makes clicking sounds when playing either an oscillator or a sampled looped
Reported by
danhand...@hotmail.com,
Aug 9 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. create 2 oscillators 2. using a midi keyboard attach the notes of the keyboard to the oscilator 3. when your playing the keyboard sometimes and randomly you hear a clicking sound. What is the expected behavior? no clicking sounds when playing sounds What went wrong? I have checked on 3 differnt computers all using windows 10 and newsest version of chrome. I also have used the online synenzisers and online pianos to test to see if the problem is not with my code. the problem exsists in all the websites and the website im creating. if you would like to use the website im developing to recreate the problem you can. www.bnaturalmusicrepair.com:8087 Did this work before? Yes in the last version of chrome i did not have this problem Does this work in other browsers? N/A Chrome version: 60.0.3112.90 Channel: stable OS Version: 10.0 Flash Version:
,
Aug 9 2017
brajkumar@ Are there more steps than this? Using your steps, I hear no audio at all. When I press the "Use tuner" button, I do hear audio then. Pressing and holding a key does seem to cause some clickyness, but I can't tell if that's a bug in webaudio or the expected result since I don't really know what it should sound like. Also, danhandman@, this demo is so huge it's really hard to figure out what could be wrong. It would be really great if you create a smaller demo that shows the problem. Or maybe point out where all the code is that uses webaudio.
,
Aug 10 2017
OK I made a quick and easy program to show that problem it will just produce a sound and if you let it play for like 30 seconds you will hear the clicking random sounds. www.bnaturalmusicrepair.com:8094
,
Aug 10 2017
Thanks for the much simpler demo. It really helps a lot! I tried this on my Linux box running Chrome 61.0.3163.31. It took quite a while before I could hear any clicks. And only a few when I tried to open the menu (3 dots) to get the Chrome version. No more clicks after that. What kind of machine are you testing this on? (Although that shouldn't matter too much. A simple oscillator and gain node should run without glitching even on an ancient Galaxy Nexus.)
,
Aug 10 2017
Im runing a 2 core 2.7 amd 8g of ram and ssd its an acer travelmate. But it also does it on my surface 1 pro. After digging more into it it seems to happen when u have cpu activity like u said clicking on the dots made the disruption in sound. The weird thing is that this is a recent change it was not like this last month.
,
Aug 10 2017
Thanks for the info. Not sure what's going on. Definitely didn't click like this before with a simple oscillator. It's going to take some digging to figure out what's happening.
,
Aug 10 2017
Well at least im not crazy.
,
Aug 14 2017
> it seems to happen when u have cpu activity like u said clicking on the dots made the disruption in sound. Based on this comment, I suspect this might be a dupe of the issue 745898.
,
Aug 21 2017
Ok well I can't view issue 745898 so i'll just wait for it to be resolved. Thanks again
,
Aug 22 2017
I figured something out that might be helpful. In windows 10 the cpu is throttled back as the cpu usage drops and is throttled up as cpu usage increases. I noticed that when I make it so window 10 can not throttle the cpu and it keeps it at the same GHZ the clicking sounds practically don't happen. and when I let the cpu throttle it down the clicks happen very often. hopefully this will help
,
Jan 8 2018
Not much we can do if the OS throttles the CPU causing glitches.
,
Jan 18 2018
Ran this again on linux using www.bnaturalmusicrepair.com:8094 and Chrome 64.0.3282.99. Don't hear any glitches at all.
,
Jan 18 2018
No issues on win10 with Chrome 63 either. Can you retry with Chrome 63 or later?
,
Jan 21
(2 days ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by brajkumar@chromium.org
, Aug 9 2017Status: Untriaged (was: Unconfirmed)