Re: [webaudio] Nicely written and very instructive

Hi Roland,

Thanks for your findings! PR merged:
https://github.com/WebAudio/web-audio-api/pull/1783

Cheers,
Hongchan

On Wed, Oct 31, 2018 at 1:22 PM Roland Illig <roland.illig@gmx.de> wrote:

> Dear editors,
>
> I enjoyed reading through the specification at
> https://webaudio.github.io/web-audio-api/.
>
> It looks very carefully written to me. The abstract gives a clear
> overview, and I immediately understood what the specification is about,
> even though I'm lacking experience in audio processing.
>
> When I saw how the individual components (audio nodes, filters, inputs,
> outputs) work together and are connected, I just thought: Yep, that's
> how it should be designed.
>
> I was especially delighted to find many real-life applications and
> examples being mentioned in the normative text, which made it easy to
> understand how these components work together and what they are used
> for. This specification is well-suited as an introductory textbook to
> audio processing, which I know is not its primary goal, but it still
> succeeds at it.
>
> I found a few typos:
>
> "comiler" should be "compiler"
>
> In "also the CPU architecture (Arm vs. x86) also", ARM should be
> capitalized, and the "also" appears twice.
>
> "readilly" should be "readily"
>
> "users audio" should be "user's audio"
>
> "emulate emulate" should be a single "emulate"
>
> "No differently" should be "Not differently"
>
> Reading through the Security and Privacy Considerations was
> enlightening, it felt like a state-of-the-art summary of security
> research in audio processing. All attack vectors that I know are covered
> nicely.
>
> In summary, a big Thank You to all involved in creating this carefully
> designed specification. Keep up the excellent work.
>
> Best,
> Roland
>
>
>

-- 
Hongchan Choi, Ph.D.

Senior Software Engineer
Google Chrome

Received on Friday, 2 November 2018 16:31:43 UTC