similar to: How to handle multiple STREAMINFO blocks?

It's certainly best to honor what the specification says. My assumption is that a "stream" could also be a continuous broadcast, not just a file. With a hypothetical server streaming FLAC bitstreams, I would assume that the most recent STREAMINFO is valid until another one comes along. If you're writing a file player, then perhaps you can trust the spec and assume

Thank you very much! But how to deal with endianness in the case of bit stream? Some blocks (for example MinBlockSize) require 16bits (simply swap first and second), some block (e.g.MinFrameSize) require 3 byte-array to be reverted. Finally totalSamples is stored in 5 bytes ( only last 4 bits from first one byte are used). It was a real issue to make it little-endian (here is how I did it:

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

Hello Ilia, The FLAC format by nature is not a byte stream, it's a bit stream. Therefore, in order to parse it you need too build a bit-reading infrastructure. Eg. a class that accepts a byte stream, implements buffering, etc, etc, and supports reading a specified number of bits, not bytes as you are used to. There is quite a lot of bit logic there, but nothing too scary. Best Regards,

Using Trader's Little Helper 2.4.1.160 when testing some 16/96 FLAC files I run into the following error: "file is decodable without error, but flac fingerprint cannot be checked since it was unset in the streaminfo block." Is there an automatic checksum verification when testing/decoding? Is there any way to fix this, i.e. get rid of the error? Martin

On Jun 22, 2010, at 21:27, Ilia Ternovich wrote: > Thank you very much! But how to deal with endianness in the case of > bit stream? Some blocks (for example MinBlockSize) require 16bits > (simply swap first and second), some block (e.g.MinFrameSize) require > 3 byte-array to be reverted. > > Finally totalSamples is stored in 5 bytes ( only last 4 bits from > first one byte

Oops. I proofread my email a little too late. I corrected the example. Hopefully what I am suggesting is clear. Brian Willoughby Sound Consulting On Jun 22, 2010, at 22:15, Brian Willoughby wrote: > What you need to do is write a bitStream function. It should only > read each byte from the stream once and completely deal with all 8 > bits before reading the next byte. You

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 implementing custom flac metadata parser. Currently the very big trouble is to parse StreamInfo metadata block. According to specifications (http://flac.sourceforge.net/format.html#metadata_block_streaminfo) we've got 2 bytes fir minBlockSize, 2 bytes for maxBlock size, 3 + 3 bytes for min/max FrameSize. Now the interesting point -- sampleRate. number of channels, buts per

On 2006-03-09 (Thu) ,at 23:20:50 Josh Coalson wrote: > the vorbiscomments are not in the streaminfo. you want to do: > > FLAC::Metadata::VorbisComment tags; > if (FLAC::Metadata::get_tags("somefile.flac", tags)) { > FLAC::Metadata::VorbisComment::Entry entry = > tags->get_comment(tags->get_num_comments-1); //e.g. last tag > // do something with

On Mon, 2003-11-17 at 11:04, Josh Coalson wrote: > could you clarify your plan... are you thinking about > 1) encoding to a FLAC container and using metadata blocks > for everything that is not data? > 2) writing your own container? > > 1) seems kind of impractical to do in a general way. > I'm starting to also think that 2) is the best route. I was originally

Thanks for the quick response on the C++ thing. It would also be nice if the host program could correctly write the STREAMINFO block in the stream encoder metadata callback without having to know the specifics of the header format (or worry about endianness). How exactly to achieve this might take some thought, but what about this idea: 1. The correct way to respond to the metadata callback:

I've been implementing Ogg FLAC support in an editor I'm working on, and I must admit to being frustrated by the lack of support for the codec on the Ogg layer... and this is more than lacking granulepos. The codec's I've worked with, and my own (Writ), use Page 0 for general information about the codec. Specifically, the samplerate, bitrate, quality, number of channels, all

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

If compression level is not default (!=5), is it stored? If compression level is stored in some case, where I can find it? Frames number works OK according to your instructions. Thank you ----- Original Message ----- From: "Josh Coalson" <xflac at yahoo.com> To: "Santiago Jimeno" <sjimeno at ya.com>; <flac at xiph.org> Sent: Tuesday, January 27, 2009 7:43

Hi, I'm trying to write a FLAC decoder for my Java audio app. Can I ask a couple of questions to this list about the format? I think there are a couple of things not-quite-mentioned in the official spec. RICE CODING: Which order are Rice-coded numbers stored in? (a) [sign-bit][low-order bits]["k" zeroes][1] (b) [sign-bit]["k" zeroes][1][low-order bits] (c)

lvqcl wrote: > Martin Leese wrote: >> Why place restrictions on which speaker a >> user can use? ... >> Finally to answer your question, for a >> single-channel file, FLAC should accept any >> one of the three masks 0x00000001 (FL), >> 0x00000002 (FR), 0x00000004 (FC), plus any >> one of the 15 other single-bit masks, plus zero. Please note that the

Hello! I'm using the seekable stream decoder API of libFLAC 1.02 and I think that I found a possible bug in process_metadata(). The problem is as follows: I have a file which isn't a FLAC sample (it's actually an ACE archive) where process_metadata() returns TRUE. And even worse, the metadataCallback() is never called (which means process_metadata() succeeds, although no metadata is

i had the problem is flac 1.1.2 so upgraded to 1.1.4 but now the problem is just different. the wav file is from audacity, so i guess it is culprit for setting that format type 1 bit, but shouldn't this still work? i found in 1.1.2 (before i found 1.1.3 had the odd size fix judging by relnotes) that i could add a dummy byte to the end and this seems to fix my issue, just not cleanly. here

Hello, I have recently found a number of FLAC files that have a PICTURE block as the first metadata block in the file. From the format documentation, it mentions that the STREAMINFO block must be present as the first block. I'm guessing that someone somewhere is not playing nicely with the format, but I just wanted to confirm that this is incorrect so that I can fix the files if they