similar to: new spec

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

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

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

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

Supposedly On2 transferred their Video Recorder and TrueCast5 streaming server into opensource along with VP3. Theora is obviously the VP3 project, and while I can find nothing on Xiph about it, the recorder source is offered on vp3.com; but I can find nothing on Xiph or vp3.com about what happened to Truecast5. I contacted On2 about whether TrueCast5 was really going to be open source, and they

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

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, 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, 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 all, It's been a few years since I encoded a number of movies using the VP3 codec (v3.2) on my Quicksilver PPC. Now I have a new Intel mac and I'd like to play them. However, it seems that the codec offered on On2's website is only for the PPC architecture. Does anyone know a workaround or some other codec that works on the MacIntel platform? I'm using Quicktime Pro 7.

--- Daniel B. Miller wrote: Please, anyone who is working with VP3 codecs, get the new build as soon as possible. It's available through the normal cvs server at xiph. see: http://www.theora.org/cvs.html take the latest build, 3.2.6.1 --- end of quote --- I've run down through all of our QuickTime 6 bugs, and the VP3 source code in CVS appears to have a clean bill of health. If

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

a couple points before I look at this too hard: "For VP3, since you can't do a constant quality encode" what? that should not be the case. Could be a QT-specific bug. Theora at any rate is certainly capable of doing constant-quality encode. This probably explains your standard deviation complaint -- VP3 is running a rate control alg, where the other codecs are just shooting for

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.

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:

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, I was discussing on the mplayer/mencoder ML about transcodingfrom Divx to Theora. I got these kind of answers: http://article.gmane.org/gmane.comp.video.mencoder.user/280 Of course I understoud only 50% of what he said, as well as I am not really used with codec and video glossary... But I generally understoud his opinion. What to think? I would like not to believe him, espacially when

Hello, Due to some licensing changes (and because I actually want to promote this, too) I want to replace our usage of Intel Indeo 5 with VP3 in a video conferencing pplication we are just developing (check: http://www.stnadby24.no/ for infos (english language) on the application). My problem is this: I need to define at least the bandwidth. I am feeding full frames from the camera with a given

--- Stephane wrote: VP3 codec uses a lot of CPU for decoding. We will need some optimization because now this codec is way too slow for home uses. --- end of quote --- Actually, the Windows VP3 QuickTime codec runs just fine on a 400MHz Pentium II box, with only occasional glitches on some dodgy Celeron systems. At work, we routinely test 320x240 full-color, full-motion video on low-end boxes.

I tried out Theora to see what the future holds, and see some pros and cons. As a great plus, I have noticed that, even at the lowest quality (ie. "-v 0"), the detail, and overally quality is clearly better than anything else available. On the negative side, at qualities comparable to MPEG4, I've notcied a great deal of blockiness. It's not as bad as blockiness from other