W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: Behavior of source nodes on connect/disconnect

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 13 Sep 2013 12:53:32 -0700
Message-ID: <CAOp6jLY-RgU55pjFLMiNvsMmw8TDBfeUm+yVp+Av5t8PKWX-7g@mail.gmail.com>
To: Katelyn Gadd <kg@luminance.org>
Cc: Chris Wilson <cwilso@google.com>, Jer Noble <jer.noble@apple.com>, Raymond Toy <rtoy@google.com>, "public-audio@w3.org" <public-audio@w3.org>
One thing that bothers me about pausing nodes automatically when their last
output node goes away is that it reduces the modularity of audio subgraphs.
E.g. if you have an app that relies on auto-pausing a subgraph when it has
no outputs, and someone (maybe someone reusing your code) adds a
ScriptProcessorNode or MediaStreamAudioDestinationNode+MediaRecorder to tap
the output of the subgraph, suddenly things break. An explicit pause/resume
API would not have this problem. (I assume the output of paused nodes would
be treated as silence if they're still connected to outputs.)

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Friday, 13 September 2013 19:53:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC