search for: metadata_block_application

...w local components have been named and referenced in the FFV1 and Matroska documents). Thus “METADATA_BLOCK_HEADER” would be `Metadata Block Header` and expressed with that same case and quoting at each reference. I also suggest that the metadata block types such as “METADATA_BLOCK_STREAMINFO” and “METADATA_BLOCK_APPLICATION” simply be renamed as `Streaminfo Block` and `Application Block` and that each of those components be defined as being a `Metadata Block`. I may send a pull request for this soon but wanted to ask around in case there’s some reason for or advantage of the ALL_CAPS_WITH_UNDERSCORE_STYLE that I’m mi...

...depending on the implementation. I've > never heard of it before. If FLAC doesn't store the 'fmt ' chunk verbatim then it doesn't handle it. At the moment people can use WavPack (which does store the 'fmt ' chunk), and in the long term we could register an ID for a METADATA_BLOCK_APPLICATION. If you are interested in the ".amb" spec then the non-standard GUIDs are described at: http://dream.cs.bath.ac.uk/researchdev/wave-ex/bformat.html and the rest of the description is at: http://www.ambisonia.com/Members/mleese/file-format-for-b-format/ There are currently over 100 piec...

Not sure if this belongs here or in flac-dev. I am subscribed to both, so flop it over if fits better over there. Looking at the Changelog for FLAC 1.2.1 (17-Sep-2007), it says: "With the new --keep-foreign-metadata in flac, non-audio RIFF and AIFF chunks can be stored in FLAC files and recreated when decoding." Where can I find more detail on what is a

On 3/22/07, Brian Willoughby <brianw@sounds.wa.com> wrote: ... > But to return to your question, exactly what kind of "support" are > you looking for? I wasn't looking for any particular support, but just to see what support was there (if any). ... > I do not believe that there is any need for code specifically > supporting Ambisonics. FLAC supports conversion to

Hello all! (cc-ing the flac-dev list) I would like to give an update as to the recent CELLAR work on the FLAC specification. • Work has been done to make internal and external links more accurate and reliable. • 'Rice Coding' has been clarified as 'Exponential Golomb Coding.' • Clarifications have been made for binary representation. • Typos and other small changes have been