Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: flac with embedded cuesheet (Read 2898 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

flac with embedded cuesheet

in my continued search for an elegant single file lossless solution...

i have been experimenting quite a bit with the embedded cuesheet function of flac.  i use eac's "copy image and create cuesheet" feature.  then the flac frontend to compress the wav, embed the cuesheet, and apply replaygain.  flac strips out the individual track info from the cuesheet in the process, but keeps artist and album data and stores the replaygain info. 

with the newest version of fb2k, the file is imported in the database with the correct artist and album tags and replaygain info, but bogus info for track names.

i then use the foo_freedb to fill in the missing track info and it works like a charm!  but, it only put the info in the database, and does not write any data to the tag itself.

my question - is there a way to copy the data from the database into the actual file tag, therefore allowing for file portability.  i have been reading through the archives and can't seem to find a definitive answer.  i believe that the file structure can support it (?vorbis?), but not sure how to accomplish.

brett

flac with embedded cuesheet

Reply #1 –
no bites?  is my goal achievable?

flac with embedded cuesheet

Reply #2 –
Sorry. This comes up fairly often, and there's no really good solution at this time. The FLAC format doesn't have an inbuilt way to tag individual tracks in a single-file album. You can define any tag you like, since it uses free-form Vorbis comments, but there are no players that would read that information in a useful way. The FLAC format also allows for "application" data blocks, and I've put some thought into how to use that to store per-track metadata, but I haven't done anything with it yet.

The other option is Matroska, which is a container format with a separate internal stream for metadata. It's coming along, but doesn't work with FLAC yet - and honestly, I haven't had much luck getting it to work with anything. I suspect, though, that it will someday be the solution for people like us, who want to have a single file that contains an entire album, with all of its metadata.