mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/dom/webidl/AudioBuffer.webidl

39 строки
1.2 KiB
Plaintext
Исходник Обычный вид История

Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
/* -*- Mode: IDL; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this file,
* You can obtain one at http://mozilla.org/MPL/2.0/.
*
* The origin of this IDL file is
Bug 1282820 - Change the specification URL in webidl files for the Web Audio API. DONTBUILD. r=smaug This patch has been written with this command, ran from the root of the tree: ``` gsed -i 's!https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html!https://webaudio.github.io/web-audio-api/!' dom/webidl/* ```
2016-06-29 12:30:13 +03:00
* https://webaudio.github.io/web-audio-api/
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
*
* Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C
* liability, trademark and document use rules apply.
*/
Bug 1322883 - AudioNode constructors - part 15 - AudioBuffer, r=padenot
2016-12-15 21:24:42 +03:00
dictionary AudioBufferOptions {
unsigned long numberOfChannels = 1;
required unsigned long length;
Bug 1329744 - AudioBuffer ctor updated, r=padenot
2017-01-11 00:30:28 +03:00
required float sampleRate;
Bug 1322883 - AudioNode constructors - part 15 - AudioBuffer, r=padenot
2016-12-15 21:24:42 +03:00
};
[Pref="dom.webaudio.enabled",
Bug 1329744 - AudioBuffer ctor updated, r=padenot
2017-01-11 00:30:28 +03:00
Constructor(AudioBufferOptions options)]
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
interface AudioBuffer {
readonly attribute float sampleRate;
Bug 1265400 - Use unsigned long for AudioBuffer length and numberOfChannels; r=smaug MozReview-Commit-ID: 47ZDDvj5QrA --HG-- extra : rebase_source : 2c441c7d04ec84eeec526a9a93607ffcac263617
2016-04-20 19:32:17 +03:00
readonly attribute unsigned long length;
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
// in seconds
Bug 813269 - Use double to represent time in Web Audio; r=bzbarsky
2012-11-20 00:52:29 +04:00
readonly attribute double duration;
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
Bug 1265400 - Use unsigned long for AudioBuffer length and numberOfChannels; r=smaug MozReview-Commit-ID: 47ZDDvj5QrA --HG-- extra : rebase_source : 2c441c7d04ec84eeec526a9a93607ffcac263617
2016-04-20 19:32:17 +03:00
readonly attribute unsigned long numberOfChannels;
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
[Throws]
Float32Array getChannelData(unsigned long channel);
Bug 915524 - Implement AudioBuffer.copyFromChannel and AudioBuffer.copyToChannel; r=roc
2013-09-17 15:30:32 +04:00
[Throws]
void copyFromChannel(Float32Array destination, long channelNumber, optional unsigned long startInChannel = 0);
[Throws]
void copyToChannel(Float32Array source, long channelNumber, optional unsigned long startInChannel = 0);
Bug 793294 - Implement AudioBuffer; r=bzbarsky,smaug This is the full implementation of the AudioBuffer object. There are two ways to create these objects from an audio context and this patch implements only one of them. The construction of the AudioBuffer object is a two step process: the object should be created with operator new first, and then InitializeBuffers should be called on it. InitializeBuffers is fallible, because it uses the JS API to create the underlying typed arrays, but that's fine, since the length of the buffers comes from web content, and we don't want to use infallible allocations for those anyways. We hold on to the JS objects from the C++ implementation, and trace through all of those objects, so that a GC does not kill those object without us knowing. The buffer should be possible to manipulate from both C++ and JS, and the C++ object probably needs to support a set of methods for the C++ callers at some point.
2012-09-22 02:42:14 +04:00
};