From: Christopher Nielsen <cnielsen@pobox.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Where is mp3dec, pac4dec vorbisdec?
Date: Mon, 24 Jan 2005 17:55:45 -0800 [thread overview]
Message-ID: <20050125015545.GZ77074@cassie.foobarbaz.net> (raw)
In-Reply-To: <200501201829.j0KITTC08053@zamenhof.cs.utwente.nl>
there are several codec and frontend ports in /n/sources/cnielsen.
the following libraries:
libogg
libvorbis
libFLAC
libOggFLAC
libfaac
and the following frontends/utilities:
faac
oggenc
vorbiscomment
metaflac
flac
bladeenc
cuetools
oggdec and faad should be no-brianer ports. i'll see if i can
do them tonight and toss them up there, too.
On Thu, Jan 20, 2005 at 07:29:29PM +0100, Axel Belinfante wrote:
> > > This may concern with many others, not only myself, I thought. (-->Sape)
> > >
> > > Thanks Sape for your jukebox program.
> >
> > You're welcome. Pac4dec, regrettably, has not been released for
> > public consumption. Rob tried hard, some years ago, to allow it to
> > be made public, but the attempts failed. There are mp3 encoders
> > and decoders on Plan 9, ported from other platforms.
>
> Now that we have jukebox, and some ported decoders,
> would it make sense to agree on where they live on the system?
>
> The bell labs stuff (I think) all ends up in /sys/src/games,
> whereas the vorbis port (link below) ends up in /sys/src/cmd/audio
> at least last time I installed it which is some time ago.
>
>
> Below is my mp3dec.
> I have tried several players and left some garbage in the script :-(
>
> I added the cat and the dd to have some more buffering
> because my mp3 files are served over the network.
> In my experience, serving files from ken-fs worked fine,
> but I had some problems with u9fs (short gaps of silence)
> that went away after adding the cat.
> (I have also got my music files over the wlan, or even,
> from the office ken-fs and u9fs's to home).
>
> cpu% cat mp3dec
> #!/bin/rc
> # if (test -e /mnt/term/tmp/dev/audio) {
> ## cat $3 | minimad | sox -t .raw -w -r 44100 -c 2 -s - -t .au -
> # cat $3 | mpg123 -s - | sox -t .raw -w -r 44100 -c 2 -s - -t .au -
> #}
> #if not {
> ## cat $3 | minimad
> # cat $3 | mpg123 -s -
> cat $3 | dd -quiet 1 | dd -quiet 1 | madplay -q -o RAW:- -
> #}
>
> Same cat trick with vorbisdec.
> My realvorbisdec is the vorbisdec I took from any's port:
> http://www.cs.helsinki.fi/u/anyrhine/p9/
>
> cpu% cat vorbisdec
> #!/bin/rc
> cat| /bin/games/realvorbisdec
> cpu%
>
> Axel.
>
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
prev parent reply other threads:[~2005-01-25 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 8:51 Kenji Okamoto
2005-01-20 13:42 ` Sape Mullender
2005-01-20 18:29 ` Axel Belinfante
2005-01-21 1:15 ` Kenji Okamoto
2005-01-21 4:38 ` Kenji Okamoto
2005-01-25 1:55 ` Christopher Nielsen [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=20050125015545.GZ77074@cassie.foobarbaz.net \
--to=cnielsen@pobox.com \
--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).