From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: all you MP3 people out there... a fix for lars!
Date: 29 Oct 1998 08:21:19 +0100 [thread overview]
Message-ID: <m3u30nltow.fsf@sparky.gnus.org> (raw)
In-Reply-To: Harald Meland's message of "29 Oct 1998 03:11:13 +0100"
Harald Meland <Harald.Meland@usit.uio.no> writes:
> I'd guess Lars is using L.A.M.E., found on
> <URL:http://student.uq.edu.au/~s302585/>.
I'm actually using Mike Cheng's version of 8hz, but that's the same
thing, only different.
> (Just guesswork, of course, but he _is_ getting thanks in the NEWS
> section :-)
I had to do *something* to relax before the Gnus talk a couple of
weeks ago, so I hacked away at LAME. :-)
> L.A.M.E. also claims to be much faster than BladeEnc, whereas BladeEnc
> seems to be claiming the opposite :)
Here are the tests I did; 8hz and LAME are virtually identical
speed-wise.
orig.wav (/ 56812604.0 (* 44100.0 4)) => 322.07
blade-128.mp3 (/ (+ (* 29 60) 18) 322.07) => 5.46
8hz-128.mp3 (/ (+ (* 18 60) 54) 322.07) => 3.52
encode-128.mp3 (/ (+ (* 25 60) 95) 322.07) => 4.95
blade-256.mp3 (/ (+ (* 24 60) 16) 322.07) => 4.52
8hz-256.mp3 (/ (+ (* 18 60) 6) 322.07) => 3.37
encode-256.mp3 (/ (+ (* 20 60) 31) 322.07) => 3.822
m3enc-128.mp3 (/ (+ (* 9 60) 39) 30) => 19
This is on a K6. These number say that 8hz compresses at a 3.52:1
time rate, while blade does it on a 5.46:1 rate, which means that
blade is, er, 70% slower than 8hz.
This is with Cheng's version of 8hz, mind you -- the original 8hz
version from the 8hz people is slower.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-10-29 7:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-28 18:16 William M. Perry
1998-10-28 22:24 ` Wes Hardaker
1998-10-29 1:04 ` William M. Perry
1998-10-29 1:28 ` Wes Hardaker
1998-10-29 2:11 ` Harald Meland
1998-10-29 5:05 ` Wes Hardaker
1998-10-29 5:20 ` David Hedbor
1998-10-29 7:21 ` Lars Magne Ingebrigtsen [this message]
1998-10-29 18:00 ` Wes Hardaker
1998-10-31 13:32 ` Lars Magne Ingebrigtsen
1998-11-02 18:59 ` Wes Hardaker
1998-11-04 5:51 ` Matt Simmons
1998-11-10 16:22 ` Justin Sheehy
[not found] ` <x7g1br8nh3.fsf@peorth.gweep.net>
1998-11-10 21:35 ` David Hedbor
1998-11-12 21:34 ` Brian Edmonds
1998-10-29 2:17 ` Mark R. Boyns
1998-10-29 11:15 ` Lars Magne Ingebrigtsen
1998-10-29 17:56 ` Wes Hardaker
1998-10-29 21:09 ` Darren Stalder
1998-10-31 13:31 ` Lars Magne Ingebrigtsen
1998-11-01 16:18 ` William M. Perry
[not found] ` <x7btmsejes.fsf@peorth.gweep.net>
1998-11-01 17:22 ` Brian Edmonds
1998-11-01 20:46 ` William M. Perry
1998-11-07 13:41 ` Lars Magne Ingebrigtsen
1998-10-29 12:57 ` Darren/Torin/Who Ever...
1998-10-29 17:57 ` Wes Hardaker
1998-10-29 20:55 ` Darren Stalder
1998-10-30 16:10 ` William M. Perry
1998-10-30 18:10 ` William M. Perry
1998-11-04 8:08 ` Matt Simmons
1998-11-04 10:42 ` William M. Perry
1998-11-05 8:05 ` Matt Simmons
1998-11-05 13:15 ` William M. Perry
1998-11-07 13:54 ` Lars Magne Ingebrigtsen
1998-11-09 16:05 ` Wes Hardaker
1998-11-10 4:51 ` Lars Magne Ingebrigtsen
1998-11-11 7:10 ` Matt Simmons
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=m3u30nltow.fsf@sparky.gnus.org \
--to=larsi@gnus.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;
as well as URLs for NNTP newsgroup(s).