similar to: bitstream versioning

Hi List, Just batting a few ideas around here, but would it be possible to include in to the codec, estimation for common video artifacts that occur in the analogue world? For example, anything that's gone through a composite stage will likely have dot-crawl and false colour - if we can recognise this effect in the encoder, we can treat it as a special case. Other artifacts that come to

it appears your encoder/player do not yet reflece the changes rillian introduced wrt theora headers, which have been split into three parts -- header proper, comment, and tables (see toplevel.c). It's strange that your code works at all linked against the new libs; presumably since the tables still have the hard-coded values, if you encode & decode from the same lib compile you won't

ok now I see why we need another packet in the header. The first one is basically for ID purposes (theora_decode_header()). I've jammed my huffman trees in there but it sucks because I need them later on when I actually build the huffman tree structs (theora_decode_init, calls InitHuffmanSet()). At that point the original header packet is gone so I've been keeping it around in a buffer.

Hello, I´m just curious: How far is Theora from a bitstream freeze? From TheoraTodo: "Derf has come up with a number of suggestions for improving the flexibility of the bitstream based on his experimental encoder work. These will be implemented, if not entirely supported by the reference decoder, before alpha 3 is released." Are those changes supposed to be the last adjustments?

I hope this list is small enough for not beeing banned when introducing oneself. So... Hi, I just subscribed to the theora-lists. I'm from the XVID project, so I know a deal about video and MPEG-4 in particular, but nothing about Vorbis/Theora etc., That's why I'm here, because I'm interested in patent-free alternatives. I guess there is no documentation of the current status

Ok, we got it working with 176x144 resolution. The following string produced an image that was not falling behind too much for too long - basically a little when it was getting TONS of movement, and then catching up fast. "65 58 110 0 1 1 90 8 120 1 1 " Now, we need to get this working on a 320x240 resolution, too (as sadly VP3 does not support 160x120. Seems to be a little senseless,

Hello all, I've been working a little inside the Theora decoder when I found that it seems that many videos had the very same huffman tables encoded into their bitstreams (at least the ones that I could take my time to dissecate). I found that the tables are listed as TH_VP31_HUFF_CODES in the file huffenc.c. I tried to investigate a little bit more to see who was setting the bitstream

Hi, last week's thread about getting closer to a release fizzled out. The mailing list discussion and the TheoraTodo wiki item suggest the following are required for release: 1. freeze the theora logical bitstream format 2. complete the reference implementation tools 3. stablize the libtheora API 4. complete the documentation I'd like to suggest this as

Hi, So it took a little while to get here but VP3 through ffmpeg is finally starting to achieve viewable results. It partially works right now. Keyframes only. And monochrome. Oh, and the picture is upside down (something I did not realize about VP3 until I let it fly just now). Anyway, here is a picture of ffmpeg's VP3 decoder in action using xine:

Hullo, When people ask me what Vorbis's license terms are, I usually tell them that the bitstream format is in the public domain, that the reference libraries are licensed under a BSD-like license, and that the example programs are licensed under the GNU GPL. (Note the distinction between filespec and implementation here.) Meanwhile, Theora.org's FAQ doesn't say anything about the

Hello Theora developers, I'm doing some cursory research into Theora's IP status in preparation for asking Apple to reconsider the possibility of shipping an implementation. I have a few questions and I'm hoping knowledgeable people can help out. 1) What are the terms of any patent licenses or disclaimers, and do they have field of use restrictions or limitations on code for

Hi John, I'm forwarding this email to the relevant developer lists at Xiph.Org, where the format was created and where the experts gather. I'm certain there is a design reason for putting the bos pages of all logical bitstreams together at the start. My guess is that with digital media you usually have a delay time for setting up the decoders for a specific format and by clustering

Hi John, I'm forwarding this email to the relevant developer lists at Xiph.Org, where the format was created and where the experts gather. I'm certain there is a design reason for putting the bos pages of all logical bitstreams together at the start. My guess is that with digital media you usually have a delay time for setting up the decoders for a specific format and by clustering

just added to the WIKI: * Ideas with some concensus after discussion on IRC, it was provisionally agreed (by those present at the time) that Theora should support arbitrary pixel sizes (presently it is limited to multiples of 16 both horizontally and vertically). It is felt that this can be achieved with minimal pain by adding four values to the page header, immediately following the present

Hi, Can anyone tell me the significant differences between VP30 and VP31 (or are you allowed to)? Are there different token and quantizer tables? Are there algorithmic differences? I have a VP30-encoded file that plays with the VP3 VfW DLL but not with the open source decoder. Thanks... -- -Mike Melanson --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

Dan, In reviewing the code, derf came across the DCSearchPoints array in QuadCodeDisplayFragments(), encode.c:696. It looks like it specifies a search order for nearby coded fragments for prediction if there isn't a nearest neighbor. However, the upper search bound is defined as *0*, so the search loop (line 917) is never executed and it always falls back to the last coded fragment.

can anyone confirm that, unlike VP3, Theora in fact decodes images right-side-up? (VP3 managed to turn everything upside down on encode and reverse it on decode) The tests I'm doing indicate that Theora doesn't reverse the image -- the first coefficients encoded correspond to the upper-left corner of the frame. ___ Dan Miller (++,) Founder, On2 Technologies --- >8 ---- List

Hi, I'm developing ffdshow and ffvfw codecs for Windows. You can read more about them at http://cutka.szm.sk and http://sourceforge.net/projects/ffdshow. Stéphane Bérubé asked me recently if I could implement Theora support. I knew about first Theora release, downloaded its sources and tested it. I liked the results add decided to support it. I implemented encoding functionality into ffvfw,

Hello, could somenone please describe me the vorbis specific physical bitstream structure, as I haven't found any documentation about it. Thank you ******************* Pierre-Henri Quelen phq@laposte.net "Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)" --- >8 ---- List archives:

./configure: line 524: syntax error near unexpected token `AM_INIT_AUTOMAKE(libtheora,0.0)' ./configure: line 524: `AM_INIT_AUTOMAKE(libtheora,0.0)' I'm sure I'm doing something pro-stupid, but --- my setup works fine for ogg & vorbis. autoconf ver 2.13 automake (GNU automake) 1.4-p4 if that matters hey let's put tool version numbers into the README -dan