The man page states this command will produce a 1-track FLAC file with embedded cue sheet:
$ abcde -1 -o flac -a default,cue
That produces a separate cue file, but if the man page is correct we assume there is also a cue sheet embedded in the '.flac' file. The man page also states that this command may be used to produce a separate file for each track in OGG format:
$ abcde -d album.flac -o ogg
All metadata is missing as that second command executes. The user must painstakingly retype all the track names and metadata.
Also, perhaps this is a second bug: it attempts to create 149 tracks when there is much fewer tracks.
I can confirm this behavior with the cue file. I would expect that metadata from the embedded cue file would be used to populate the CDDB entry when extracting titles from the singletrack FLAC file. Is this not the case?
My current workaround is to use a local CDDB repository that caches the entry so I don't have to type it again later on.
(In reply to Chris Chapman from comment #1)
> My current workaround is to use a local CDDB repository that caches the
> entry so I don't have to type it again later on.
A quotation from FLAC's faqs that might shed some more light on this issue <https://xiph.org/flac/faq.html#general__no_cuesheet_tags>:
> Why aren't PERFORMER/TITLE/etc tags stored in the FLAC CUESHEET block?
> For FLAC the intention is that applications can calculate the CDDB or CDindex
> ID from the CUESHEET block and look it up in an online or local database just
> like CD rippers and players do. But if you really want it in the file itself,
> the track metadata should be stored separate from the CUESHEET, and already
> can be because of FLAC's metadata system. There just isn't a method specified
> yet ...
It appears that currently abcde only imports the cue sheet into the FLAC CUESHEET block and does not include the CDDB entry as a FLAC metadata tag. So, from what I am finding, it seems that when producing separate files for each track, the two alternatives would be to either fetch the entry from a CDDB repository or to come up with a convention for storing CDDB data in a FLAC metadata tag and processing that tag if it exists (later on in the faq answer above they mention Foobar2000 doing this, but I am not an expert in this area and may be unaware of any further standards work for this).