Re: Let's go for it then...

> A well defined interface for pluggable modules is a must. But I have no idea
> how to define and
> synchronize such things in a group of developers. Do we need some kind of a
> hierarchy? Does that
> mean we have to have some internal documentation papers? How are we supposed
> to work?

    The first steps are:

    -    think on and define well the main data structures (macroblock,block,frame...)
    -    define the main interfaces (function pointer prototypes in C), for example
        -    transformation
        -    quantization
        -    intra prediction
        -    intra prediction process
        -    deblocking filter
        -    motion estimation (ugh!)
        -    SAD
        -    entropy coding (must support UVLC/CAVLC and CABAC)
        -    bit stream generation
        -    ...

    Then is easy, just fill in the gaps... ;-)  As i commented long ago IMHO the
best first milestone must be to have a compliant intra coder, that is, a codec that
generates a correct bitstream (decodable by the reference software and other
implementations) but that only makes use of I pictures.  I think that this milestone
is mostly easy to achieve... if people contribute.

    /AITOR




-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1