From: Devendra Jalihal <dj@tenet.res.in>
To: linux-sound@vger.kernel.org
Subject: Need info on G.723.1 .wav format
Date: Mon, 18 Feb 2002 08:20:48 +0000 [thread overview]
Message-ID: <marc-linux-sound-101405687018962@msgid-missing> (raw)
I am sorry for sending this mail to linux-sound group. It is not very
pertinent to this group. But, I don't know where to send it. So, here it
goes.
We have our own implementation of G.723.1 speech compression @ 6.3 kbps
(it is a licenced codec and not a free one). I would like to output the
compressed bits in .wav format. Can somebody direct me to the site where I
can get info about .wav in general and specifically about G.723.1 based
.wav? Is there an IETF recommendation on .wav? An RFC? Where can I get
info about .wav? Which body makes the .wav standard?
I would really appreciate any info that you can give me.
Devendra Jalihal
dj@tenet.res.in
next reply other threads:[~2002-02-18 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 8:20 Devendra Jalihal [this message]
2002-02-18 19:48 ` Need info on G.723.1 .wav format
2002-02-19 7:45 ` Zwane Mwaikambo
2002-02-19 11:43 ` Devendra Jalihal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-sound-101405687018962@msgid-missing \
--to=dj@tenet.res.in \
--cc=linux-sound@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox