search for: hip245

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:

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,

as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision

>>> Ideally? You seem to be stuck in a world of operating systems that need >>> a specific filename extension to identify a file type. >> >> Sounds like you're a Mac user. > > <snip> > > ...determining a file type is not a task for the OS... For the past few years, users of the QuickTime container have faced a similar dilemma to what we have

As was briefly discussed on IRC, ffmpeg and mplayer currently output two somewhat incompatible YUV4MPEG streams. This meant that encoder_example could take input from mplayer, but not ffmpeg or movtoy4m (a QuickTime->Y4M tool). This is a patch that fixes this issue and should allow encoder_example to take input from either format: diff -urd xiph-cvs/theora/examples/encoder_example.c