cueprint/cuetag: no "DATE" and "GENRE" tags are read/written from/to audiofiles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cuetools (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
In .cue files DATE and GENRE tags are stored as "comments" (strings begin with "REM ... " ).
E.g.:
REM GENRE "Heavy Metal"
REM DATE 1998
PERFORMER "....."
And there are two problems with this:
1) cueprint doesn't treat these fields as tags (because of cue-standard?).
2) cuetag doesn't properly tag audiofiles (because of no output of these tags from cueprint)
I've made a hack in cuetag to read these two tags directly from .cue file.
Now DATE and GENRE tags are supported (only in ogg/flac files).
Maybe this breaks something. I don't know. I've only tested this on .flac files.
P.S.: looks like problem exists in Ubuntu 11.11 too.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: cuetools 1.3.1-9 [modified: usr/bin/cuetag]
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
Architecture: amd64
Date: Sun Nov 27 22:36:00 2011
ProcEnviron:
LANGUAGE=ru_UA:ru
PATH=(custom, no user)
LANG=ru_UA.UTF-8
SHELL=/bin/bash
SourcePackage: cuetools
UpgradeStatus: Upgraded to natty on 2011-05-04 (207 days ago)
description: | updated |
summary: |
- cuetag: no "DATE" and "GENRE" tags are written to audiofiles + cueprint/cuetag: no "DATE" and "GENRE" tags are read/written from/to + audiofiles |
description: | updated |
The attachment "cuetag.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.
[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]