I think a feature addition should be proposed together with a clear use case, which would take the form of a snippet of code, and/or an paragraph explaining why either this new feature makes authors's life easier, or the use-case is simply impossible to achieve using today's Web Audio. I believe this be better for the group, enabling a sane discussion: not everybody in this group is familiar with some specific point of signal processing and such, and I thing having a set of use case would yield a more appropriate API, in some cases, while keeping the barrier to entry low for new feature proposal. Also, we should really discuss what should be the scope of a so-called v1 in a call. --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/pull/262#issuecomment-26796613
Received on Tuesday, 22 October 2013 11:57:53 UTC