similar to: Boring but useful VP3/QT patches

--- "Daniel B. Miller" wrote: It looks to me like patch is trying to put each .cvsignore in the vp32 directory rather than the specified subdirectories such as Codecs/quicktime/. It seems like I need some option to get patch to use the 'Index:' commands. I looked at the man page, it goes on about how patch tries to derive the filenames, but I am still confused. Any help would

QuickTime 6 for Windows breaks the VP3 codec quite severely--if you turn on "Safe Mode" (which forces QuickTime to draw through GDI), you'll see a white or black screen instead of video. This is logged as bug #2111990 in Apple's QuickTime feedback system. The fix is a classic one-liner, although it took me a long time to figure it out. :-/ Also attached is a patch to bump the

The new 3.2.6.1 codecs work great with QuickTime 6 (thank you!), but there's no way for an application to identify them. And since the older 3.2.1.x and 3.2.2.x installers will actually *downgrade* the installed version of VP3, it would be nice if an application could warn the user. The attached patch increments kdxlqt_CodecVersion (and documents all the Component Manager arcana involved).

I performed a minor amount of refactoring of the build environment for oggdrop. These include: Action: Added a workspace to manage project files and dependencies Purpose: To build all dependent libraries before attempting to build oggdrop -- i.e. provide one-step build process. Instead of opening "oggdrop.dsp", open "oggdrop.dsw" Action: Added

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

It looks like there's more QT 6 trouble, and this is specific to the post-3.2.5.x builds. I'm on it, and will try to sort things out by Monday. Cheers, Eric (not a happy camper!) --- From a note I sent to Dan Miller: The "3.2.2.0" binaries on www.vp3.com fail with an error I haven't seen before--"You may experience problems playing a video track in credits_v.mov

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,

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

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

I tried it out on the Vp32 site - nothing in there. Says something of not matching the current tag. Nice. Theora's website does not have a web surface. Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) --- >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

How good is the video compression in vp3.2? For example, how does it compare (bit rate & quality) to mpeg1, mpeg2, Divx, real Video 8+, Windows Media, etc. etc. It being open source is nice and all, but if it can't be reasonably competitive then there isn't much point to it. I just haven't seen anything that compares vp32 to anything else. (Although to be honest, I haven't

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:

Hello everyone, I'm developing software for a marketing company which creates multimedia presentations. We're currently using proprietary Windows software, but are looking for a royalty-free cross-platform solution. It's important that the solution is royalty- and patent-free because the presentations are copied and given out in large quantities for free (as in beer ;-) We are

The VC6 .dsp and .dsw files included with the distro of the Vorbis source has a few problems. Mostly, a few files are missing and cause unresolved symbols when attempting to link to the resulting vorbis.lib. There also exists a problem with linking to LIBC, that can cause multiply defined symbols in an application that attempts to use vorbis.lib. The attached .dsp and .dsw file fix these

The VC6 .dsp and .dsw files included with the distro of the Vorbis source has a few problems. Mostly, a few files are missing and cause unresolved symbols when attempting to link to the resulting vorbis.lib. There also exists a problem with linking to LIBC, that can cause multiply defined symbols in an application that attempts to use vorbis.lib. The attached .dsp and .dsw file fix these

Hello , I had downloaded latest tar.gz of speex sources. I am trying to build it on windows , by using the Visual C project files. (dsp/dsw) with libspeex I did succeed. When I try to build speexdec (using the (dsp/dsw project files under win32/speecdec) I get the follwoing message dialog : "browse for project ogg_static" what to do ? regards sting

The .dsp and .dsw files included I obtained as a part of the vorbis source, via CVS, are not recognized by Visual Studio as valid workspace/project files. Should I be getting these files from another place or can someone clue me in on how else to build vorbis on a windows platform? Scott Danahy Programmer VedaLabs - www.vedalabs.com --- >8 ---- List archives: http://www.xiph.org/archives/

On 09-03-13 01:01, Erik de Castro Lopo wrote: > I would like to know how many years I have to wait before we can ditch > this stuff. I intend to do some testing on platforms I have available > today and roll a second pre-release after my testing. Talking about ditching, there are still .dsp files in the repository, these are MSVC 6 files. I haven't seen anyone on the list testing

Hello everybody, I hope to finish this MIME types discussion with these conclusions - it's taken enough bandwidth on these lists :). So here's a generic MIME types scheme that we all seem to be able to agree on and all that is needed for the moment. --- 1) Ogg encapsulated files: Any data that is encapsulated in an Ogg container will us the MIME type: application/ogg (as already

Hello everybody, I hope to finish this MIME types discussion with these conclusions - it's taken enough bandwidth on these lists :). So here's a generic MIME types scheme that we all seem to be able to agree on and all that is needed for the moment. --- 1) Ogg encapsulated files: Any data that is encapsulated in an Ogg container will us the MIME type: application/ogg (as already