14 Apr
2006
14 Apr
'06
6:40 a.m.
I've gone through the docs a number of times, but can't find
a way to read / write the channelmask and guid in a WAVEFORMAT
extensible file.
Is it possible ?
--
FA
Follie! Follie! Delirio vano e' questo!
14 Apr
14 Apr
7:46 a.m.
Alfons Adriaensen wrote:
I've gone through the docs a number of times, but
can't find
a way to read / write the channelmask and guid in a WAVEFORMAT
extensible file.
I thought the guid was determined by the data encoding ie once
you decide to write PCM data, you have to use a specific guid.
Is it possible ?
Not currently. If you want to discuss this further maybe you
should bring it up on the libnsndfile-devel list:
http://www.mega-nerd.com/libsndfile/lists.html
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"I could never learn to use C++, because of the completely
overwhelming desire to redesign the language every time I tried
to use it, but this is the normal, healthy reaction to C++."
-- Erik Naggum
9:44 a.m.
On Fri, Apr 14, 2006 at 07:46:38PM +1000, Erik de Castro Lopo wrote:
Alfons Adriaensen wrote:
You obviously need access to the channelmask when reading or creating
multichannel files.
As to the GUID, there are e.g. special GUIDs for Ambisonics files,
see <http://dream.cs.bath.ac.uk/researchdev/wave-ex/bformat.html>.
BTW I don't understand the relation between the definition of
the GUIDs on that page
SUBTYPE_AMBISONIC_B_FORMAT_PCM {00000001-0721-11d3-8644-C8C1CA000000}
SUBTYPE_AMBISONIC_B_FORMAT_IEEE_FLOAT {00000003-0721-11d3-8644-C8C1CA000000}
and the example representation of the first one further down:
{0x00000001,0x0000,0x0010, {0x80,0x00, 0x00,0xaa,0x00,0x38, 0x9b, 0x71}}
Does it make sense to you ?
--
FA
Follie! Follie! Delirio vano e' questo!
I've gone through the docs a number of times,
but can't find
a way to read / write the channelmask and guid in a WAVEFORMAT
extensible file.
I thought the guid was determined by the data encoding ie once
you decide to write PCM data, you have to use a specific guid.
10:14 a.m.
Alfons Adriaensen wrote:
You obviously need access to the channelmask when
reading or creating
multichannel files.
As to the GUID, there are e.g. special GUIDs for Ambisonics files,
see <http://dream.cs.bath.ac.uk/researchdev/wave-ex/bformat.html>.
BTW I don't understand the relation between the definition of
the GUIDs on that page
SUBTYPE_AMBISONIC_B_FORMAT_PCM {00000001-0721-11d3-8644-C8C1CA000000}
SUBTYPE_AMBISONIC_B_FORMAT_IEEE_FLOAT {00000003-0721-11d3-8644-C8C1CA000000}
and the example representation of the first one further down:
{0x00000001,0x0000,0x0010, {0x80,0x00, 0x00,0xaa,0x00,0x38, 0x9b, 0x71}}
Does it make sense to you ?
Sorry, no it doesn't. Thats why I suggested joining the libsndfile-devel
list.
I didn't implement the WAVEX stuff. The guy who did is on the libsndfile-devel
list but not on this one.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"I invented the term Object-Oriented, and I can tell you I
did not have C++ in mind." -- Alan Kay
10:59 a.m.
Alfons Adriaensen <fons.adriaensen(a)alcatelaleniaspace.com> writes:
BTW I don't understand the relation between the
definition of
the GUIDs on that page
SUBTYPE_AMBISONIC_B_FORMAT_PCM {00000001-0721-11d3-8644-C8C1CA000000}
SUBTYPE_AMBISONIC_B_FORMAT_IEEE_FLOAT {00000003-0721-11d3-8644-C8C1CA000000}
and the example representation of the first one further down:
{0x00000001,0x0000,0x0010, {0x80,0x00, 0x00,0xaa,0x00,0x38, 0x9b, 0x71}}
Does it make sense to you ?
The example representation is for KSDATAFORMAT_SUBTYPE_PCM.
Some grepping through MS headers resulted in the following:
DEFINE_GUIDSTRUCT("00000001-0000-0010-8000-00aa00389b71",
KSDATAFORMAT_SUBTYPE_PCM);
#define KSDATAFORMAT_SUBTYPE_PCM DEFINE_GUIDNAMED(KSDATAFORMAT_SUBTYPE_PCM)
Matthias
12:29 p.m.
On Fri, Apr 14, 2006 at 02:59:28PM +0200, Matthias Koenig wrote:
Alfons Adriaensen
<fons.adriaensen(a)alcatelaleniaspace.com> writes:
The example representation is for
KSDATAFORMAT_SUBTYPE_PCM.
Some grepping through MS headers resulted in the following:
DEFINE_GUIDSTRUCT("00000001-0000-0010-8000-00aa00389b71",
KSDATAFORMAT_SUBTYPE_PCM);
#define KSDATAFORMAT_SUBTYPE_PCM DEFINE_GUIDNAMED(KSDATAFORMAT_SUBTYPE_PCM)
Thanks ! Suspected something like that but I don't have the
MS headers...
--
FA
Follie! Follie! Delirio vano e' questo!
6859
days inactive
6859
days old
linux-audio-dev@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Alfons Adriaensen -
Erik de Castro Lopo -
Matthias Koenig