search for: interframes

...this has already been rehashed before. There seems to be something very odd about how the PP_INSTANCE::PrevFragments array is handled during keyframes. I'm not a video codec expert so I'm not entirely sure what the reason for keeping a history of blocks updated in the last few previous interframes and adding them to the blocks to be updated in the current interframe is, but I'm sure there's a good one (perhaps it's to further refine the updated fragments). However, the way keyframes are handled in this history seems very counter-intuitive to me. When PrevFragments is initial...

Hello, all! I have many questions about tap device architecture. What is a right way to calc mtu on TAP device to avoid fragmentation on real eth device? I suppose TAP MTU = 1500-8(UDP)-20(IP)-18(Ethernet) = 1454. So I'd set 1454 for tap device: "ip link set mtu 1454 dev eth0" I'm not shure about what is the exact size of ethernet frame header, which tap device use in switch

At 17:05 8/11/2001 -0400, you wrote: >you tell me. Works alright here, except in xmms which has a bug in its >shoutcast metadata handler. I've submitted a patch at bugs.xmms.org >for it. Hmm.. well with the current version of winamp and the previous two it would and does skip if I have metadata enabled.. it'll start anywhere from ten minutes to an hour into the stream and then

Hi, I checked out the Theora source code for the first time as I figured that's the only way the Theora quirks will get documented (and subsequently re-implemented in libavcodec). I see that most of the code cribs the original VP3 source code, including the misspelled comments. Moving right along, I can't reconcile the way bits are packed in the stream. In VP3, the first byte of an

Hello, I have some code that encodes PCM data into a vorbis stream, using the workflow shown in http://www.xiph.org/vorbis/doc/libvorbis/overview.html. By analyzing that process with valgrind/cachegrind I found out that 95% of the time used for encoding is spent in the function "vorbis_analysis(&vb, 0)". My question now is: would it be technically possible to parallelize this? I

??????? I've rewritten my theora player using liboggz. I've stumbled upon a few issues though. First of all liboggz exposes oggz_read and oggz_run, but how can i read only sound data, or only video data using liboggz, say something like this: oggz_read_sound(1024), oggz_read_video(1024). ? ? ? ?? Second of all i tried using liboggz's seek function. Immediately after the seek i get some

...pdateFrame() out of the (MotionScore > 0) conditional block. I've also included my change that prevents the encoder from spending WAY to many bits on keyframes. This helps prevent the artifact where the video suddenly gets very clear when keyframes occur but gets progressively blurry for interframes. This change helps minimize some of the drastic Q changes that cause this artifact. Aaron Index: encoder_toplevel.c =================================================================== --- encoder_toplevel.c (revision 9007) +++ encoder_toplevel.c (working copy) @@ -739,12 +739,12 @@ /* Increm...

On Sunday, 12 August 2001 at 04:33, Asymmetric wrote: > At 17:05 8/11/2001 -0400, you wrote: > > > >you tell me. Works alright here, except in xmms which has a bug in its > >shoutcast metadata handler. I've submitted a patch at bugs.xmms.org > >for it. > > Hmm.. well with the current version of winamp and the previous two it would > and does skip if I

I hope this list is small enough for not beeing banned when introducing oneself. So... Hi, I just subscribed to the theora-lists. I'm from the XVID project, so I know a deal about video and MPEG-4 in particular, but nothing about Vorbis/Theora etc., That's why I'm here, because I'm interested in patent-free alternatives. I guess there is no documentation of the current status

Im using a Linux machine with standard pc hardware with 3 seperate PCI network interfaces to operate as a DiffServ core router using Linux traffic control. The machine is a P4 2.8ghz, 512mb RAM running fedora core 3 with the 2.6.12.3 kernel. All links and network interfaces are full duplex fast ethernet. IP forwarding is enabled in the kernel. All hosts on the network have their time sychronised