From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Line-In
Date: Thu, 28 Feb 2002 12:09:18 -0500 [thread overview]
Message-ID: <20020228170931.84E90199EE@mail.cse.psu.edu> (raw)
glad BladeEnc is working for you. as the page i
referenced notes, i think your results from LAME
match what i was seeing. rsc noted earlier that
LAME and /dev/audio disagree about byte order
in the samples; i've lost my LAME binary, so i
can't confirm that this makes my issue go away,
but if you have LAME around you could try the
command he posted:
lame -v -rx -S --preset cd $i $i.mp3 && rm $i
and see if that produces more sensable mp3s. it'd
be nice to have both LAME and BladeEnc working,
since they're better at different things.
ア
next reply other threads:[~2002-02-28 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 17:09 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 16:35 Russ Cox
2002-02-26 15:27 anothy
2002-02-27 10:06 ` Don
2002-02-26 10:15 Don
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=20020228170931.84E90199EE@mail.cse.psu.edu \
--to=anothy@cosym.net \
--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).