From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CD ripper that generates song titles?
Date: Wed, 26 Aug 2015 13:16:08 -0700 [thread overview]
Message-ID: <55DE1E88.3060206@gmail.com> (raw)
In-Reply-To: <20150826200610.GA22849@waltdnes.org>
On 08/26/2015 01:06 PM, Walter Dnes wrote:
> I went to the CNE (Canadian National Exhibition) yesterday and
> indulged in a buying spree of 18 CD sets of my fave music (basically
> anything pop/rock/country pre-Beatles). I now have over 20 CDs that I
> want to rip to flac eventually. I dread the gruntwork in renaming
> tracks like track01.cdda.wav, etc. What Gentoo ebuilds are there for
> stuff that'll get ahold of track titles? Is it in the form of metadata
> on the CD?
>
I don't believe there's metadata on the CD outside of cd-text, which is
very limited.
I've messed around quite a bit with ripping on linux (although not in
the last 1-2 years) and eventually just gave up and ran EAC under wine.
EAC uses the album information on the CD to look up track lists on the
internet. Ripping and tagging are done in one step this way.
Outside of that, you can use something like EasyTAG to tag the tracks
after they are ripped. You can also use it to search databases on the
internet to get tags. However, with really new or obscure albums they
may not exist - you might have to tag them manually anyway.
Dan
next prev parent reply other threads:[~2015-08-26 20:16 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 20:06 [gentoo-user] CD ripper that generates song titles? Walter Dnes
2015-08-26 20:16 ` Daniel Frey [this message]
2015-08-26 20:38 ` covici
2015-08-26 20:49 ` Heiko Baums
2015-08-26 21:01 ` Marc Joliet
2015-08-27 11:28 ` Joerg Schilling
2015-08-27 23:48 ` wabenbau
2015-08-26 20:53 ` wabenbau
2015-08-26 20:58 ` Marc Joliet
2015-08-26 21:04 ` Emanuele Rusconi
2015-08-26 22:53 ` Walter Dnes
2015-08-27 11:37 ` Joerg Schilling
2015-08-27 19:42 ` Walter Dnes
2015-08-27 21:00 ` Neil Bothwick
2015-08-29 1:09 ` Walter Dnes
2015-08-29 9:38 ` Neil Bothwick
2015-08-30 0:20 ` Walter Dnes
2015-08-30 10:46 ` Neil Bothwick
2015-08-30 17:39 ` [gentoo-user] " James
2015-08-31 16:40 ` [gentoo-user] " Stroller
2015-08-31 22:21 ` Alan McKinnon
2015-09-01 3:22 ` Walter Dnes
2015-08-26 21:04 ` Fernando Rodriguez
2015-08-27 11:30 ` Joerg Schilling
2015-08-26 21:12 ` [gentoo-user] " Grant Edwards
2015-08-26 21:40 ` [gentoo-user] " Neil Bothwick
2015-08-26 22:50 ` Alex Corkwell
2015-08-27 3:42 ` Daniel Frey
2015-09-07 23:45 ` covici
2015-09-08 0:49 ` Fernando Rodriguez
2015-09-08 2:51 ` covici
2015-09-08 3:17 ` Fernando Rodriguez
2015-09-08 4:09 ` covici
2015-09-08 5:02 ` Fernando Rodriguez
2015-09-08 7:09 ` covici
2015-09-08 5:59 ` Fernando Rodriguez
2015-09-08 6:05 ` Fernando Rodriguez
2015-08-27 4:14 ` Alan McKinnon
2015-08-27 9:53 ` Neil Bothwick
2015-08-27 14:43 ` Alan McKinnon
2015-08-27 17:29 ` Mick
2015-08-27 18:16 ` Alan Grimes
2015-08-28 1:03 ` [gentoo-user] " James
2015-08-27 18:56 ` [gentoo-user] " Neil Bothwick
2015-08-27 19:07 ` Todd Goodman
2015-08-28 5:03 ` Alan McKinnon
2015-08-28 8:04 ` Neil Bothwick
2015-08-27 11:24 ` Joerg Schilling
2015-08-28 6:15 ` Justin Findlay
-- strict thread matches above, loose matches on Subject: below --
2015-08-27 20:06 Schilling, Jörg
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=55DE1E88.3060206@gmail.com \
--to=djqfrey@gmail.com \
--cc=gentoo-user@lists.gentoo.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