similar to: Legalese. What is stride?

Hi, despite the warnings on the website ;-) I played with the current CVS source of theora on Windows 2000 w/ Microsoft Visual C++. The codec and the "experimental" example programs compiled fine. I also encoded a 33 MB MPEG2 (?) video (3 minute trailer) to a 14 MB .OGG using "mplayer -vo yuv4mpeg -ao pcm" and the "encoderwin" sample program, and play it with the

I'd previously been working on the assumption that the frame_height was the height of the inner picture region... and height was the height of the outer frame. Then upon readnig the spec... where it calls the outer part the frame and the inner part the picture region... i assumed i'd made a mistake and that frame_width is actually >= width in the theorainfo structure... ie

Hello all. I've implemented aspect scaling in xine, but have it turned off by default, because it appears it isn't absolutely clear if the fields in theora should mean pixel or frame aspect yet. In a recent IRC discussion, it appears most felt that pixel aspect should be it. Would it be acceptable to turn this on in xine, or should I wait until you make some official decision about it?

hi all, i'm trying to code a tool to get some images from a ogg/theora file .... so basically i need to get a frame and convert to rgb ... and here is my question (sorry, i'm newbe here) ... how to convert a yuv_buffer to a rgb matrix ? i tryied diferent ways but my mistakes are bassically cause i don't understant how yuv_buffer structure works ... anybody can help? thanks a lot.

Hi there, is there any document giving a high-level overview of how to use "libtheora"? As it stands, I'm scrounging through headers and example code, and doing a whole lot of guessing. In the meantime, could you either confirm or deny the following guesses? 1) Before compressing with Theora, I must unpack my YUY2 data into three separate arrays (Y, U, and V respectively), and

Just trying to debug my theora encoder... just wondering if someone could give me some insight on a few thigns... In the yuv_buffer i'm sending in... i am just setting y_stride = y_width = videoWidth uv_stride = videoWidth/2 y_height = videoHeight uv_height = videoHeight/2 Making the y buffer (width*height) and each of u and v (width*height/4) Am i correct in doing this ? I knwo stride

hi folks! once again i am trying to decode a yuv_buffer to a 24 bit RGB buffer. last time nobody seemed willing to tell me how to do this, so i am trying again. i try to make my questions more simple. what i need to know is: how many bytes are in each y, u, v array? what for are these strides? what exactly is a "plane" in a frame, and what does it do? what i want to achieve is

I posted this the other day... but it didn't get delivered... ------------------------------------------------------------------- I'm getting stuck into a theora decoder for directshow... i was just wondering if someone could give me some info. What output format does theora use ? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwmt/html/YUVFormats.asp

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, is there any place where the possible values for the strides in the yuv_buffer structure is specified? or just in the source code? ;) I could compress a video with, lets say, yuvbuf.y_stride = yuvbuf.y_width, so the yuvbuf.y[0] really started in the start of the y channel data. I watched the video in several players, and everythings' ok. But, when programming the decompress process, the

I've spent the weekend or so trying to get my head around Theora and I'm just not having any luck. First of all, I really don't have any interest in immersing myself in video encoding--I just have one simple thing I'd like to do--so I haven't spent any time reading about the theory or specs or anything like that. I'm attempting to write a "render-to-theora"

I'm seeing the following failures with "make check" (x86-32 linux): FAIL: test/CodeGen/X86/fold-mul-lohi.ll Failed with exit(1) at line 2 while running: llvm-as < test/CodeGen/X86/fold-mul-lohi.ll | llc -march=x86-64 | not grep lea leaq B, %rsi leaq A, %r8 leaq P, %rsi child process exited abnormally FAIL:

Hi, Attached is my patch to add theora encoding to ffmpeg's libavcodec (by using libtheora). I am requesting help to fix the bug I mention below and am seeking general comments before I submit the patch properly. Files encoded using this encoder have a problem playing in VLC. The files will not play unless "Drop late frames" has been unticked in the advanced video settings.

Fixed. Thanks. Evan On Feb 11, 2008, at 2:35 AM, Duncan Sands wrote: > I'm seeing the following failures with "make check" (x86-32 linux): > > FAIL: test/CodeGen/X86/fold-mul-lohi.ll > Failed with exit(1) at line 2 > while running: llvm-as < test/CodeGen/X86/fold-mul-lohi.ll | llc - > march=x86-64 | not grep lea > leaq B, %rsi > leaq

Hi Evan, In -relocation-model=static mode, those tests are now getting code like this leaq A, %rsi movss %xmm0, (%rsi,%rdx,4) instead of this: movss %xmm0, A(,%rdx,4) This is specifically what these tests were written to catch :-). Running them with -relocation-model=pic is hiding the real bug. Dan On Feb 11, 2008, at 11:22 PM, Evan Cheng wrote: > Fixed.

Hello, I understand the need for a proper stride setting when formatting a filesystem on a RAID device. However, is there any problem in using a stride setting when formatting a filesystem on a regular non-RAID, non-SSD, just plain-vanilla-single-disk block device? I'm sure there isn't any benefit to it, but I'm curious if there is any harm. The reason I ask is I'm looking at

All, I have a question about calculating the value for the -E stride option to mke2fs. The mke2fs man page says stride=stripe-size Configure the filesystem for a RAID array with stripe-size filesystem blocks per stripe. So stride = size of stripe/blocksize. The size of a stripe is the RAID chunk size * the number of drives in the RAID. My question: are parity disks

Fixes FDO#55294. --- src/gallium/drivers/nv30/nv30_miptree.c | 3 +-- src/gallium/drivers/nv50/nv50_miptree.c | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/src/gallium/drivers/nv30/nv30_miptree.c b/src/gallium/drivers/nv30/nv30_miptree.c index 5a9a63b..9700fa8 100644 --- a/src/gallium/drivers/nv30/nv30_miptree.c +++ b/src/gallium/drivers/nv30/nv30_miptree.c @@ -56,8

Fixed. However, I wonder if we are doing the right / smart codegen for static codegen. AMD64 ABI document seems to indicate rip relative addressing should be used even in this case (see page 38). You know about about Linux addressing mode than I do. Please check. Thanks, Evan On Feb 12, 2008, at 10:10 AM, Dan Gohman wrote: > Hi Evan, > > In -relocation-model=static mode, those

Enabling the following function in tests/noop.c: noop_test_decode () { theora_info ti; theora_state th; theora_info_init (&ti); theora_decode_init (&th, &ti); theora_clear (&th); theora_info_clear (&ti); } segfaults. The cause is that theora_decode_init() expects a theora_info structure which was previously initialized by passing actual bitstream data through