Web Audio API - Analyzer does not work

[GoogleCodeExporter]

related to this question: 
https://plus.google.com/105702345674277158844/posts/bGtuXy89VYh

i just started to develop my first chromecast app where i want to play audio 
and show an analyzer. the problem is, that the analyzer is not showing anything.

my code is fully working on chrome desktop (34.0.1847.137m on Win 8.1 Pro) but 
not on chromecast.

Original issue reported on code.google.com by kujans...@gmail.com on 17 May 2014 at 8:03

[GoogleCodeExporter]

I'm running into the same issue. When I add a script processing node, it looks 
like the onaudioprocess event is fired correctly, but the passed in 
AudioProcessingEvent's inputBuffer is nothing but zeros.

Original comment by JonEcks...@gmail.com on 18 Jun 2014 at 5:00

[GoogleCodeExporter]

Original comment by aba...@google.com on 26 Sep 2014 at 6:14

• Changed state: Acknowledged

[GoogleCodeExporter]

Issue 288 has been merged into this issue.

Original comment by jonathan...@google.com on 5 Nov 2014 at 6:12

[GoogleCodeExporter]

This has been addressed in the latest SDK release. If you are still having 
issues, let us know and we can reopen the ticket.

Original comment by jonathan...@google.com on 11 May 2015 at 10:15

• Changed state: Fixed

[GoogleCodeExporter]

Hello,

i still dont get any data(all values are zero) for my analyzer.

My code is based on this tutorial and works on chrome desktop (42.0.2311.152 m) 
https://www.developphp.com/video/JavaScript/Analyser-Bars-Animation-HTML-Audio-A
PI-Tutorial (only change is using an shoutcast stream as source and 
crossorigin="anonymous" on the media element)

i tested on my chromecast with firmware 27946. on sender side i'm using android 
with 7.3.0 play services and 21.1.1 mediarouter. the receiver is using 
"//www.gstatic.com/cast/sdk/libs/receiver/2.0.0/cast_receiver.js"

anything i need to update?

Original comment by kujans...@gmail.com on 16 May 2015 at 8:39

[GoogleCodeExporter]

The firmware version should be 31432. You may have to wait for the update to 
take effect.

Original comment by jonathan...@google.com on 18 May 2015 at 4:55

[GoogleCodeExporter]

Got the 31432 update, but still no valid data (all values are 0)

Original comment by kujans...@gmail.com on 22 May 2015 at 7:23

[GoogleCodeExporter]

Just to add a datapoint, I'm also hitting this problem on 31432 firmware.

Original comment by bhels...@gmail.com on 23 May 2015 at 3:34

[GoogleCodeExporter]

Currently, WebAudio analyzer on Chromecast only works for audio-only FLAC/Opus 
content;
other combinations are not supported. Apologies for the confusion.

Original comment by jonathan...@google.com on 26 May 2015 at 10:37

[GoogleCodeExporter]

Since the status is still "fixed", does that mean there are no plans to support 
other audio formats?

Original comment by cdolphin...@gmail.com on 26 May 2015 at 10:48

[GoogleCodeExporter]

Not at this time, but make sure to star the issue to be notified of any future 
developments.

Original comment by jonathan...@google.com on 26 May 2015 at 10:58

[GoogleCodeExporter]

Thanks! Is there a forum for discuss of which formats will be added or is that 
entirely an internal decision?

Original comment by cdolphin...@gmail.com on 26 May 2015 at 11:06

[GoogleCodeExporter]

That's something that would be discussed internally but any relevant updates 
will be posted here. You are welcome to post any audio formats that you think 
should be supported.

Original comment by jonathan...@google.com on 27 May 2015 at 12:14

[GoogleCodeExporter]

I think at least mp3 should be supported too. but in our case we just switched 
our streams to AAC.

i wonder why you only addd flac/opus? isnt chromecast based on chrome browser 
so that the required code to get this working should already be available?

Original comment by kujans...@gmail.com on 27 May 2015 at 9:40

[GoogleCodeExporter]

Both FLAC and Opus audio appear to work fine with an AnalyserNode. Other 
formats (including even uncompressed LPCM WAVE) just output zeros as others 
have described.

I too would like to see other common formats supported such as MP3, Vorbis and 
WAV.

Presumably this has been done to encourage the use of Opus and FLAC; these 
perhaps being the formats that Google Play Music use (which now has a particle 
visualizer).

Original comment by the.smoo...@gmail.com on 4 Nov 2015 at 12:37

[GoogleCodeExporter]

Issue 689 has been merged into this issue.

Original comment by na...@google.com on 21 Nov 2015 at 12:37