similar to: Fwd: [flac:bugs] #407 Error in md5.c

lvqcl wrote: >>> Win_utf8 stuff should not be included in libflac since it's only to be >>> used by the flac.exe frontend. It is not needed by other programs nor >>> would they benefit from it without doing the extra work of converting >>> their ansi filenames and functions to utf-8. >>> >>>> Version 2 of my patch attached, which fixes

Hi all, I finally managed to bite the bullet and roll a pre-release. Its here: http://downloads.xiph.org/releases/flac/beta/ I have personally tested this code on: x86-linux x86_64-linux powerpc-linux I have not yet done any work on making sure the changelog is up-to-date. That will be done between now and the release. What I'm after now is testing of this source tarball

The patch changes flac_snprintf (in src/share/grabbag/snprintf.c) and its copy local_snprintf (src/libFLAC/metadata_iterators.c). It also adds flac_vsnprintf (src/share/grabbag/snprintf.c) and its copy local_vsnprintf (src/share/win_utf8_io/win_utf8_io.c). And it changes stats_print_info in src/flac/utils.c so it uses flac_vsnprintf instead of vsnprintf. Return value checking becomes

Here's the fix for another problem in metadata_iterators.c: it is possible for libLFAC to create too big padding metadata block -- a) when it merges existing padding blocks b) when it expands padding block during metadata changes. THe result is corrupted FLAC file. The patch should fix the problem. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix3.patch

I can't figure out how to verify flac md5 signatures. The docs say flac does an md5 over the unencoded audio data, but I can't reproduce it. I'm using flac 1.0.2 and Ron Rivest's reference md5 implementation. $ md5 temp.wav MD5 (temp.wav) = a7c92c4a656b2be2582f77c51b68a623 $ flac temp.wav $ metaflac temp.flac file: temp.flac METADATA block #0 ... MD5 signature:

Hello, I have proposed to WebM to use FLAC in a future version. Since FLAC was designed a decade ago, I was wondering if there were any new compression techniques that FLAC could use in a new version to improve compression ratios. If so, it would be worth synchronising with WebM for compatibility reasons. Here's the WebM discussion:

Janne Hyv?rinen wrote: > Patch v2, now handles more malformed cases. Original patch was for a > file for which I had a sample from a user but this allows handling some > manually broken test cases. Err, I'm getting warning messages on that patch: CC metadata_iterators.lo metadata_iterators.c: In function ?read_metadata_block_data_vorbis_comment_cb_?:

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/7/25, Josh Coalson <xflac@yahoo.com>: > > > > --- Harry Sack <tranzedude@gmail.com> wrote: > > > 2007/7/25, Harry Sack <tranzedude@gmail.com>: > > > > > > > > Hi > > > > > > > > I have downloaded a FLAC file somewhere and when trying to > decode

Perhaps update the codec to handle 32 bit files while remaining the same otherwise? Dennis Brunnenmeyer FULL FIDELITY MUSIC ------------------------------------------------------------------------ On 6/19/2012 12:00 PM, flac-dev-request at xiph.org wrote: > Send flac-dev mailing list submissions to > flac-dev at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/7/25, Harry Sack <tranzedude@gmail.com>: > > > > Hi > > > > I have downloaded a FLAC file somewhere and when trying to decode > it to > > WAV it gives the error message: ERROR, MD5 signature mismatch > > So my question is now: are FLAC files that give the error message > above > >

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/7/27, Josh Coalson <xflac@yahoo.com>: > > > > > > > But how is it possible then the FLAC encoder allows files which > have > > > a bad > > > resulting MD5 to be encoded? Is it because of the bad ram, ... > this > > > incorrect MD5 is not detected during encoding? > > >

2013/5/15 Ulrich Klauer <ulrich at chirlu.de> > Felix Homann wrote: > > > Yes, HAVE_SYS_PARAM_H is set in config.h: > > OK ... Yet still I don't see how a change in > src/libFLAC/include/private/macros.h could affect src/flac/utils.c in > any way. > > Anyone got an idea? I haven't spend too much attention to the errors when bisecting, sorry! The

Hi I have downloaded a FLAC file somewhere and when trying to decode it to WAV it gives the error message: ERROR, MD5 signature mismatch So my question is now: are FLAC files that give the error message above still decodable to WAV (and how can you do this, because flac.exe doesn't want to decode the file), even if there is a MD5 signature mismatch, or is this not possible at all? thx

Hi all, Second and hopefully final pre-release is here: http://downloads.xiph.org/releases/flac/beta/ I have personally tested this code on: x86-linux x86_64-linux powerpc-linux armhf-linux i386-freebsd9.1 i386-openbsd5.2 I also cross-compiled from Linux to 32 bit Windows and the compile ran to completion (the test suite requires a bunch of hacking before it can

Here's a patch to allow flac and metaflac handle files with malformed vorbiscomment metadata block. -------------- next part -------------- diff --git a/src/libFLAC/metadata_iterators.c b/src/libFLAC/metadata_iterators.c index d50df39..39cb276 100644 --- a/src/libFLAC/metadata_iterators.c +++ b/src/libFLAC/metadata_iterators.c @@ -78,7 +78,7 @@ static FLAC__Metadata_SimpleIteratorStatus

JonY wrote: > What is your link test checking and how does it fail? My m4 macro is really simple, TRY_LINK a simple program with the stack protect CFLAGS: AC_DEFUN([XIPH_GCC_STACK_PROTECTOR], [AC_LANG_ASSERT(C) AC_MSG_CHECKING([if $CC supports stack smash protection]) xiph_stack_check_old_cflags="$CFLAGS" SSP_FLAGS="-fstack-protector --param ssp-buffer-size=4"

hi, according to the FAQ flac supports multichannel formats. i had no luck with 1.1.4 though ( "Untitled.aif: ERROR: unsupported number channels 8 for AIFF" ), i guess that feature was added in 1.2? unfortunately, the binary for 1.2 does not run on OS X 10.4 (says libiconv is too old). i removed libiconv and reinstalled that from source, but then flac 1.2.1 just prints

Op 07-02-12 19:50, Ralph Giles schreef: > Basically the audio is chopped into a blocks and each block is coded > either uncompressed, as a constant value (good for silence), or with > linear predictive coding plus a rice-coded residual. I don't know how > the encoder decides where to put the block boundaries. AFAIK, FLAC uses a fixed block length so block boundaries are just put

Ralph, for Mac OS you should download either the Unarchiver which is free, or Entrophy which is what I use, but it costs like $15 I believe, both support decompressing .7z and Entrophy supports compressing TO .7z On Mon, May 6, 2013 at 3:00 PM, <flac-dev-request at xiph.org> wrote: > Send flac-dev mailing list submissions to > flac-dev at xiph.org > > To subscribe or

Hi i have seen that the dbPowerAmp ripping and encoding software supports a new so-called "FLAC uncompressed" format, e.g. http://www.audiostream.com/content/dbpoweramps-flac-lossless-uncompressed-wish-come-true i know only the normal flac compression levels from 0 to 8. have i missed an option on the flac comamnd line tool or how could i achieve that on the linux command line flac