[XviD-devel] API changes request from MPEG4IP

[suxen_drol]

gday bill.

> ----- Beginning of forwarded message -----
> From: Bill May <wmay at cisco.com>
> I'm working on  porting your latest xvid tarball  (0.9.2) to mpeg4ip. My
> new concept is  to use the codec libraries  published by the developers,
> rather than including them with our package.
> 
> This is working great with lame, faac and ffmpeg (as an alternate mpeg4 
> encoder).
> 
> I  have our  decoder  plugin working  very  well, and  have the  encoder
> encoding (it  looks great, btw). However,  I need some  minor changes to
> the encoding APIs -  I wanted to pass them by you  before I did any work
> to make sure that you'll accept the code.
> 
> 1) - need to be  able to disable all VOL headers in  the stream. This is
>      fairly simple to do - probably add a flag.

all VOL headers? is that correct, not even the initial one.
what about the VOS & VO headers?

should be easy regardless.
 
> 2) - need  to get  the reconstructed  YUV  image back  after encoding  a
>    frame.   I'd like  to know  what  you think  the best  way to  return
>    this. I'm current  using XVID_CSP_USER to pass in  the data - perhaps
>    just overwriting the data there ?

what order do you want the images in, coded or display?

the later is already provided by the plugins callback concept.
see "src/plugins/plugin_dump.c"

> I'm also  contemplating adding small  option menus to mp4live  that will
> allow differing  options -  I'd like  to know what  opinions as  to what
> different options make sense.
> 
> For those unaware, mpeg4ip is  a standards based streaming platform that
> consists of player, content  creation tools and mp4live.  We've recently
> made some major  changes to mp4live - we know  can broadcast pretty much
> infinitely and remain in audio/video  sync.  We've been using xvid since
> April, 2001.

yep, sounds good.
note: xvid started back in late august, 2001 ;-).

cya
-- pete