similar to: new patch

./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

the files produced by windows compile vs. Linux are indeed significantly different in size (about 140K vs. 160) However I'm not convinced all the default parameters are set the same way in the two example files. This needs to be verified to see if there really is a bug, or can the two versions produce byte-equal output streams? <p> ___ Dan Miller (++,) Founder, On2 Technologies

Hi, So I have almost completed a new VP3 decoder implementation. In the course of doing so, I have encountered something odd about macroblock coding. As a quick overview, VP3 has a notion of fragments (8x8 pixels) and superblocks (32x32 pixels, 4x4 fragments). These apply to each individual plane (e.g., a 64x64 video will have 4 Y superblocks and 1+1 C superblocks, 64 Y fragments

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

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

Hi, Sorry for taking so long with this, but I finally committed a first pass of my own VP3 decoder to the ffmpeg codebase. You can browse the source here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ffmpeg/ffmpeg/libavcodec/ vp3.c and vp3data.h are the files in question. Attached is a message I sent to the ffmpeg-devel list about the new decoder and its present shortcomings.

Hi, Some of you may recall that I got the VP3 decoder working with the xine multimedia player some time ago and posted a patch for anyone else to try. I really messed up when I did that since I generated the patch against some random CVS snapshot of xine-lib. I did better this time and generated the patch against the latest release of xine-lib (1.0-beta4, released today). If you

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:

Hi, I have been on a documentation kick recently. I finally updated my VP3 format document tonight: http://www.pcisys.net/~melanson/codecs/vp3-format.txt v0.2: October 9, 2003 - expanded section "Reversing the DC Prediction" - added Appendix B: Theora Differences Feel free to look it over and point out any glaring mistakes. I can't wait to see how much sense it makes to

At this point, my understanding is as follows. Monty has the final word but I believe this is his intention: * Theora is a video codec. It is a modification of VP3. Presently it is assumed that Theora will be a superset of VP3; ie, VP3 streams can, with a little header magic, be losslessly transcoded into Theora streams. However, we expect future versions of Theora to diverge significantly

hi folks I've posted a new version of the Theora spec, same place as before: ftp.vp3.com/theora/spec name: vp3 pass: vp3dev This one actually works (the old one had a significant bug). Many editorial changes too. Please review & comment. - dan ps Rillian, I would have updated CVS myself but my pub key stuff is not working. --- >8 ---- List archives: http://www.xiph.org/archives/

Hi, Check it out-- another update in the space of a week: http://home.pcisys.net/~melanson/codecs/vp3-format.txt v0.4: March 2, 2004 - renamed and expanded section "Initializing The Quantization Matrices" - outlined section "Reconstructing The Frame" - moved Theora Differences Appendix to its own section entitled "Theora Specification" - added Appendix:

Hi, I don't know how much of the old VP3 codebase is incorporated into Theora. I wrote ffmpeg's VP3 decoder from scratch but eventually ported in the original VP3 IDCT function. A BSD conflict cropped up that I thought I would pass along. -- -Mike Melanson <p>---------- Forwarded message ---------- Date: Wed, 10 Sep 2003 13:06:37 -0700 (PDT) From: Steven M. Schultz

Hi, Quick note: In case anyone has not heard, Nullsoft, the people behind Winamp, have seen fit to develop their own multimedia container format. It can hold any kind of data, but their primary codecs are MP3 for audio and VP3 for video: http://www.nullsoft.com/nsv/ I and a few other people are still working out the details of the format:

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

Hi, I have been working with VP3 for some time now. Dan Miller from On2 just told me about this list. A few months ago, I managed to get On2's VP3 source snapshot to compile under Linux, a feat that many have apparently attempted and quickly abandoned. I compiled a small console app and the results of the experiment are explained here:

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

Hi, I am making good progress on understanding, documenting, and re-implementing VP3. I have found some more deadwood in the decoder code and I just wanted to verify that it really has no place: * Version 3.3 tables: There are 2 sets of VLCs: One for v3.1 and one for v3.3. The v3.1 set is always selected. Are the v3.3 tables in production, or will they ever be? * DC Search Points: VP3

Hi, The VP3 source code supports various CPU-specific optimized instructions. I see references to MMX and XMM (SSE2). I also see references to WMT. What is WMT? Thanks... -- -Mike Melanson <p><p>--- >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, I checked out the Theora source code for the first time as I figured that's the only way the Theora quirks will get documented (and subsequently re-implemented in libavcodec). I see that most of the code cribs the original VP3 source code, including the misspelled comments. Moving right along, I can't reconcile the way bits are packed in the stream. In VP3, the first byte of an