Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: Wes Hardaker <wjhardaker@ucdavis.edu>, ding@gnus.org
Subject: Re: all you MP3 people out there... a fix for lars!
Date: 30 Oct 1998 11:10:23 -0500	[thread overview]
Message-ID: <86d87a58uo.fsf@kramer-fast.bp.aventail.com> (raw)
In-Reply-To: Darren Stalder's message of "29 Oct 1998 12:55:37 -0800"

Darren Stalder <darren@u.washington.edu> writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Wes Hardaker, in an immanent manifestation of deity, wrote:
> >Willing?  Heck, thats what my "cdrec" script is currently written in.
> >Was there another alternative???
> 
> Okay.  I've gotten the impression on ding that if it ain't e-lisp, it
> ain't nuthin.  I need to make a recent change to cd->query and then I
> can send a snapshot to anyone that wants it.

  And for those that really do think if it aint-e-lisp, its crap, here's a
first pass at cddb.el.  It can use cdda2wav or cdparanoia to get the TOC
from the CD, computes the discid, and can either look up the CD in a local
CDDB database, or do it remotely.  It even works through my socks.el stuff, 
wheee. :)

  Try evaluating (cddb-get-entry) when you have a CD in the drive.  It will
pull back the XMCD style info.  Next on the list is actually parsing this
out.  I want to eventually have a suite of elisp scripts that will just
take a CD, convert the whole damn thing to mp3, and create an appropriate
.XAM file (the xaudio album format).

  Or perhaps just go all the way and write an MP3 player in elisp and make
the playlists, etc, controllable via custom, and album files in a nice easy 
to (read ...) format.

  Any interest? :)

-Bill P.


  reply	other threads:[~1998-10-30 16:10 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
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 [this message]
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=86d87a58uo.fsf@kramer-fast.bp.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@gnus.org \
    --cc=wjhardaker@ucdavis.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).