#100 problem parsing cuesheet with CATALOG entry

[Anonymous]

passing a cuesheet to the flac command line will fail
if the cuesheet contains a CATALOG line. The error
suggests that the problem is that the CATALOG number is
the wrong length, but it's not. Removing the CATALOG
line from the cuesheet causes the encoder to parse the
remainder correctly, but it would be nice to not have
to do this.

flac --cuesheet=/tmp/cd.cue ...
ERROR parsing cuesheet "/tmp/cd.cue" on line 1: CD-DA
CATALOG number must be 13 decimal digits

the line in the cuesheet looks like this...
CATALOG "0075994576923"

[Josh Coalson]

Logged In: YES
user_id=78173

The problem is the quotes. It should work without them.
Not sure if quoting is legal; what program generated the
cuesheet?

Josh

[Nobody/Anonymous]

Logged In: NO

the cuesheet was transformed from a toc. the original toc
was generated by cdrdao and also contains the quotes around
the catalog number. the cuetools programe "cueconvert" was
used to turn the toc into a cuesheet. (the toc2cue that
comes with cdrdao would only ever generate 0 byte files for me.)

sure enough, if I remove the quotes by hand, flac processes
the file ok. There are other quoted values in the cue/toc
but all are for fields that flac is going to ignore (file,
cd-text, etc.)

where can we find out whether quotes are supposed to be allowed?

[Josh Coalson]

Logged In: YES
user_id=78173

Looking into this, it appears there is no real standard.
I'll add supporting for quotes in CATALOG to the parser.
Does it quote anything else? (like TRACK, INDEX, ISRC,
FLAGS)

Josh

[Nobody/Anonymous]

Logged In: NO

Apart from CATALOG, this particular program doesn't seem to
quote any of the values that flac pays attention to.
Although some other program might, so it might not hurt to
parse it either way (assuming it's not that much work to add).

I've also mailed the cuetools folks about this, but haven't
heard back from them yet.

for what it's worth, the cdrdao/cuetools combination
produces a cue sheet that does quote the following:
CATALOG
TITLE
PERFORMER
MESSAGE
FILE (filename but not datatype)

and it does not quote the following:
TRACK
ISRC
INDEX

I haven't seen it generate a cuesheet that contains the
FLAGS keyword yet, so I can't say how it handles it.

Thanks for looking into this. And thanks for creating such a
great program.

[Josh Coalson]

Logged In: YES
user_id=78173

OK, finally checked in a fix for this. Will close
the bug when the next release comes out.

Josh