🎉 Thanks for opening this pull request! For guidance on contributing, check out ourcontributor guidelines and otherresources for contributors!
🤔 Please ensure that your PR links to an issue, which has been approved for work by a maintainer; otherwise, there might already be someone working on it, or still ongoing discussion about implementation. You are welcome to join the discussion in an Issue if you're not sure!
🌸 Once your PR is merged, be sure toadd yourself to thelist of contributors on the readme page !

Thank You!

Hi! A few things to note here:

• p5.sound.js, in this repo, is pulled in fromhttps://github.com/processing/p5.js-sound as part of the release process, so changes should go in that repo to not be overwritten.
• The legacy p5.sound.js is also no longer maintained; further updates will go in the new p5.sound library,https://github.com/processing/p5.sound.js. I'm not 100% sure what the status of bug fixes into the legacy p5.sound is,@ksen0 are we still making bug fixes into it or just leaving it as is?

Regarding the particular issue in question here, it actually looks like thishas been fixed in legacy p5.sound already, four years ago:processing/p5.js-sound#605

@ksen0 it looks like the version in p5.js has just never been updated since 1.0.1:

A test release 1.0.2 was madehttps://github.com/processing/p5.js-sound/releases/tag/v1.0.2 but it's not clear how extensively this was tested. I guess it never made its way out.@ksen0 not sure how risky you feel it is to do a legacy p5.sound update in a minor p5 1.11.x release. (As you can probably see@CharlieELweb, the mixed release process of p5 and p5.sound in 1.x is a little messy, and they have separate release schedules in 2.x to resolve some of that messiness.)

Thanks@davepagurek, just found that the official web editor of p5.js default version 1.11.8 has this problem so sent this pull request.

we appreciate you noticing the bug! the fact that it was fixed upstream but not actually released is still worth looking into, it's just that the fix is likely more to do with the release process than a code change 🙂