|
From: Michael C. <ch...@mc...> - 2008-01-10 07:26:40
|
[ Apologies the previous double posting, I am having
to use a 'tunnel' to escape the spam filters ! ]
*.amb files are Wave Format Extensible files with a specific GUID (they
contain ambisonic channels).
The 'dwChannelMask' (four bytes) is always 0.
The SubFormat GUID (16 bytes) is
\x03\x00\x00\x00\x21\x07\xd3\x11\x86\x44\xc8\xc1\xca\x00\x00\x00
for floating point
or
\x01\x00\x00\x00\x21\x07\xd3\x11\x86\x44\xc8\xc1\xca\x00\x00\x00
for PCM.
(The PCM/float bytes occur in exactly the same place as for all other Wavex
files.)
Sox recognises "in.amb" as Wavex and will process it.
SoX will not though, currently, write "out.amb".
The change requested is seemingly trivial (much of the data is already in the
code), but my attempts to modify wav.c / wav.h to submit a diff have been
remarkably unsuccessful, so I propose this to the authors.
Thanks,
Michael.
PS Can provide fuller references for the above if required. MC
PPS an 'all things to all men' solution would be to allow users
to use flags to set bytes 41-44 (speakers mapped to tracks/channels)
and bytes 47-60 (the only bit of the GUID the user should set (bytes
45 and 46 can be, and are arguably better, set by the software)).
MC
|