similar to: Problems with Theora alpha 4 crashing

Derf's from-scratch alternate implementation of the theora codec is now publicly available from our subversion repository. http://svn.xiph.org/experimental/derf/theora-exp/ This exciting new codebase promises superiour performance, and the encoder is capable of higher quality output than the current represenation, taking advantage of the bitstream extension we've added to the

I've just committed an image flip for compatibility with VP3 lossless transcode. Thanks to mau and derf for verifying that this was needed. It's a little hacky on the decode side; suggestions for improvement are welcome. Since this is a bitstream change, and we're still a ways from having a complete spec (which is the gating item for beta 1 and the bitstream freeze) we're

Hi, A few questions: Is libtheora strictly backward compatible with VP3? Can I set it up to shove raw VP3 data through and trust it to decode the same way as On2's open source code did, loop filters and all? Also, is libtheora just supposed to be a C-based reference implementation? I was looking through the code and noticed a distinct lack of any kind of optimizations. Naive tree-based

Monty, Derf and I were discussing some theora bitstream improvements. He was curious about the spare bits in the keyframe header. There's a keyframe type bit which is always DCT_KEY_FRAME aka '0' and two spare bits. You took out a lot of similar extra bits in the VP3 code. Do you remember anything about the motivation for leaving this one in? Given the constant, were there plans

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.

As I understand it the current plan is to make it possible to losslessly transcode VP3 video to Theora video. In my experience, one of the "features" of VP3 is it drops frames in the event that there is little/no movement in a frame, or if "drop frames" is enabled, to drop frames if the data rate is getting too high. I understand that the way that VP3 does this in

I try to merge VP3's mmx decoder into theora. http://kyoto.cool.ne.jp/vp3/developers/theora-alpha3-MMXd-src.zip You can see the change by searching the keyword "_UsingMMX_" in all lib folder's file. From VP3???YO vp3@go8.enjoy.ne.jp

Hello, First of all, I would like to say that my work that I wrote in the other email would be to do in hardware the functions: CopyRecon, LoopFilter and UpdateUMVBorder. These are modules that Leonardo had made, but it wasn't ok in FPGA. When I had a chat with Leonardo we were thinking in rewrite these module for to do this running in FPGA (to debug in a Hardware level is much more

attached patch adds support for the experimental theora branch to mplayer. you can get theora-exp from svn: svn co http://svn.xiph.org/experimental/derf/theora-exp/ The decoder here is feature-complete, up to and including all planned bitstream features for the initial Theora release. Some of these are not yet present even in the reference decoder. These include: - Support for non-VP3 style

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

The vp3 / theora decoder in FFmpeg project received a major speedup: http://multimedia.cx/eggs/profiling-and-optimizing-theora/#comment-150751 http://git.ffmpeg.org/?p=ffmpeg;a=commit;h=6e8061980c9a18a0eb9802f5dc5becc349066680 http://git.ffmpeg.org/?p=ffmpeg;a=commit;h=8476744ba50d26a3e188def192cd9086b0f781d7 http://git.ffmpeg.org/?p=ffmpeg;a=commit;h=a51faef9b61bd80499a28322802ef4b22be44d43

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

some of you may find this helpful: I've uploaded a short (5 second) raw clip in yuv4mpeg format, associated audio, and batch files to exercise the encoder & decoder examples. In addition I've included the file as compressed (test.ogg), and a longer version as well to test playback sync. Notes: to use MPlayer with the -vo yuv4mpeg option, you need to get the latest release and compile

I'm new to the list so please excuse me if this has already been rehashed before. There seems to be something very odd about how the PP_INSTANCE::PrevFragments array is handled during keyframes. I'm not a video codec expert so I'm not entirely sure what the reason for keeping a history of blocks updated in the last few previous interframes and adding them to the blocks to be

Hi guys, instead of sleep, I had a thorough read of the Theora 1 Specification document last night. It's a turning into a really good document and I'll have more detailed feedback tomorrow. Cheers, Silvia. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

Hi everyone, I just landed into the theora planet, as a game programmer, I searched for a free video fomat/codec and the theora choice became obvious. However I experienced rather bad performance (at least from a game programming point of view) After a couple a profiling, I discovered, as previous discused in a post found via Google, that the bottleneck is in the ogg library. An unsane part of the

My understanding -- Monty or Emmett, feel free to chime in if you think this is incorrect -- is as follows: www.theora.org is the home for all new releases of the Theora video codec (formally known as VP3). This includes the main OGG/Vorbis integration product, which Monty is working on personally, as well as the QT and Windows codecs, both legacy VP3 versions and new versions reflecting any

Hi all. I'm here again :) The small leak in my app is gone. I'm going on with it, now I grab a frame from a video device and I encode it with Theora... The debugger ( valgrind ) says: ... ==2782== Invalid read of size 1 ==2782== at 0x1B94B0BD: PixelLineSearch (scan.c:1482) ==2782== by 0x1B94B35A: PixelLineSearch (scan.c:1597) ==2782== by 0x1B94B447: LineSearchScorePixel

Hi, Since a number of people are eager to try out the native VP3 decoder in xine, I have made a patch available, bz2-compressed: http://www.pcisys.net/~melanson/codecs/xine-vp3-decoder-patch.bz2 To work with this patch: 1) Get the latest xine-lib from CVS. Visit this page for more details: http://sourceforge.net/cvs/?group_id=9655 The module name is xine-lib, but you will also need

I'm pleased to announce the alpha 3 release of the theora reference implementation. http://theora.org/files/libtheora-1.0alpha3.tar.bz2 http://theora.org/files/libtheora-1.0alpha3.tar.gz http://theora.org/files/libtheora-1.0alpha3.zip The main differences over alpha 2: The encoded image has been flipped to match the sense used in VP3, with the origin at the lower left.