Package: abcde
Version: 2.3.99.6-1
Severity: wishlist

I see that it is deliberate in the flac format that embedded Cue sheets do
not have track information like track names embedded in them:
http://flac.sourceforge.net/faq.html#general__no_cuesheet_tags

OK, whatever.  However, given that abcde has all of the information already
and in fact generates an external cue file with artist and track names, I
think the information should be put *somewhere* even if it's just in random
comment tags in the flac file.  As it is right now, I end up with two files:

foo.flac.cue - Cue sheet with artist and track name info
foo.flac - Has cue sheet with only track info

If I:
metaflac --remove-tag=CUESHEET foo.flac
metaflac --import-cuesheet-from=foo.flac.cue foo.flac
metaflac --export-cuesheet-to=foo.flac.cue2 foo.flac
then foo.flac.cue2 is missing the extra information in foo.flac.cue

Arguably this is a problem with metaflac - maybe metaflac
--import-cuefile-from should (optionally?) write auxilary track info to
comments, but I don't know what the right answer is.  The more straight
forward answer would seem to be that abcde should manually insert tags for
each track; I don' tknow what the format of this would be however.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages abcde depends on:
ii  cd-discid             0.9-1              CDDB DiscID utility
ii  cdparanoia            3.10+debian~pre0-6 audio extraction tool for sampling
ii  flac                  1.2.1-1            Free Lossless Audio Codec - comman
ii  vorbis-tools          1.1.1-15           several Ogg Vorbis tools
ii  wget                  1.10.2-3           retrieves files from the web

abcde recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to