Sorry, forgot to mention build numbers.

IE - 11.0.9600.18537
FF - 50.1
Chrome - 55.0.2883.87 m

Unable to register with  http://siriusxm.com, request got blocked for security reasons.
Adding TE-NeedsTriageHelp label for further triage.

Deleted: Issue 679166.PNG 27.3 KB

	Issue 679166.PNG 27.3 KB View Download

Assigning to rtoy@ for triage at the "unable to decode audio data" error in the console in a Web Audio error.

Comment #2 version of chrome is inconsistent with the reported chrome version.  Is it chrome 55 or chrome 57?

Does it work with Chrome 56?  My guess is that it stopped working with 57 because that's when the prefixed AudioContext was removed (after being deprecated for several years).

Getting all of the console log from Chrome 56 (or earlier) and 57 would be helpful to determine if the removal is the problem.

Chrome Version : 57.0.2976.0 (Developer Build) (32-bit) is the version of Chromium I was using from which I generated the screenshot.  I upgraded to version 57 of Chromium after experiencing the same issue in version 56.

The version of Chrome that was reported in the comment was referring to Google Chrome. My apologies for the confusion.

If needed I can install Chromium 56 and take another screenshot, though I'm almost certain the behavior and reported errors were identical.

Hmm. If you had this problem in Chrome 56 too, then it's not the removal of the prefixed AudioContext as I guessed.  The screenshot indicates that webaudio cannot decode the audio for some reason.

If you have the time and desire, it would be great if you could try Chrome 56 (and 55) and capture the console log.

Pardon a stupid question, but when you say Chrome 56 (and 55), do you mean Chromium 55/56 or Google Chrome 55/56?  If you mean the former, where can I find older versions of Chromium for x86?

Nevermind, I found the old versions.  It never fails that you only find something immediately after you ask someone.

Looking in the Win folder I see a lot of 5 digit numbers (99646,99621) . So I guess the more appropriate question is how do I know which builds are version 55 and 56?

I mean Chrome 55/56, not Chromium.  To find the version, go to chrome://help and you'll see a version number like 57.0.2987.37 (for Chrome 57 beta that I'm running right now).

SiriusXM audio plays as expected in Google Chrome 55 and 56.  However, there are still a few console errors.  Attached screenshots for each.

Deleted: 56.0.2924.87 (Official Build) (32-bit).png 493 KB

	56.0.2924.87 (Official Build) (32-bit).png 493 KB View Download

Deleted: 55.0.2883.75 (Official Build) (32-bit).png 618 KB

	55.0.2883.75 (Official Build) (32-bit).png 618 KB View Download

These error messages are not from WebAudio. You will have to contact the Sirius XM developer to fix them.

I figured as much, but didn't want to come back with nothing.  The main issue still persists in Chromium.

That's because Chromium does not include the support for proprietary codec. Thus the codec like MP3 or AAC won't be played. I am assuming Sirius player is using one of those codecs.

Correct, Sirius uses AAC.

Yes, instead of using Chromium, please try Chrome which has these codecs enabled.

I suspect this will be fixed by using Chrome.

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919 

Closing (WontFix, working as intended). Per c#16 and the fact that Chromium by default doesn't include any proprietary codecs, this is working as intended.