similar to: What is the magic code for Ogg FLAC?

While testing the new vcut, some of the early results had badly framed headers. I actually didn't notice it at first, because I was testing with oggz-validate, but ogginfo does identify the problem: "WARNING: Vorbis stream X does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos" Conrad (or someone else) may want to

On 5/26/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: >> char[8]: 'kate\0\0\0\0' | kate > > This is incorrect, should be: > > char[9]: '\x80kate\0\0\0\0' | kate The last one is how it's listed on ogginfo code, but the first one (char[8]) is how it's described in the wiki page. I thought the

Hello list, We have recently introduced the codecs (optional) parameter on the Ogg media types for easier identification of encapsulated codecs in conditions were it's not feasable to examine the streams directly. I received a comment from the IESG that we should have some sort of list to describe how Ogg mapping strings translate to codec parameter strings, so I went ahead and compiled a

2008/5/29 Ralph Giles <giles at xiph.org>: > On 28-May-08, at 6:20 PM, Conrad Parker wrote: > >> /* TODO: this should check against 42 for the relevant version numbers */ >> if (op->bytes < 41) return 0; > > I gather this means the USE_THEORA_PRE_ALPHA_3_FORMAT #if should instead be > based on the length of the header packet. I'm not sure why you're

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

On 4/11/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: > how (or do you mean ogg/mng or spots) ? People want an official standard on how to embed JPEG/PNG in single stream Vorbis files, because one of the extensions/hacks of MP3 ID3 allows it. > uuencode ^_^ Hmm...

Oh, hey, I'm more or less on the final stages of drafting the registration proposal that will be submitted to the IETF. If you have comments, suggestions, fixes, anything, this is it. https://trac.xiph.org/browser/experimental/ivo/drafts/draft-xiph-rfc3534bis.txt -Ivo

Oh, hey, I'm more or less on the final stages of drafting the registration proposal that will be submitted to the IETF. If you have comments, suggestions, fixes, anything, this is it. https://trac.xiph.org/browser/experimental/ivo/drafts/draft-xiph-rfc3534bis.txt -Ivo

Josh Coalson <xflac@yahoo.com> wrote: > I think everything you need is here: > http://flac.sourceforge.net/ogg_mapping.html " Ivo Emanuel Gon?alves " <justivo@gmail.com> wrote: > I'd say it had enough info, but too much for what I needed. I ended > up finding the answer in oggenc/flac.c: it's "\177FLAC" not "fLaC" as > ogginfo

I have several corrupted ogg files; I believe they were created several years ago with grip, and that the corruption is not disk corruption but just something wrong with the encoder at the time. I would rather not have to re-rip these discs. The error I see with ogginfo is Warning: Hole in data (18000 bytes) found at approximate offset 702086827724505088 bytes. Corrupted ogg. Warning: Hole

On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On 4/11/08, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > > > uuencode ^_^ > > > > Hmm... > > Yes! A Vorbis Comment tag called ART or ALBUMART with a Base64 string > would do the trick and it would not choke existing players. No, vorbiscomments are meant to be

It obviously would be nice to have such a mode available, for e.g. DVD audio compression. Apparently, the list doesn''t tell me too much about it. My questions are: 1. What is the current status of the 5.1 channel coupling in Vorbis? 2. If I''ll be interested in participation in its development, what is the recommended reading? -------------- next part -------------- An HTML

I bumped the version number of vorbis-tools and am preparing it for an eventual release in a few days. A changelog of what's new may be found at [1]. Meanwhile, what's in SVN is a "Release Candidate" to find out if anything was broken since version 1.1.1. Report any (or lack of) problems you may find, so we'll be able to put out a new version of vorbis-tools. -Ivo [1]

Erik de Castro Lopo <mle+xiph@mega-nerd.com> wrote: > Martin Leese wrote: > > So what is "OggPCM"? I started this thread > > because I was puzzled why someone was > > changing a draft instead of the document > > itself. > > The original OggPCM was started by a person who really didn't > lnow what they were doing and wouldn't listen to

On 1/23/08, jaromil <jaromil@dyne.org> wrote: > nope. we have a freej specific mailinglist, see http://lists.dyne.org Ah, so sorry. > freej is statically including theora-mmx or offering to be dynamically > compiled to system-wide theora libraries (so the issue is then > delivered to the distribution) Most distros should be already using the latest beta, so that should

On 5/13/07, Brian Willoughby <brianw@sounds.wa.com> wrote: > If we ever reach this 64 GigaSample limit, the fact that FLAC is a > stream should allow multiple FLAC headers to be concatenated in a > single file - although that might be tricky. I believe you can do this with Ogg FLAC. The Ogg container manages the multiple FLAC streams. Theoretically, we'll never see limit

Is it all right to discuss CELT here? I haven't seen any specific mailing list for it yet. I would like to ask if someone could provide me one or two sample Ogg CELT files, so I could test detection in ogginfo. I know CELT content isn't really supposed to be around as files since it would lose all the format's latency advantages, but I assume people can create them if need be. -Ivo

The Xiph.Org Foundation announces the release of Theora 1.0. Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number

The Xiph.Org Foundation announces the release of Theora 1.0. Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number