From: "paco@hydrofunk.org" <paco@hydrofunk.org>
To: linux-sound@vger.kernel.org
Subject: Re: [linux-audio-dev] Re: Multimedia compression
Date: Tue, 20 Jun 2000 23:02:24 +0000 [thread overview]
Message-ID: <marc-linux-sound-96200429928838@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96126686903146@msgid-missing>
On Tue, 20 Jun 2000 paco@OhKeePa.Net wrote:
>
> Hey... this is fairly new. Somebody hacked XMMS so that it plays SHN
> files directly. The relevant info is in the text below.
>
> Note that you can also do this:
>
> paco@hydrofunk.org%> shorten -x <file>.shn - | play -t wav -
>
> from the command line to play a SHN without making the intermediate .WAV
> file. It works fine, but you don't get a nice GUI or the ability to
> pause, ffwd, or rewind the audio.
Just in case anybody out there isn't familiar with perl, I though I'd send
this email out to help them. Attached is my script for playing SHNs out
of directories or off of a CD.
To use it, put it in your path somewhere (make sure it's executable!), and
type:
shnplay /my/shn/file/directory/or/CDROM/path
That's is. It will play each file with a ".shn" extention in that
directory without making big WAV files as an intermediate step.
SInce the shorten algorithm is so fast, playing SHN files like this only
uses up about 10% of my CPU. (550MHz Athlon.)
BTW: it's nice to have a topic on this mailing list aside from "how do I
get this card working" or "is there planned support for this card" and the
like. Those are all good posts to this list, but we never really have too
many actual discussions about stuff. We just help each other make the
boxes make noise.
next prev parent reply other threads:[~2000-06-20 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-17 18:33 [linux-audio-dev] Re: Multimedia compression John Lazzaro
2000-06-19 18:50 ` Juhana Sadeharju
2000-06-20 11:54 ` Benno Senoner
2000-06-20 22:28 ` Dustin Barlow
2000-06-20 22:40 ` paco
2000-06-20 23:02 ` paco [this message]
2000-06-20 23:04 ` 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-96200429928838@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