Hi! I want to use Flac 1.0.4. I also want to have VorbisComment Tags.

which command line should I use in EAC?

And what is "Padding"? free space for further tags? and how big should that space be? 4096 bytes?

Look at the bottom of this page:

http://www.saunalahti.fi/~cse/EAC/



If you don't use padding the entire file will have to be rewritten if you change the tags. This will be a major pain for a ~400 MB file. Around 1024 bytes of padding should be enough. Add the following to the commandline:

is -P 1024 the same as --padding=1024??


and what's up with replaygain in Flac 1.0.5?

Yes, -P is the same.



Josh is adding relaygain support in 1.0.5.

and how much space will replaygain need? is a padding of 1024 bytes still enough??

OT:
political statements do not belong into a signature if you ask me

sorry - but nobody except the germans would understand this.

I'll correct this.

ReplayGain will require about 100 bytes to store the Vorbis comments.

flac 1.0.5 will also allow you to import cuesheets and store them in a metadata block if you do whole CD rips. The size of this block is still in flux while I figure out the format, and it will vary based on the size of the CD TOC (number of tracks), but if you are ripping whole CDs I would use around 8k padding if you plan to add cuesheets later.

Josh

"flac 1.0.5 will also allow you to import cuesheets and store them in a metadata block if you do whole CD rips"

This is great news Josh but I have a question.

Say, for example, that I encode a CD with 10 tracks and each track is listed to the file's cuesheet. Can I decode just a particular track of the album to a wave file (say track 5) without decompressing the whole file first? If so, this would be great on on demand mp3 encoding.

Thanks!

Agent69

Josh, I have another question. You've stated that FLAC 1.0.5 will allow ReplayGain (for playback), but will it allow the FLAC file to be decoded as a ReplayGained WAV? (That is, could I decode the FLAC file once as "album" and a second time as "track," and automatically have WAV files of differing volume? Or would the decoding process be restricted to the original, unmodified WAV?)

Also, will FLAC 1.0.5 improve upon FLAC's compression levels? If anyone is considering a massive transcoding project, will the new version offer enough of an improvement to warrant holding off until its release?

- M.

I strongly doubt it... The format is finished, note the 1.x version number... Unless you want CUE sheet support, you can start archiving right now...

Ooh, good idea. flac already has --skip and I am adding --until, so a --cue option could just look at the cuesheet and transform itself into the proper --skip and --until values.



I am real hesitant to add any lossy-type options to flac. The code that actually does that is in a convenience library used by the plugins (see src/plugin_common/replaygain_synthesis.c in CVS), so you could probably roll your own pretty easily.



There are no new compression techniques and I don't know of any that are asymmetric enough. I considered incorporating techniques from Monkey's Audio for just PC use but dropped the idea for several reasons. In the absence of any other great and unpatented ideas I will probably keep hammering on features. Monty has some ideas which we may experiment with in the future but I wouldn't hold back using flac for that chance.

After flac 1.0.4 went out I did make an optional 64-bit data path through the analysis and synthesis stages; the increased accuracy there leads to better compression of 24-bit files. That will be in flac 1.0.5.

Josh