similar to: Win32 experimental player/encoder

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

Question: is it permissible to put more than one frame packet into a page? At 30 fps, Ogg page overhead is on the order of 8 - 10 kbits/sec. At low datarates, this is going to be unacceptable. If I shove a few frames into a page, how does this affect the granulepos stuff? ___ Dan Miller (++,) Founder, On2 Technologies <p>--- >8 ---- List archives: http://www.xiph.org/archives/

First, an introduction: I work in a group that makes educational software. In the coming months, we're planning to release our entire Mac/Windows runtime under the GPL. We currently encode our audio with MP3 and our video with VP3. For playback, we rely on QuickTime 5 on MacOS and Windows. In the short run, we'd like to help maintain the VP3 QuickTime codecs, preferably without

Well, I've been slamming my head against this all night, so it's time to ask for help... Having gotten together a reasonably decent port of what I thought was the whole API to the Ogg Way, complete with Ogg mem management and bitpacking, I started digging deeper in the code... only to find that it looks like I only have a middle stream handler. The encode and decode code both assume that

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.

pls let me know if/when you have theora compiling & running on Windows. -----Original Message----- From: Tabuleiro [mailto:beta@tabuleiro.com] Sent: Tue 10/22/2002 3:13 PM To: theora-dev@xiph.org Cc: Subject: [theora-dev] compglobals.c I believe this file is no longer used and contains functions that are no

Hello all. I've been playing around with theora since it first entered CVS, and I like what I'm seeing. Today I've been fixing xine's theoraplugin to understand theora_info.frame_{width,height} and theora_info.offset_{x,y}. I only got it working after some experimenting and basically copying the code from player_example. A few questions related to this: 1. What are the legal

This is mostly for derf, but others may be interested too. Attached are the warnings (stderr log) from compling theora under gcc 3.2.3 (Debian). There quite a few. Many of them are spurious, but some indicate real bugs. In particular it seems likely we have more unitialized variables since Dan reports differing encoder output depending on the compiler used. In general, we need to go through

good question. I would think beta means the bitstream is more or less stable. Monty? >If June is the goal for public release, is the second milestone the first beta/rc1? Guess what I'm asking is, whats a good estimate for when the codec will be frozen as far as backwards compatability.. -----Original Message----- From: Arc [mailto:arc@indymedia.org] Sent:

--- "Tabuleiro" wrote: Hi, guys. I was working with the VP3 code, planning to integrate it with Ogg for a self-contained solution for video playback, platform independant, no installation required, no QT, no AVI runtimes. My main interest is CD-based work using local files and portability/performance, not really into streaming or anything fancy (network error correction, prediction,

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 all, > One problem I see with your proposed implementation is that it does not > specify how audio and video would be synchronized, since there are no > absolute time stamps for the video frames. So it is difficult to account > for > audio latency on different systems, much like when you play an AVI file. > Ideally it would be wonderful to have timestamps that could be used

All the notes you mention for VC are in vp32_build.html in the release, but thanks for reiterating. Last time I built for Mac I believe I did the os9 version in CW6 and the OsX version in CW8, but I can't think why they shouldn't both compile in CW8. <p>-----Original Message----- From: Tabuleiro [mailto:beta@tabuleiro.com] Sent: Thu 9/5/2002 4:25 PM To: theora-dev@xiph.org Cc:

Okay, thanks to some stubbornness on my part and helpfulness on the part of people on this mailing list, I got the Ogg Theora alpha compiled up and installed and running. Yesterday, I went to the Prelinger archives (the public-domain video archive at www.archive.com) to find a high-quality original to re-encode as a test. The encoder worked just fine, and playback as well, and I thought I'd

[standard disclaimer about my mail format] in ftp.vp3.com/theora user: vp3 pass: vp3dev theora_dbm_5-28.zip this implements a bitstream change; the header now contains a compressed huffman tree rather than the frequency counts (as discussed) pardon my inability to use diff correctly. The change in toplevel.c is trivial (new function names & params) huffman.c is the important one. I

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

FYI, Google is acquiring On2: <http://www.betanews.com/article/Future-of-open-Web-video-may-change-with-Google-acquisition-of-On2/1249481107> Also on Slashdot: <http://tech.slashdot.org/article.pl?sid=09/08/05/1742249> Anyone knows what, if anything, this means for Theora, open video and/or the Xiph.Org Foundation? Wild speculation: considering that they complained about the

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

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