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

Re: AudioBuffer channel read/write APIs

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 12 Sep 2013 08:56:31 -0700
Message-ID: <CAOp6jLa=7XYu55wfjDx_=K7VRwYNkO_bp+XCN8rEtSnnG4EmWw@mail.gmail.com>
To: Katelyn Gadd <kg@luminance.org>
Cc: Ehsan Akhgari <ehsan.akhgari@gmail.com>, Marcus Geelnard <mage@opera.com>, "public-audio@w3.org" <public-audio@w3.org>
On Thu, Sep 12, 2013 at 5:13 AM, K. Gadd <kg@luminance.org> wrote:

> Arguably no matter the terminology, start/offset are unclear when you have
> both a source and a destination. IMO either prefix the offset argument
> (sourceOffset, etc) or allow offsets to be specified for source and
> destination. Passing both source and destination offsets would make these
> APIs a lot more useful since they allow you to carve slices out of a much
> larger buffer, and there's already the length argument. If you just want
> people to use typed array views for that, probably take out the length
> argument and just use the length of the source array.

For most uses I could think of, starting at offset 0 of the array was fine.
How would an offset into the array make this much more useful?

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 Thursday, 12 September 2013 15:56:58 UTC

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