similar to: Play Time of FLAC Files

Yes, it's finally here. See the homepage for details, but here's a summary: - 10-15% decoder speedup - 24-bit input support restored - more robust plugins - new metadata block for Vorbis-style tags - vastly improved metadata editor - fixed bug with pipes and Windows - new libFLAC++, a C++ object wrapper around libFLAC - new metadata editing interface in libFLAC and libFLAC++ - and

Hello all, I?m trying to use flac and metaflac as tooling to analyze the generated FLAC files of a new encoder implementation. However, while my own third-party decoder can handle the output just fine, flac, metaflac, and other tools discard the output since the frame checksum (footer CRC-16) is invalid. This is expected, since I have no checksum generation implemented apart from the frame

Hi, Is it possible for you to compile flac/metaflac yourself? Then you'll only need to remove a few lines, namely these 4: https://github.com/xiph/flac/blob/28e4f0528c76b296c561e922ba67d43751990599/src/libFLAC/stream_decoder.c#L2118-L2121 and these 7: https://github.com/xiph/flac/blob/28e4f0528c76b296c561e922ba67d43751990599/src/libFLAC/stream_decoder.c#L2141-L2147 As you can see these lines

Hello, I'm looking into storing FLAC audio in Matroska and I have a few questions. 1. Can I use libflac to extract the compressed frames? Or will I need to write up a simple file parser? 2. What is required to decode the frames? From the docs I understand that you need the FRAME and you may need the METADATA_BLOCK. Thanks, Jory Stone jcsston@toughguy.net Matroska, the new,

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

First, Thank you for your answers. I using the following code to try simply decode a flac file and write the decoded data raw PCM file. The resulting file is just noise and pops, so is the decoded data in a different format than PCM? struct flacData { FILE *inputFile; FILE *outputFile; char *filename; }; FLAC__StreamDecoderReadStatus flac_DecoderReadCallback(const FLAC__StreamDecoder

So the right way to do it -- it seemed to work when I tried it, at least -- is metaflac --remove-all --dont-use-padding filename.flac ? I guess that these features make it more imperative than ever to watch the timestamps and not to validate a FLAC with an MD5 that is older than the FLAC is.

Josh Coalson <xflac@yahoo.com> wrote: > --- Scott F <graue@oceanbase.org> wrote: > > > If I use flac to encode with the --replay-gain > > option, I get a warning about the --no-padding > > option... > > > > "NOTE: --replay-gain may leave a small PADDING block even with > > --no-padding" > > > > ...even though I'm

I have some FLACs that have STREAMINFO that looks like this: METADATA block #0 type: 0 (STREAMINFO) is last: false length: 34 minumum blocksize: 4608 samples maximum blocksize: 4608 samples minimum framesize: 0 bytes maximum framesize: 0 bytes sample_rate: 44100 Hz channels: 2 bits-per-sample: 16 total samples: 0 MD5 signature: 00000000000000000000000000000000 (This came

Op zo 13 okt 2024 om 22:33 schreef Stefan Oltmanns <stefan-oltmanns at gmx.net>: > > Is the seektable written at the beginning of the file in the metadata > block or can there also be a second metadata block at the end? > Only at the start of the file. > > If it's at the beginning, would it possible to reserve space for N seek > points and during encoding remember

Firstly, a big thank-you to Josh for FLAC. Someone mentioned it in a post on Slashdot, so I came over to sourceforge for a look-see. This is just the sort of thing I've been looking for. Can anyone relate any general tips for using flac on Windows for the purpose of archiving cd's? If I can nail down a solid, easy-to-use process, I'm happy to write it up and contribute it to the

Hi all, As people may have seen there's a pre-release here: http://downloads.xiph.org/releases/flac/beta/ Specifically: flac-1.3.1pre1.tar.xz : The source code flac-1.3.1pre1-win.zip : Windows 32 and 64 bit binaries Please test. I'm particularly interested in hearing about the windows binaries which were cross compiled from Linux to Windows. Unfortunately there is a bug

Hi, I am new to this mailing list. I am adding FLAC support to the SLIMP3 player (http://www.slimdevices.com) and I had two questions about utilizing the format. The SLIMP3 player is a network mp3 player with an open source server written in perl. All audio must be re-encoded to the mp3 format before the player can use it. 1. Do any perl modules exist to read and/or write the metadata in a FLAC

So, let's provide some information then :-) ---------------------------------------------------------------------------------------------- soa2ii at thor /mnt/files/music/Slime/Alle gegen Alle $ flac -aF 02\ St?rtebecker.flac flac 1.2.1, Copyright (C) 2000,2001,2002,2003,2004,2005,2006,2007 Josh Coalson flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome

If I use flac to encode with the --replay-gain option, I get a warning about the --no-padding option... "NOTE: --replay-gain may leave a small PADDING block even with --no-padding" ...even though I'm not using --no-padding. And the file does end up with a small padding block, so changing tags is slow. I'd fixed this bug in my own copy of flac 1.1.4, but forgot to submit the

Hi all, The latest pre-release is here: http://downloads.xiph.org/releases/flac/beta/flac-1.3.0pre3.tar.xz but there will probably need to be at least one more. I've tested this on x86_64-linux powerpc-linux i386-openbsd5.2 i386-freebsd9 The majority of changes since the last pre-release is the addition of Janne Hyv?rinen's utf8 I/O functionality. Janne's

I think there is another major issue for me: In METADATA_BLOCK_STREAMINFO the field for the length is only 36 bit, that's not even half an hour at 40 MHz sample rate, resulting in that the encoder sets it to 0 for longer captures. In the seekpoint the sample number is 64 bit, which is more than enough. But how does the decoder handle the seektable when the total number of samples is unknown?

Hi, I would like to clear something up about Sample Rate, If the Frame header can look to the metadata block streaminfo for sample rate what (if anything limits it to 655350Hz)? Can all frame headers not just point to streaminfo and it be specified in streaminfo as all 1s ie 2^20-1 = 1,048,575Hz? It would be really good to be able to use 1MHz and beyond for some of my/our work. Does anything

Hello, I'm currently doing a little music player using libflac and libao. What I've currently done works as it should, but I have a problem where only one metadata block is detected, even if there are more (it doesn't have the last attribute set to true). This is using flac 1.3.2 on Gentoo amd64. The main code file is attached, it mainly follows the examples given with the libflac

Replying to myself once again, since I seem to have found the answer I was looking for. Sorry for the noise. It seems CRAM is indeed misusing FLAC, since stated in the Notes section of the FLAC format for the FRAME_HEADER is the fact that only block size values 0110 and 0111 can be used for variable block size data (i.e., the block size is specified as an 8 or 16 bit value at the end of the