just out of curiosity does anyone here go all willy nilly and re rip all their cds with each new flac version just to stay "bleeding edge"?
Thanks romor, the pre2 is working fine for me. The ref lib is 1.2.1xxx, not 1.3xxx?
Also why the date is up to 2009 and not 2013?
Will this new release support compressing multiple audio tracks / files simultaneously with multicore CPUs natively?
Quote from: SpaceAgeHero on 11 March, 2013, 03:57:17 AMWill this new release support compressing multiple audio tracks / files simultaneously with multicore CPUs natively?No, for features like that you should use other encoders.
Considering you can't use multiple cores to encode a single track
Quote from: Maurits on 11 March, 2013, 06:24:48 AMConsidering you can't use multiple cores to encode a single trackWhy? Afaik FLAC encoding is easy to parallelize.
Quote from: C.R.Helmrich on 04 March, 2013, 06:08:13 PMI'm just wondering whether 7- and 8-channel support is the only new feature for end users like me...Aside from lots of bug fixes, cleanups and harderning, a few features were added.- adding ReplayGain support for 88.2kHz, 96kHz, 176.4kHz and 192kHz files to metaflac- while it was already present in FLAC 1.2.1, --ignore-chunk-sizes can be used to encode malformed WAV-files (i.e. > 4GB) and this option is now present in the documentation- support for Wave64 and RIFF64 has been addedI think that's it, but I might have missed something. Here's the changelog: https://git.xiph.org/?p=flac.git;a=shortlog
I'm just wondering whether 7- and 8-channel support is the only new feature for end users like me...
That's quite a shift. Do you have a suspect?
valid_bits WavPack, TAK, OptimFrog FLAC16 453f0af141959d709cccdc4723ff77ec 00b0bff6862b518452b46ad994cbde11 (the same as for 16-bit file)17 453f0af141959d709cccdc4723ff77ec 25234a864c084eb6c23c5f61ce5fdfc418 453f0af141959d709cccdc4723ff77ec c207d52c70f3fda72595864f3d133f3519 453f0af141959d709cccdc4723ff77ec 4b26f915fe3775ea165e58ba4fc4b1cd20 453f0af141959d709cccdc4723ff77ec daa325b376bfa803c849636fa1de070421 453f0af141959d709cccdc4723ff77ec 3d0670388b6919ab3ac79301b5c1999622 453f0af141959d709cccdc4723ff77ec cac12a2a39c14e20df4716f34ea145b723 453f0af141959d709cccdc4723ff77ec 086a82a505fac96241b50fd67c925f4524 453f0af141959d709cccdc4723ff77ec 453f0af141959d709cccdc4723ff77ec (the same as in other encoders)
Anybody knows how FLAC calculates MD5?
When ValidBitsPerSample=16: yes, FLAC just throws away these padding bytes. But when ValidBitsPerSample=17...24 then FLAC doesn't discard bits but simply shifts all input samples by (BitsPerSample - ValidBitsPerSample) bits and only then calculates MD5.