From: "paco@hydrofunk.org" <paco@hydrofunk.org>
To: linux-sound@vger.kernel.org
Subject: Re: Multimedia compression
Date: Tue, 20 Jun 2000 17:08:54 +0000 [thread overview]
Message-ID: <marc-linux-sound-96200429928835@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96119149930040@msgid-missing>
On Sat, 17 Jun 2000, Benno Senoner wrote:
> I tried shorten some time ago:
>
> OTOH, when using lossless compression the gain is sometime minimal,
> only 20% if you are unlucky.
> Not much for my taste.
I find this very hard to believe. Speaking from my own experience, I've
had nothing but outstanding results with SHORTEN.
I collect live concert bootlegs; recorded on DAT, dumped down onto the
HDD as WAVs, compressed to SHNs, and burned onto CDs that I listen to.
I've got nearly 100 such CDs sitting here at my side, and here's the
stats based on those live concert CDs.
My average song compression 52% savings
My worst single-song comression 35% savings
My best single-song compression 60% savings
The main thing I wanted to point out is that I've never had a something
compress less than 35%.
peace,
-Paco
prev parent reply other threads:[~2000-06-20 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 21:35 Multimedia compression Sergey
2000-06-16 21:55 ` paco
2000-06-16 21:56 ` paco
2000-06-17 16:57 ` Benno Senoner
2000-06-20 17:08 ` paco [this message]
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-96200429928835@msgid-missing \
--to=paco@hydrofunk.org \
--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