- From: Raymond Toy <rtoy@google.com>
- Date: Wed, 12 May 2021 10:47:37 -0700
- To: "public-audio@w3.org Group" <public-audio@w3.org>, public-audio-comgp@w3.org
- Message-ID: <CAE3TgXFdv1ZrJWJRMkvu7X0HrV-zuaLsW8EJPwcT3euJrBQ0Aw@mail.gmail.com>
May 12Attendees Jeff Switzer, Jack Schaedler, Michel Buffa, Raymond Toy, Philippe Milot Minutes - 16:00-16:10 UTC (9:00-9:10 am PDT): Set up calls - 16:10-16:30 UTC (9:10-9:30 am PDT): NoiseGenerator <https://github.com/WebAudio/web-audio-api-v2/issues/8> - [Raymond briefly describes API] - Michel: What about colored noise? - Raymond: No support for that; there’s no generally accepted method for this that I could find. - Jeff: The output values are cross-browser equivalent? - Raymond: Yes, the node and RNG is specified so that you should get exactly the same output for the same seed and sequence for the uniform generator. The gaussian generator may produce different values because there are many many different ways to do that. - Michel: What is the actual use case? - Raymond: Don’t actually know other than the request. - Michel: See https://faustlibraries.grame.fr/libs/noises/ - Jeff: ruth posted this in slack: https://studio.rumyra.com/newnodes/ - Michel: Should specify the generator code? - Raymond: It’s pcg, but could be others like the one used in Javascript (xoroshiro) - Michel: Can we propose more? Colored noise; using your own generator. - Jack: In that case should this be in a worklet? - Raymond: We’re not opposed to adding more types; just need to have some well-known good methods for colored noise. - Michel: The Faust code has references to how to generate different types. - Raymond: Please propose new things since you have a lot of experience with this in Faust. - Michel: I’ll take a look again and propose something. - 16:30-17:00 UTC (9:30-10:00 am PDT): Automation with power law <https://github.com/WebAudio/web-audio-api-v2/issues/22> - Michel: Talking to people from the native audio world, no one will want to use AudioParams - Michel: Linked to a document containing a critique of AudioParams. - [Raymond: Document isn’t completely public, so no link to it here, but is available to WebAudio members. Please ask Michel if you want to see it.] - Jack: I understand the criticism but also understand the historical view. Things have changed a lot since the beginning of webaudio. - Jack: This is probably to fill a gap in what novice users see with plugins that have these kinds of wave shapes. This is useful for them. - Raymond: It’s relatively easy to add and the specification is straightforward. - 17:00-18:00 UTC (10:00-11:00 am PDT): playbackPosition property <https://github.com/WebAudio/web-audio-api-v2/issues/26> - Jack: I agree with Paul’s last comment. - Jeff: Yes, and I don’t agree with paulSlocum’s comment about using time. - Jeff: What else needs to be done? - Raymond: I think Paul’s proposal is pretty complete. Not much else needs to be done. - Jack: I think it would be great. - Raymond: Jack, do you have a need for this? - Jack: Most definitely. - Raymond: What do you do now then? - Jack: We compute the position ourselves using complicated formulas so not having to do that would be really nice. - Raymond: Ah, like what ChrisW says with his wubwub demo.
Received on Wednesday, 12 May 2021 17:48:04 UTC