Fons Adriaensen wrote:
On Sun, Apr 03, 2016 at 11:05:59AM +0000, Politis Archontis wrote:
Oops, that should have been “About N3D…” instead of “About ACN...”
Modulo that correction, that's probably something that anyone who
has ever done any maths related to HOA decoding, beamforming,
rotation, etc. will confirm without any reservation.
Another matter: what is the 'official' definition of IEM's
Ambix format ? Problem is that I find contradicting info.
There's the paper:
<http://iem.kug.ac.at/fileadmin/media/iem/projects/2011/ambisonics11_nachbar_zotter_sontacchi_deleflie.pdf>
and the source code on Github:
<https://github.com/umlaeute/ambix/blob/master/libambix/src/uuid_chunk.c>
These mention different UUIDs for the extended (with matrix) format.
Also in the paper it is at least suggested (Fig. 1) that the matrix
dimensions are 32-bit floating point, while the code uses 32-bit
integers (which makes sense).
1. I honestly hope that Google IT developpers will be aware of any of
such "issues". < g >
2. Shows that you should not use anyything just because it is new. ("to
replace an outdated 1st order format"; Google proposes AmbiX for
FOA-only application!)
3. Alas, seems to be an overkill solution - compared to B format/FOA.
Best,
Stefan
_______________________________________________
Sursound mailing list
[email protected]
https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit
account or options, view archives and so on.
