[x264-devel] Re: x264 documentation

[rupert.mish at comcast.net]

And the motion prediction code is in predict.c? It seems that prediction is done on 16x16,8x8 and 4x4 blocks since all 3 functions are called. At what is it determined that which one will be used?

Thanks,
- Rupert
 -------------- Original message ----------------------
From: Loren Merritt <lorenm at u.washington.edu>
> On Mon, 20 Nov 2006, rupert.mish at comcast.net wrote:
> 
> > I'd like to know if x264 has an API that might allow custom 
> > implementions of different parts of the encoder (for example a 
> > different entropy encoder or prediction scheme).
> 
> API? No. You might be able to do so by modifying x264, but that was not a 
> design goal. For example, the arithemetic coder backend is modular enough 
> that you could replace it with a range coder or the like, but if you want 
> to change the selection of contexts that's a lot more work. Motion 
> prediction is pretty hard-coded.
> Furthermore, as x264 is only an encoder, you'd have to modify some other 
> h264 decoder to support whatever non-standard-compliant feature you add, 
> which could be much duplication of work.
> 
> > I'd really appreciate if I could get any help with any existing 
> > documentation or just a few pointers to where I might want to look.
> 
> --Loren Merritt
> 
> -- 
> This is the x264-devel mailing-list
> To unsubscribe, go to: http://developers.videolan.org/lists.html
> 

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html