Chrome: GainNode.gain.value setter smoothing is deprecated and will be removed in January 2018

[kburke3]

TODO

• [*] Is this a question or bug? [Stack Overflow] This is a bug.

• [*] Did you search the issues to see if someone else has already reported your issue? If yes, please add more details if you have any!

• [*] If you're using an older version, have you tried the latest?

• [*] If you're requesting a new feature; provide as many details as you can. Why do you want this feature? Do you have ideas for how this feature should be implemented? Pseudocode is always welcome!

Issue Details

• Version used (Ex; 1.0): 1.0.0

• Describe whats happening (Include any relevant console errors, a Gist is preferred for longer errors): I'm getting this error in Chrome. [Deprecation] GainNode.gain.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See https://www.chromestatus.com/features/5287995770929152 for more details.

• OS & Browser version (Please be specific) (Ex; Windows 10 Home, Chrome 62.0.3202.94): Macos 10.12.6 Chrome 63.0.3239.84 (Official Build) (64-bit)

[gmtta]

I'm concerned about this as well. Hopefully this will be a fairly simple patch?

[owendwyer]

From reading this thread it seems it's not a big deal. Chrome is just going to start behaving the same way that Firefox already does.

GainNode.gain.value setting will still work, but it won't get the extra 'smoothing' that had been happening on Chrome.

From what I understand, changing volume suddenly can sometimes cause popping or cracking sounds. To counteract this, Chrome had/has a smoothing feature so that no change was ever too drastic. However, there may be some situations where it's better to not have smoothing at all, so Chrome are going to stop doing it.

[MaryLou9988]

The reported GitHub issue (288) discusses a deprecation warning in Chrome related to the GainNode.gain.value setter smoothing, slated for removal around January 2018. To resolve this, consider updating to the latest version of the library or tool causing the warning, checking for updates, and adjusting the code to use setTargetAtTime() as recommended. Keep an eye on the Chrome Status page for additional insights. Ensure compatibility with the latest browser versions and assess whether the library, like r2park, requires updates to align with recent browser changes.