Linux Sound subsystem development
 help / color / mirror / Atom feed
From: <paco@hydrofunk.org>
To: linux-sound@vger.kernel.org
Subject: Re: Multimedia compression
Date: Fri, 16 Jun 2000 21:55:35 +0000	[thread overview]
Message-ID: <marc-linux-sound-96119262931697@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96119149930040@msgid-missing>

There's something called SHORTEN that does lossless compression of .WAV
files. It produces .SHN files that are roughly 1/2 the size of the .WAV,
but... you can't play a SHN file (yet).  You have to decompress it to a
WAV and listen to it that way.  So, it's good for up/down-loading music
and for archiving music.

You can whip up a little script to play CDs full of SHN files.  I did.  It
just decompresses the SHN off of a CD and pipes the output directly to
"play" so that I can keep twice the music on a single CD.

I don't remember the Shorten website name exactly, but there is a link to
it off of my website.

	http://www.hydrofunk.org/music

peace,
--Paco

On Sat, 17 Jun 2000, Sergey wrote:

> Hi!
>  Have someone heard of "Multimedia compression"?
>  I mean, a special Zip (WINZIP :( ) which compresses PCM WAVes without
>  losses. (Special optimized algorythms are used)
>  Is there something like that for Linux?
>  
>  As I know, it will save 30-40% of disk space if you store plain PCMs -
> whiel a ususal bzip or zip saves just about 5%.
>  
>  Please do not write of mpeg or any other "destructive" compression.
>          Sergey.
> 

  reply	other threads:[~2000-06-16 21:55 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 [this message]
2000-06-16 21:56 ` paco
2000-06-17 16:57 ` Benno Senoner
2000-06-20 17:08 ` paco

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-96119262931697@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