Josh Coalson wrote: >> Thus,... if I currently have my index-based wav files (that is EAC >> makes >> track-number.index-number.wav) from an cdda,.. and the corresponding >> CUE >> file (EAC writes it in min:sec:frame),... than I could use sox to >> concatenate the single files to one big file,.. >> encode it to flac with the CUE infos,.. >> And afterwards I'd be able to restore/decode it to the single files, >> right?! >> > as long as the ripping is not missing "pregap" (especially track 1 > index 0), which has to be set up a certain way in EAC, then yes. > you should try an experiment with one disc first. > Yes... I'm always having a special look for track 01 index 00 in EAC.... but if you use index-based extraction you'll get one file for each range.
>> btw: This is not the right place to ask,.. but is it planned to add a >> standard to ogg (and thus flac) like ogg comments,.. but for >> additional stuff like lyrics,.. or CD-cover art and so on? >> > FLAC uses the same tag standard as vorbis. ogg has no tag standard. > the vorbis standard does not mandate any tags, but has some > recommendations. There is one thing I forgot to ask last time.... when using that cue feature from flag,.. is it possible to store different tags (title, composer, etc) for each range? And if so how do I specify this on the command line? > I think the current convention by users is to > store lyrics in the LYRICS tag. cover art is not part of the tags, > it will go in the PICTURE metadata block in upcoming FLAC 1.1.3: > http://flac.cvs.sourceforge.net/*checkout*/flac/flac/doc/html/changelog.html > I assume that this could be added later via metaflac to already encoded files? btw: are there any other changes (e.g. in encoding strenght or so) that makes it worth waiting for 1.1.3? Thanks and best wishes, Chris. :-) _______________________________________________ Flac mailing list [email protected] http://lists.xiph.org/mailman/listinfo/flac
