Bug 779297 (webaudio)

Implement and ship Web Audio

RESOLVED FIXED in mozilla25

Status

()

defect
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: roc, Assigned: Ehsan)

Tracking

(Depends on 1 bug, Blocks 2 bugs, {feature, meta})

Trunk
mozilla25
Points:
---
849636, 775302, 779715, 788310, 792263, 792646, 792649, 797150, 802192, 803392, 804387, 807171, 807526, 807533, 808374, 808841, 808876, 809271, 809654, 809882, 811369, 811555, 811864, 812390, 812617, 813269, 814789, 815492, 815643, 816828, 822803, 827541, 833631, 834513, 834869, 834929, 836072, 836076, 836599, 837684, 845960, 846329, 847481, 848651, 848652, 848954, 849230, 849652, 849713, 849914, 849916, 849918, 850970, 851338, 851412, 851603, 851949, 851966, 851986, 852011, 852366, 852410, 852817, 852838, 853076, 853246, 853298, 853360, 853434, 853551, 853718, 853721, 853963, 854319, 854336, 854741, 855568, 855990, 856327, 856328, 856329, 856361, 856771, 857302, 857610, 857790, 857793, 859335, 859594, 859595, 859597, 859600, 859602, 861021, 861187, 861371, 861591, 862088, 862177, 863918, 863923, 864083, 864086, 864091, 864164, 864171, 864351, 864605, 864606, 864609, 864613, 864709, 864937, 865004, 865231, 865233, 865234, 865239, 865241, 865242, 865244, 865246, 865247, 865248, 865251, oscillatornode, 865256, 865257, 865261, 865413, 865532, 865548, 865550, 865553, 865642, 865650, 866079, 866108, 866141, 866433, 866434, 866442, 866570, 866737, 866839, 867086, 867089, 867104, 867174, 867203, 867324, 867511, 867588, 867876, 868116, 868305, 868409, 868485, 868504, 868776, 868855, 868864, 869224, 869257, 869682, 869684, 870065, 870167, 870174, 871201, 871577, 872394, 872635, 873335, 873553, 873858, 874024, 874508, 874540, 874869, 874915, 874934, 874952, 875144, 875152, 875221, 875277, 875402, 875529, 875596, 875617, 875911, 876024, 876118, 876207, 876215, 876249, 876252, 876273, 876338, 876834, 877039, 877125, 877231, 877523, 877527, 877662, 877695, 877820, 878014, 878015, 878328, 878407, 878478, 878497, 878875, 879014, 880129, 880202, 880265, 880342, 880384, 880404, 880724, 881092, 881558, 881587, 881959, 882171, 882543, 882956, 883010, 883011, 883591, 883844, 884459, 884632, 885496, 885505, 885956, 886165, 886168, 886381, 886618, 886787, 889016, 889042, 890023, 890072, 890369, 890371, 891254, 895196, 898962, 904302, 904707, 905444, 906966, 907758, 907986, 910171, 912474, 913854, 914030, 915524, 918217, 920987, 921457, 921695, 922639, 923058, 923106, 923319, 924286, 924288, 925619, 932621, 956489, 1020370
Dependency tree / graph
Bug Flags:
sec-review +

Firefox Tracking Flags

(relnote-firefox 25+)

Details

(Whiteboard: [games:p1][tech-p1], )

Assignee

Updated

7 years ago
Alias: webaudio

Comment 1

7 years ago
I have created a MozillaWiki article for the W3C Web Audio API: https://wiki.mozilla.org/Web_Audio_API
Assignee

Updated

7 years ago
Depends on: 788310
Whiteboard: [games:p?]
Whiteboard: [games:p?] → [games:p1]
All the child bugs here are fixed. What's the status of this API implementation?
OS: Windows 7 → All
Hardware: x86_64 → All
Assignee

Comment 3

7 years ago
(In reply to comment #2)
> All the child bugs here are fixed. What's the status of this API
> implementation?

It's long ways away.  Not all of the actual portions have been filed now.  I've been mostly filing bugs for things that I have in-flight patches for.
Assignee

Updated

7 years ago
Depends on: 792263
Assignee

Updated

7 years ago
Depends on: 792646
Assignee

Updated

7 years ago
Depends on: 792649
Assignee

Updated

7 years ago
Depends on: 797150
Assignee

Updated

7 years ago
Depends on: 802192
Assignee

Updated

7 years ago
Depends on: 803392
Assignee

Updated

7 years ago
Depends on: 804387
Assignee

Updated

7 years ago
Depends on: 807171
Assignee

Updated

7 years ago
Depends on: 807526
Assignee

Updated

7 years ago
Depends on: 807533

Updated

7 years ago
Depends on: 808374
Assignee

Updated

7 years ago
Depends on: 808841
Assignee

Updated

7 years ago
Depends on: 808876
Assignee

Updated

7 years ago
Depends on: 809271
Assignee

Updated

7 years ago
Depends on: 809654
Keywords: meta
Assignee

Updated

7 years ago
Depends on: 809882
Assignee

Updated

7 years ago
Depends on: 811369

Comment 4

7 years ago
Just wondering... but when will this be avaliable for Firefox users?
Assignee

Updated

7 years ago
Depends on: 811555
(In reply to Jessica_XY from comment #4)
> Just wondering... but when will this be avaliable for Firefox users?

There's no particular target set at this point. Sometime next year, probably.
Assignee

Comment 6

7 years ago
(In reply to comment #4)
> Just wondering... but when will this be avaliable for Firefox users?

We're working on it, it's still not clear which version will enable this by default.
Assignee

Updated

7 years ago
Depends on: 811864

Updated

7 years ago
Depends on: 812390
Assignee

Updated

7 years ago
Depends on: 812617
Assignee

Updated

7 years ago
Depends on: 813269
Assignee

Updated

7 years ago
Depends on: 814789
Assignee

Updated

7 years ago
Depends on: 815492
Assignee

Updated

7 years ago
Depends on: 815643
Assignee

Updated

7 years ago
Depends on: 816828
Assignee

Updated

7 years ago
Depends on: 822803
Assignee

Updated

7 years ago
Depends on: 827541
Assignee

Updated

6 years ago
Depends on: 833631
Assignee

Updated

6 years ago
Depends on: 834513
Assignee

Updated

6 years ago
Depends on: 834869
Assignee

Updated

6 years ago
Depends on: 834929
Assignee

Updated

6 years ago
Depends on: 836072
Assignee

Updated

6 years ago
Depends on: 836076
Assignee

Updated

6 years ago
Depends on: 836599
Depends on: 837684
Major content use case and needed for competitive parity.
Whiteboard: [games:p1] → [games:p1][tech-p1]
Assignee

Comment 9

6 years ago
(In reply to comment #8)
> Major content use case and needed for competitive parity.

Do we have a detailed set of requirements for b2g?  Web Audio is a huge API and we're currently working to determine the list of nodes we're going to implement first.  The proposed list is currently available at <https://etherpad.mozilla.org/webaudio> and it would be great if b2g folks could give us feedback on the prioritization proposed there.  Thanks!
Assignee

Updated

6 years ago
Depends on: 845960
The two use cases I know are very simple.  I'm not an expert on this, so I'm going to wave my hands
 - multi-shot API for playing back sounds (bug 674080).  I don't know how this overlaps with WebAudio, or what nodes that would correspond to.

 - generating infinite sine-wave tones, mixing two tones into one channel, and applying ADSR.  This is used to generate key-pad tones.

Beyond that, b2g is shooting for parity with android audio processing APIs, so that's the next place I would look.
In b2g, Music and Videp apps can use WebAudio. The apps can play music with audio effect.
Assignee

Comment 12

6 years ago
(In reply to comment #10)
> The two use cases I know are very simple.  I'm not an expert on this, so I'm
> going to wave my hands
>  - multi-shot API for playing back sounds (bug 674080).  I don't know how this
> overlaps with WebAudio, or what nodes that would correspond to.

In Web Audio you can decode the audio in a buffer and play it as many times as you like.

>  - generating infinite sine-wave tones, mixing two tones into one channel, and
> applying ADSR.  This is used to generate key-pad tones.

Web Audio lets you do that but I think doing that in software for the key-pad tones is a mistake.  We can just record the audio and play it back from a file.

> Beyond that, b2g is shooting for parity with android audio processing APIs, so
> that's the next place I would look.

Which APIs are those exactly?  I'm not familiar with Android audio APIs at all.
Assignee

Comment 13

6 years ago
(In reply to comment #11)
> In b2g, Music and Videp apps can use WebAudio. The apps can play music with
> audio effect.

What types of effects?
(In reply to :Ehsan Akhgari from comment #12)
> >  - generating infinite sine-wave tones, mixing two tones into one channel, and
> > applying ADSR.  This is used to generate key-pad tones.
> 
> Web Audio lets you do that but I think doing that in software for the
> key-pad tones is a mistake.  We can just record the audio and play it back
> from a file.

If this is for user feedback, you shouldn't use real DTMF tones in the first place. In e.g., WebRTC, the real DTMF data is conveyed in RFC 4733 RTP packets and any tones that are played are just candidates for double-detection and other confusion on the receiving end. So you could even use the same file for every key.

Updated

6 years ago
Depends on: 846329
Yes, the tones are audio played for user feedback, not what's sent over the wire.  I'll have to let the authors of the current code speak to the issues they ran into.
Assignee

Updated

6 years ago
Depends on: 847481
Assignee

Updated

6 years ago
Depends on: 848651
Assignee

Updated

6 years ago
Depends on: 848652
Assignee

Updated

6 years ago
Depends on: 848953
Assignee

Updated

6 years ago
Depends on: 848954
Assignee

Updated

6 years ago
No longer depends on: 848953
Assignee

Updated

6 years ago
Depends on: 849230
Assignee

Updated

6 years ago
Depends on: 849636
Assignee

Updated

6 years ago
Depends on: 849652
Assignee

Updated

6 years ago
Depends on: 849713
Assignee

Updated

6 years ago
Depends on: 849914
Assignee

Updated

6 years ago
Depends on: 849916
Assignee

Updated

6 years ago
Depends on: 849918
Assignee

Updated

6 years ago
Depends on: 850970
Assignee

Updated

6 years ago
Depends on: 851338
Assignee

Updated

6 years ago
Depends on: 851412
Assignee

Updated

6 years ago
Depends on: 851603

Comment 16

6 years ago
I was trying this code snippet with FF Nightly https://gist.github.com/automata/5174277 but I'm getting an error about the number of arguments for mozAudioContext.createBuffer.

Beside this, is anyone working on testing currently Web Audio API spec with the one implemented on FF? Any plans on how to do that? I want to help.

Thanks guys.
Assignee

Updated

6 years ago
Depends on: 851949
Assignee

Comment 17

6 years ago
(In reply to Vilson Vieira from comment #16)
> I was trying this code snippet with FF Nightly
> https://gist.github.com/automata/5174277 but I'm getting an error about the
> number of arguments for mozAudioContext.createBuffer.

There are two versions of createBuffer, one which just creates a buffer and one that decodes audio on the main thread.  You're trying to use the second version which we have not implemented yet.  Bug 848652 is on file for that. In the mean time, you can rework your sample to use the asynchronous version of this API, decodeAudioData which we implement and is better since it won't block the main thread any way.

> Beside this, is anyone working on testing currently Web Audio API spec with
> the one implemented on FF? Any plans on how to do that? I want to help.

I am actively involved in the spec discussions.  What kinds of things are you interested to help with?  I'm sure we could use more hands here.  :-)
Assignee

Updated

6 years ago
Depends on: 851966
Assignee

Updated

6 years ago
Depends on: 851986
Assignee

Updated

6 years ago
Depends on: 852011

Comment 18

6 years ago
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #17) 
> There are two versions of createBuffer, one which just creates a buffer and
> one that decodes audio on the main thread.  You're trying to use the second
> version which we have not implemented yet.  Bug 848652 is on file for that.

Ehsan, thank you, I'll try decodeAudioData instead.

> I am actively involved in the spec discussions.  What kinds of things are
> you interested to help with?  I'm sure we could use more hands here.  :-)

I can help testing the Web Audio API implementation (I don't know what is the best way to do that, maybe trying available examples like http://chromium.googlecode.com/svn/trunk/samples/audio/index.html and reporting the status?) and try to help on dev as much as I can. Well, use my hands :-)
Assignee

Comment 19

6 years ago
(In reply to comment #18)
> > I am actively involved in the spec discussions.  What kinds of things are
> > you interested to help with?  I'm sure we could use more hands here.  :-)
> 
> I can help testing the Web Audio API implementation (I don't know what is the
> best way to do that, maybe trying available examples like
> http://chromium.googlecode.com/svn/trunk/samples/audio/index.html and reporting
> the status?) and try to help on dev as much as I can. Well, use my hands :-)

Testing the existing Web IDL implementation will be a _huge_ help!  Note that at this stage there are large parts of the Web Audio APIs that we don't implement yet.  Unfortunately the best way to tell what has been implemented so far is to look in <http://mxr.mozilla.org/mozilla-central/source/dom/webidl/> for files named like [interfaceName].webIDL (for example, <http://mxr.mozilla.org/mozilla-central/source/dom/webidl/AudioContext.webidl>) and look at the properties and methods on those interfaces.  Reporting issues caused by things which we are not implementing yet is generally not very helpful since we're already well aware of those, but reporting issues with the things that we currently implement is extremely helpful (bug 846329 is my favorite example so far!)

As far as different node types, we have the DOM bindings implemented for a whole bunch of them, but most are not hooked up to anything yet.  The node types that are currently implemented and should work fine are AudioBufferSourceNode, AudioDestinationNode and AudioGainNode.  More is coming along shortly, of course, so please continue watching this bug.  :-)

If you're interested in hacking on the implementation itself and have experience writing C++ code, please let me know and I would be happy to help you find a good place to start!  And please ask questions if anything is not clear to you.  Thanks!
Assignee

Updated

6 years ago
Depends on: 852366
Assignee

Updated

6 years ago
Depends on: 852410
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #19)
> (In reply to comment #18)
> > > I am actively involved in the spec discussions.  What kinds of things are
> > > you interested to help with?  I'm sure we could use more hands here.  :-)
> > 
> > I can help testing the Web Audio API implementation (I don't know what is the
> > best way to do that, maybe trying available examples like
> > http://chromium.googlecode.com/svn/trunk/samples/audio/index.html and reporting
> > the status?) and try to help on dev as much as I can. Well, use my hands :-)
> 
> Testing the existing Web IDL implementation will be a _huge_ help!  Note
> that at this stage there are large parts of the Web Audio APIs that we don't
> implement yet.  Unfortunately the best way to tell what has been implemented
> so far is to look in
> <http://mxr.mozilla.org/mozilla-central/source/dom/webidl/> for files named
> like [interfaceName].webIDL (for example,

Are there no mochitests for these APIs? I looked in dom/tests/mochitest/ and could not find anything related to audio.
(In reply to David Dahl :ddahl from comment #20)
> Are there no mochitests for these APIs? I looked in dom/tests/mochitest/ and
> could not find anything related to audio.

content/media/webaudio/test/
Assignee

Comment 22

6 years ago
(In reply to comment #20)
> > Testing the existing Web IDL implementation will be a _huge_ help!  Note
> > that at this stage there are large parts of the Web Audio APIs that we don't
> > implement yet.  Unfortunately the best way to tell what has been implemented
> > so far is to look in
> > <http://mxr.mozilla.org/mozilla-central/source/dom/webidl/> for files named
> > like [interfaceName].webIDL (for example,
> 
> Are there no mochitests for these APIs? I looked in dom/tests/mochitest/ and
> could not find anything related to audio.

There are some tests in content/media/webaudio/tests, but we don't have an implementation for ScriptPrpcessoprNode yet, which means that we can't write any interesting tests for now (tests that actually see what the audio graph is outputting.)  I plan on working on ScriptProcessorNode very soon.
Assignee

Updated

6 years ago
Depends on: 853076

Comment 23

6 years ago
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #19)
> Testing the existing Web IDL implementation will be a _huge_ help!  ...

Ehsan, I am starting to test the IDL implementations. My initial attempt is at https://github.com/automata/webaudio-tests

Currently I am getting: TypeError: context.decodeAudioData is not a function. But looking at AudioContext.webidl, decodeAudioData was implemented. Any suggestions?

BTW maybe this discussion could be more appropriate by IRC/email, so just tell me. I am automata at #media or I can mail you.

> If you're interested in hacking on the implementation itself and have
> experience writing C++ code, please let me know and I would be happy to help
> you find a good place to start!  And please ask questions if anything is not
> clear to you.  Thanks!

I don't have enough experience writing C++ but I can give a try! Thank you!
Assignee

Updated

6 years ago
Depends on: 853246
Assignee

Updated

6 years ago
Depends on: 852817
Assignee

Updated

6 years ago
Depends on: 852838
Assignee

Updated

6 years ago
Depends on: 853298

Comment 24

6 years ago
I could get context.decodeAudioData to work with ogg files, while it fails to decode wav audio.

(In reply to Vilson Vieira from comment #23)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #19)
> > Testing the existing Web IDL implementation will be a _huge_ help!  ...
> 
> Ehsan, I am starting to test the IDL implementations. My initial attempt is
> at https://github.com/automata/webaudio-tests
> 
> Currently I am getting: TypeError: context.decodeAudioData is not a
> function. But looking at AudioContext.webidl, decodeAudioData was
> implemented. Any suggestions?
> 
> BTW maybe this discussion could be more appropriate by IRC/email, so just
> tell me. I am automata at #media or I can mail you.
> 
> > If you're interested in hacking on the implementation itself and have
> > experience writing C++ code, please let me know and I would be happy to help
> > you find a good place to start!  And please ask questions if anything is not
> > clear to you.  Thanks!
> 
> I don't have enough experience writing C++ but I can give a try! Thank you!
boblemarin, if you can give us a testcase (i.e. a page where you can observe the failure to use decodeAudioData on a .wav file), we could fix it faster, I think.
Flags: needinfo?(emeric)

Comment 26

6 years ago
Ooops. My bad, OGG and WAV decoding are working perfectly.
(test case here : http://minimal.be/mozilla/decode/ )
Flags: needinfo?(emeric)

Comment 27

6 years ago
Remember to use FirefoxNightly for your tests. The Live channel features a mozAudioContext object that is not functional, but the Nightly channel uses the unprefixed version which has the decodeAudioData method working.
(See my example here: http://minimal.be/mozilla/decode/ )

(In reply to Vilson Vieira from comment #23)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #19)
> > Testing the existing Web IDL implementation will be a _huge_ help!  ...
> 
> Ehsan, I am starting to test the IDL implementations. My initial attempt is
> at https://github.com/automata/webaudio-tests
> 
> Currently I am getting: TypeError: context.decodeAudioData is not a
> function. But looking at AudioContext.webidl, decodeAudioData was
> implemented. Any suggestions?
> 
> BTW maybe this discussion could be more appropriate by IRC/email, so just
> tell me. I am automata at #media or I can mail you.
> 
> > If you're interested in hacking on the implementation itself and have
> > experience writing C++ code, please let me know and I would be happy to help
> > you find a good place to start!  And please ask questions if anything is not
> > clear to you.  Thanks!
> 
> I don't have enough experience writing C++ but I can give a try! Thank you!
Assignee

Updated

6 years ago
Depends on: 853718
Assignee

Updated

6 years ago
Depends on: 853721
(In reply to boblemarin from comment #26)
> Ooops. My bad, OGG and WAV decoding are working perfectly.
> (test case here : http://minimal.be/mozilla/decode/ )

This causes https://crash-stats.mozilla.com/report/pending/cfed53a0-f354-438e-8788-00b2c2130322 for me after a few presses of the ‘play ogg’ or ‘play wav’
(In reply to John Drinkwater (:beta) from comment #28)
> (In reply to boblemarin from comment #26)
> > Ooops. My bad, OGG and WAV decoding are working perfectly.
> > (test case here : http://minimal.be/mozilla/decode/ )
> 
> This causes
> https://crash-stats.mozilla.com/report/pending/cfed53a0-f354-438e-8788-
> 00b2c2130322 for me after a few presses of the ‘play ogg’ or ‘play wav’

Filed Bug 853434 yesterday already about that one.
(In reply to XtC4UaLL [:xtc4uall] from comment #29)
> Filed Bug 853434 yesterday already about that one.

ta
Assignee

Updated

6 years ago
Depends on: 853434
Assignee

Updated

6 years ago
Depends on: 853963
Assignee

Updated

6 years ago
Depends on: 854336
Assignee

Updated

6 years ago
Depends on: 854741
Depends on: 855568
Assignee

Updated

6 years ago
Depends on: 856327
Assignee

Updated

6 years ago
Depends on: 856328
Assignee

Updated

6 years ago
Depends on: 856329
Assignee

Updated

6 years ago
Depends on: 855990
Assignee

Updated

6 years ago
Depends on: 856361
Assignee

Updated

6 years ago
Depends on: 856771
Assignee

Updated

6 years ago
Depends on: 857302
Assignee

Updated

6 years ago
Depends on: 857610
Assignee

Updated

6 years ago
Depends on: 857790
Assignee

Updated

6 years ago
Depends on: 857793
Assignee

Updated

6 years ago
Depends on: 859335
Flags: sec-review?
Assignee

Updated

6 years ago
Depends on: 859594
Assignee

Updated

6 years ago
Depends on: 859595
Assignee

Updated

6 years ago
Depends on: 859597
Assignee

Updated

6 years ago
Depends on: 859600
Assignee

Updated

6 years ago
Depends on: 859602
Assignee

Updated

6 years ago
Depends on: 854319
needs fuzzing
Flags: sec-review? → sec-review?(cdiehl)
Assignee

Comment 32

6 years ago
(In reply to comment #31)
> needs fuzzing

Jesse has been doing some of that.  Will definitely need more!
Assignee

Updated

6 years ago
Depends on: 861021
Assignee

Updated

6 years ago
Depends on: 861371
Assignee

Updated

6 years ago
Depends on: 861591
Assignee

Updated

6 years ago
Depends on: 861187
Assignee

Updated

6 years ago
Depends on: 862177
Assignee

Updated

6 years ago
Depends on: 863923
Assignee

Updated

6 years ago
Depends on: 863918
Assignee

Updated

6 years ago
Depends on: 864083
Assignee

Updated

6 years ago
Depends on: 864086
Assignee

Updated

6 years ago
Depends on: 864091
Assignee

Updated

6 years ago
Depends on: 864164
Assignee

Updated

6 years ago
Depends on: 864171
Assignee

Updated

6 years ago
Depends on: 864351
Assignee

Updated

6 years ago
Depends on: 864605
Assignee

Updated

6 years ago
Depends on: 864606
Assignee

Updated

6 years ago
Depends on: 864609
Assignee

Updated

6 years ago
Depends on: 864613
Assignee

Updated

6 years ago
Depends on: 864780
Assignee

Updated

6 years ago
Depends on: 864937
Assignee

Updated

6 years ago
Depends on: 865231
Assignee

Updated

6 years ago
Depends on: 865233
Assignee

Updated

6 years ago
Depends on: 865234
Assignee

Updated

6 years ago
Depends on: 865239
Assignee

Updated

6 years ago
Depends on: 865241
Assignee

Updated

6 years ago
Depends on: 865242
Assignee

Updated

6 years ago
Depends on: 865244
Assignee

Updated

6 years ago
Depends on: 865246
Assignee

Updated

6 years ago
Depends on: 865247
Assignee

Updated

6 years ago
Depends on: 865248
Assignee

Updated

6 years ago
Depends on: 865251
Assignee

Updated

6 years ago
Depends on: oscillatornode
Assignee

Updated

6 years ago
Depends on: 865256
Assignee

Updated

6 years ago
Depends on: 865257
Assignee

Updated

6 years ago
Depends on: 865261
Assignee

Updated

6 years ago
Depends on: 864709
Assignee

Updated

6 years ago
Depends on: 865004
Assignee

Updated

6 years ago
Depends on: 865413
Assignee

Updated

6 years ago
Depends on: 865532
Assignee

Updated

6 years ago
Depends on: 865548
Assignee

Updated

6 years ago
Depends on: 865550
Assignee

Updated

6 years ago
Depends on: 865553
Assignee

Updated

6 years ago
Depends on: 865650
Assignee

Updated

6 years ago
Depends on: 865642
Assignee

Updated

6 years ago
Depends on: 862088
Assignee

Updated

6 years ago
Depends on: 866079
Depends on: 866108
Assignee

Updated

6 years ago
Depends on: 866141
Assignee

Updated

6 years ago
Depends on: 866433
Assignee

Updated

6 years ago
Depends on: 866434
Assignee

Updated

6 years ago
Depends on: 866442
Assignee

Updated

6 years ago
Depends on: 866570
Assignee

Updated

6 years ago
Depends on: 866737
Assignee

Updated

6 years ago
Depends on: 866839
Assignee

Updated

6 years ago
Depends on: 867089
Assignee

Updated

6 years ago
Depends on: 867174
Assignee

Updated

6 years ago
Depends on: 867324
Assignee

Updated

6 years ago
Depends on: 867203
Depends on: 867086
Depends on: 867104
Assignee

Updated

6 years ago
Depends on: 867511
Assignee

Updated

6 years ago
Depends on: 867588
Assignee

Comment 33

6 years ago
It would be great if we could relnote this on Aurora once 23 gets there.
relnote-firefox: --- → ?
Assignee

Updated

6 years ago
Depends on: 867876
Assignee

Updated

6 years ago
Depends on: 868116
Depends on: 868305
Assignee

Updated

6 years ago
Depends on: 868409
Assignee

Updated

6 years ago
Depends on: 868485
Assignee

Updated

6 years ago
Depends on: 868504
Assignee

Updated

6 years ago
Depends on: 868776
Assignee

Updated

6 years ago
Depends on: 868855
Assignee

Updated

6 years ago
Depends on: 868864
Depends on: 869073
Assignee

Updated

6 years ago
No longer depends on: 869073
Assignee

Updated

6 years ago
Depends on: 869224
Depends on: 869257
Assignee

Updated

6 years ago
Depends on: 869682
Assignee

Updated

6 years ago
Depends on: 869684
Depends on: 870065
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #33)
> It would be great if we could relnote this on Aurora once 23 gets there.

Is this coded to be disabled on Beta/Release? Or will the whole feature be ready and enabled in FF23 riding the trains.
Assignee

Updated

6 years ago
Depends on: 870167
Depends on: 870174
Assignee

Comment 35

6 years ago
(In reply to comment #34)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #33)
> > It would be great if we could relnote this on Aurora once 23 gets there.
> 
> Is this coded to be disabled on Beta/Release? Or will the whole feature be
> ready and enabled in FF23 riding the trains.

It's not clear yet, we do have a vehicle for disabling it on Beta/Release if needed, and we'll obviously try to ship it as soon as we can.  But that's besides the point.  What I'm interested in is for this to come up in the list of new things for Aurora 23 so that we can get some developer attention to it.
Assignee

Updated

6 years ago
Depends on: 871201
Assignee

Updated

6 years ago
Depends on: 871577
Depends on: 872208
No longer depends on: 872208
Depends on: 872394
Assignee

Updated

6 years ago
Depends on: 872635
Assignee

Updated

6 years ago
Depends on: 873335
Assignee

Updated

6 years ago
Depends on: 873553

Updated

6 years ago
Depends on: 874024
This has been noted in the Aurora 23 release notes:

http://www.mozilla.org/en-US/firefox/23.0a2/auroranotes/

If you would like to make any changes or have questions/concerns please contact me directly.
Assignee

Updated

6 years ago
Depends on: 873858
Assignee

Updated

6 years ago
Depends on: 874508
Assignee

Updated

6 years ago
Depends on: 874540
Depends on: 874869
Assignee

Updated

6 years ago
Depends on: 874915
Depends on: 874934
Depends on: 874952
Depends on: 875144
Depends on: 875152
Depends on: 875221
Assignee

Updated

6 years ago
Depends on: 875277
Depends on: 875402
Assignee

Updated

6 years ago
Depends on: 875529
Depends on: 875596
Assignee

Updated

6 years ago
Depends on: 875617
Assignee

Updated

6 years ago
Depends on: 875911
Depends on: 876118
Depends on: 876207
Depends on: 876215
Depends on: 876249
Depends on: 876273
Depends on: 876338
Assignee

Updated

6 years ago
Depends on: 876252
Assignee

Updated

6 years ago
Depends on: 876834
Depends on: 877039
Depends on: 877125
Depends on: 877231
Depends on: 877523
Depends on: 877527
Assignee

Updated

6 years ago
Depends on: 877662
Assignee

Updated

6 years ago
Depends on: 876024
Assignee

Updated

6 years ago
Depends on: 877695
Depends on: 877820
Depends on: 878014
Depends on: 878015
Depends on: 878328
Depends on: 878407
Depends on: 878478
Assignee

Updated

6 years ago
Depends on: 878497
Assignee

Updated

6 years ago
Depends on: 879014
Assignee

Updated

6 years ago
Component: Video/Audio → Web Audio
Depends on: 880129
Assignee

Updated

6 years ago
Depends on: 880265
Assignee

Updated

6 years ago
Depends on: 880202
Depends on: 880342
Depends on: 880384
Depends on: 880404
Depends on: 880724
Assignee

Updated

6 years ago
Depends on: 881558
Assignee

Updated

6 years ago
Depends on: 881587
Depends on: 881775
Assignee

Updated

6 years ago
No longer depends on: 881775
Assignee

Updated

6 years ago
Depends on: 881959
Assignee

Updated

6 years ago
Depends on: 882171
Depends on: 882956
Assignee

Updated

6 years ago
Depends on: 883010
Assignee

Updated

6 years ago
Depends on: 883011

Comment 37

6 years ago
Hello, I'm getting a sample rate of 48khz in my AudioContext (using the nightly) even if I'm not hooked up to any special audio interfaces. I would expect 44.1... or am I thinking about something wrong? - Charlie
(In reply to bigbadotis from comment #37)
> Hello, I'm getting a sample rate of 48khz in my AudioContext (using the
> nightly) even if I'm not hooked up to any special audio interfaces. I would
> expect 44.1... or am I thinking about something wrong? - Charlie

Why would you expect 44.1kHz?

The spec does not mandate any particular sample rate. You should always use |AudioContext.sampleRate| to make your calculations anyway, you cannot have guarantees about what the samplerate will be on any particular platform, as it is hardware and OS dependent.

Comment 39

6 years ago
I'm guessing I'm misunderstanding something fundamental here, but, if my DAC is running 44.1, and Firefox is processing at 48, where is the downsampling occurring? Isn't it a 10% efficiency hit if Firefox is processing more samples per second than my computer is outputting via the DAC?

Thanks for any clarification.
You are perfectly right, and this is an issue we are going to address in the future, but there is only so many hours in a day.
Depends on: 883591
Depends on: 884459
Assignee

Updated

6 years ago
Depends on: 884632
Assignee

Updated

6 years ago
Depends on: 885496

Comment 41

6 years ago
Just downloaded the Nightly. No createOscillator() ? 

I've been wanting to test this app in FireFox:

http://cloudmusiccompany.appspot.com/

Is there a temporary fix for that to begin testing? Thanks.
Assignee

Updated

6 years ago
Depends on: 885505
Assignee

Comment 42

6 years ago
(In reply to comment #41)
> Just downloaded the Nightly. No createOscillator() ? 
> 
> I've been wanting to test this app in FireFox:
> 
> http://cloudmusiccompany.appspot.com/
> 
> Is there a temporary fix for that to begin testing? Thanks.

Bug 865253 tracks implementing OscillatorNode.  We hope to land the fix to that bug within the next few days...
Assignee

Updated

6 years ago
Depends on: 886165
Assignee

Updated

6 years ago
Depends on: 886168
Assignee

Updated

6 years ago
Depends on: 886381
Assignee

Updated

6 years ago
Depends on: 885956
Assignee

Updated

6 years ago
Depends on: 886787

Comment 43

6 years ago
Any plans to implement createMediaElementSource ?
Assignee

Comment 44

6 years ago
(In reply to comment #43)
> Any plans to implement createMediaElementSource ?

Of course!  See bug 855568.
Assignee

Updated

6 years ago
Depends on: 889016
Assignee

Updated

6 years ago
Depends on: 889042
Target Milestone: --- → mozilla24
Assignee

Updated

6 years ago
Depends on: 890023
Assignee

Updated

6 years ago
Depends on: 890072
Depends on: 890369
Depends on: 890371
Assignee

Updated

6 years ago
Depends on: 881092
Assignee

Updated

6 years ago
Depends on: 891254
Depends on: 895196
Depends on: 898962
Assignee

Updated

6 years ago
Summary: Implement Web Audio → Implement and ship Web Audio
This is currently marked as targeted for Firefox 24.  Am I wrong an thinking this should be updated to reflect the new intention to let it bake a bit longer and ship in 25?
QA Contact: manuela.muntean
Assignee

Updated

6 years ago
Target Milestone: mozilla24 → mozilla25
Depends on: 904707
Depends on: 905444
Depends on: 906966
Depends on: 907986
Adding the feature keyword so that this bug is properly picked up by the Release Tracking wiki page.
Keywords: feature
Depends on: 914030
Depends on: 910171
Assignee

Updated

6 years ago
Depends on: 915524
Is everything on track to leave this on in Firefox 25 and have it pulled into Firefox 1.2?  The last answer was yes, but I wanted to confirm before Monday.
I'd say yes, for my blockers. Ralph?
Flags: needinfo?(giles)
It's going to be close, but I still intend to close by blocker before Monday.
Flags: needinfo?(giles)
Did we make it?
Assignee

Comment 51

6 years ago
(In reply to comment #50)
> Did we make it?

Yeah, we'll try to uplift the patches that missed the deadline.
Ok great, drop in a comment once the last blocker is confirmed as in both Firefox 25 Desktop and Android along with Firefox 1.2.  If either of those release versions changes, please let me know asap.
Depends on: 920987
Depends on: 912474
Depends on: 921695
Assignee

Comment 53

6 years ago
Let's call this fixed.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Depends on: 923319

Comment 54

6 years ago
In case anyone wants to do some performance tests, my app here is updated to work with FireFox's Web Audio API support (trying to keep consistent with iOS 6's Web Audio API in Safari Mobile and FireFox needs basically two interfaces).

http://cloudmusiccompany.appspot.com/
Depends on: 913854
Depends on: 924286
Depends on: 924288
Depends on: 924289
No longer depends on: 924289
Depends on: 925619
Depends on: 932621
Depends on: 956489

Comment 55

5 years ago
I've been testing WebAudio API on firefox 27 (beta as of today) with audio tag as source [createMediaElementSource(audio_tag)], and after doing that binding, setting the audio_tag.playbackrate during audio execution makes no effect anymore... also, timeudate event is not fired, and the audio tag cursor on the controls stops indicating the current time.

Hope this report helps.
(In reply to Sergio from comment #55)
> I've been testing WebAudio API on firefox 27 (beta as of today) with audio
> tag as source [createMediaElementSource(audio_tag)], and after doing that
> binding, setting the audio_tag.playbackrate during audio execution makes no
> effect anymore... also, timeudate event is not fired, and the audio tag
> cursor on the controls stops indicating the current time.
> 
> Hope this report helps.

I think this (apart from the playback rate thing) has been fixed in current Nightly.
(In reply to Paul Adenot (:padenot) from comment #56)

> I think this (apart from the playback rate thing) has been fixed in current
> Nightly.

It sounds like Sergio is reporting more than one bug here.

Paul -- Is there a bug already tracking some of this?  If so, do you have the bug number?  And is there a fix available that should be uplifted (at least to Fx 28)?  Does the playback rate problem (that you think may not be fixed) also have a bug number, and is it a Web Audio bug or Video/Audio (Media Playback) bug?  Thanks.
Flags: needinfo?(paul)
(In reply to Maire Reavy [:mreavy] from comment #57)
> (In reply to Paul Adenot (:padenot) from comment #56)
> 
> > I think this (apart from the playback rate thing) has been fixed in current
> > Nightly.
> 
> It sounds like Sergio is reporting more than one bug here.
> 
> Paul -- Is there a bug already tracking some of this?  If so, do you have
> the bug number?  And is there a fix available that should be uplifted (at
> least to Fx 28)?  Does the playback rate problem (that you think may not be
> fixed) also have a bug number, and is it a Web Audio bug or Video/Audio
> (Media Playback) bug?  Thanks.

That would mean uplifting roc's changes in 938022, if not more.

The playbackRate bug is a bug at the barrier between Media Playback and Web Audio. I opened bug 966247 to track this.
Flags: needinfo?(paul)
(In reply to Paul Adenot (:padenot) from comment #58)
> That would mean uplifting roc's changes in 938022, if not more.

Thanks for the bug number.  The good news is that that fix is already in Fx 28.
> 
> The playbackRate bug is a bug at the barrier between Media Playback and Web 
> Audio. I opened bug 966247 to track this.

Thanks!
Flags: sec-review?(cdiehl) → sec-review+
Depends on: 1020370
No longer depends on: 864780
You need to log in before you can comment on or make changes to this bug.