[XviD-devel] dev-api-4 this weekend

[suxen_drol]

hi,

On Sat, 22 Feb 2003 11:27:13 +0100 elcabesa <elcabesa at inwind.it> wrote:
> how many ofrk are inside cvs and what are used or still alive?
> 
> cvs-head
> dev-3-api and
> dev-4-api?

i posted 'cvs structure' to xvid-devel >1 day ago, which describes the
cvs layout.

cvs-head is very much alive. it is the primarly place for ~unstable
development.
dev-api-3 was recently merged back into the head, and now inactive.
dev-api-4 is currently active.

 On Sat, 22 Feb 2003 12:49:45 +0100 elcabesa <elcabesa at inwind.it> wrote:
> since you want to move ratecontrol inside core why not move inside core 
> fuction to set motion estimation preset?
> 
> static int const motion_presets[7] = {
[...]> 
> 
> this may be done during init , using xvid_global and you can also leave abilty 
> to user to change it as they do now=)

we could do it via XVID_GBL_INFO, or a XVID_ENC_INFO command, where xvid
returns the array and number of elements. my only concern is that the
api becomes over-compliciated by structures.

/* motion descriptor */
struct {
   int flags;		motion flag preset
   char * desc;		short flag description ("Low","Medium", "High","Ultra","Monster Kill")
} xvid_motion_preset_t;

/* encoder info */
struct {
    int version;			[in]
    int preset_num;			[out] num of presets
    xvid_motion_desc_t * preset;	[out] motion preset descriptor array
} xvid_enc_info_t;

> p.s. looking new api i see that every struct has inside VERSION and you tell 
> that when starting a function we should make a memset and then set version
> is this xvid-coder related or MUST be done also by external program that want 
> to use xvid codec?

the application must zero the struct and set the version field. this
ensures backwards/forwards compatibility.

> i'm looking new code nad found lot's of idea.. and post them here =)
> please don't kill me=)

ideas are welcome
code/patches are very welcome.

> can you define ADD this version system in stable and dev-api-3 too?
> it would make coders life easy have a common system versioning
> p.s. i wrote ADD not replace=)

the new versioning system was designed to make life easier. its been on
my todo list since september. however, upgrading the api is a lot of
work, which is why i've forked off to commit changes.

when we're satisified with the new api (and ratecontrol/plugins issues
are resolved), it will merged into the head. there's still much to be
done, so please dont upgrade libmpcodecs\ve_xvid.c just yet.

the stable releases (release_0_9_0 and release_0_9_1) shouldn't be
changed. they are release versions, which are only maintained in the
event of bugs.

-- pete; life is like a box of ammo