From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Where is mp3dec, pac4dec vorbisdec?
Date: Fri, 21 Jan 2005 10:15:59 +0900 [thread overview]
Message-ID: <229220a0e4b58969812bcc92ec921c1f@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <200501201829.j0KITTC08053@zamenhof.cs.utwente.nl>
Thanks Sape and Axel.
I now reminded there was a discussion on Pac format here, which
is a Lucent proprietary one.
Axel, you seem to have tried several decoders, such as minimad, mpg123,
madplay for mp3 file, and finaly chose madplay. Would you teach us
what was your experience on those decoders if possible where I mean
if you think it not bad to discuss in public.
Kenji
next prev parent reply other threads:[~2005-01-21 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 8:51 Kenji Okamoto
2005-01-20 13:42 ` Sape Mullender
2005-01-20 18:29 ` Axel Belinfante
2005-01-21 1:15 ` Kenji Okamoto [this message]
2005-01-21 4:38 ` Kenji Okamoto
2005-01-25 1:55 ` Christopher Nielsen
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=229220a0e4b58969812bcc92ec921c1f@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).