search for: metadata_blocks

I have a question about module-level METADATA_BLOCKs in the bitcode. There are currently two blocks with the METADATA_BLOCK id at module scope. The first has the module-level metadata values (consisting of some combination of METADATA_* record codes except for METADATA_KIND). The second consists only of METADATA_KIND records. The latter is used only...

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 everybody, I have a question about the following part of the METADATA_BLOCK_PICTURE specification. The components: Width, Height, Color Depth, and Colors Used don't provide an "unknown" value and seem to assume that the program encoding the METADATA_BLOCK will be aware of these components of the file. As these fields seem to just provide "extra" information (I'm

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

"Santiago Jimeno" wrote: > Flac files, as us knows, follows the Vorbis Tags system included in block 4 > Recently Vorbis has established the possibility to include picture files by > means of 2 Tags: COVERARTMIME AND COVERART. > To work therewith is quite easy. No. this in incorrect. The VorbisComment "COVERART" was only ever unofficial, and has been deprecated

--- Jory <jcsston@ToughGuy.net> wrote: > 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? I'm not sure I understand your question, but one unfortunate fact about native FLAC is that you cannot discover the frame

On Fri, 2 Feb 2001, Josh Coalson wrote: > sounds great. I've been thinking about adding a > 'what uses FLAC' set of links to the web page... > please keep me posted. The latest version of my cue+wav splitter supports .flac files. Hope to get it released this weekend. Will eventually be at: www.lameb.fsnet.co.uk It also supports .shn and .ape. I've seen shorten

OK Martin. Thank you for the explanations and for your time. I am writing a program that reads and writes all existent Tags types. It lacks only to end the edition (rewriting) of "Native" Flac and Matroska. Both cases for the same problem: the separation of Tags and Picture in different blocks. In Flac I resolved it, but now I have to add METADATA_BLOCK_PICTURE. Reading Vorbis

You said "With the exception of where to put a picture file, VorbisComments in a Vorbis stream are the same as VorbisComments in a FLAC stream." In METADATA_BLOCK_PICTURE case they would not be the same. Up to now we could exchange the complete block of VorbisComments. But with the addiction of METADATA_BLOCK_PICTURE doesn't happen this way. In Ogg files the METADATA_BLOCK_PICTURE

I seem to recall that changes in the second number indicated a minor change in the *format* of the file itself (for example, 1.1.x to 1.2.x introduced a new rice coding option used for 24-bit files). Are there any format changes that would justify that ? Otherwise, 1.2.2 would seem more appropriate, not to minimize the work that you are doing... Cheers, Pyt. http://www.mjuware.com On Sat, Jan

On Jan 12, 2013, at 05:30, Martijn van Beurden wrote: > On 12-01-13 08:23, pyth.flac-dev.5.pyt at spamgourmet.com wrote: >> I seem to recall that changes in the second number indicated a minor >> change in the *format* of the file itself (for example, 1.1.x to >> 1.2.x >> introduced a new rice coding option used for 24-bit files). > > Well, the only change in