The problem is that Mozilla (and maybe others) just need to fix (or better document) their version of the Web Audio API. Then it'd be possible to decode ambisonic at any order. Chrome does a better job, but it's (hopefully) a temporary monopoly, since Mozilla is organising the Web Audio Conference. -- Marc
On Fri, 23 Oct 2015 09:37:06 +0100 Dave Malham <dave.mal...@york.ac.uk> wrote: > I think the problem is the fact that at least one of the decoders > needed is proprietary so costs money to include which makes it > difficult for free browsers, if not backed by mega corporations. Of > course, I could well be wrong (again) but it is a shame when Mozilla > loses it's position as the most standard compliant browser, > especially when it impacts audio. > > Dave > > > On 22 October 2015 at 13:44, David Pickett <d...@fugato.com> wrote: > > > Bruce Wiggins' webpage on browsers that play surround recordings > > using the HTML5 <audio> tag is 3.5 years old. > > > > http://www.brucewiggins.co.uk/?p=265 > > > > I dont use IE, and Firefox doesnt play ball at all on the PC, so I > > use Chrome for multi-channel aac files. > > > > http://www.fugato.com/pickett/surround-tests.shtml > > > > But it is disappointing to think that no other browsers have caught > > up in the last three years. > > > > Has anyone tested any others with multi-channel files? > > > > David > > > > _______________________________________________ > > Sursound mailing list > > Sursound@music.vt.edu > > https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe > > here, edit account or options, view archives and so on. > > > > > _______________________________________________ Sursound mailing list Sursound@music.vt.edu https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit account or options, view archives and so on.
