[MPlayer-dev-eng] state of realvideo?

[Arpi]

Hi,

> Well, I'm making progress.  I've gotten far enough now that I know at 
> least which functions have return values, and how many arguments there 
> are.  I built a .so wedge, so now I can watch the function calls as they 
> happen while playing back a .rm file!  :)
cool :)

> However, I'm a little worried that the argument structures appear to be 
> filled with code references.
it's possible due to c++ stuff :(

> Another strange behavior is that there appear to be 4 "CustomMessage" 
> calls for every "Transform" call.  I don't like that...
> 
> If anyone wants to take a look at the wedge, let me know.  The quick 
> summary of what I've learned is:
> 
> void (*rv20_init)(unsigned int * info, void ** handle);
> unsigned int (*rv20_hive)(unsigned int * info, void * handle);
> unsigned int (*rv20_free)(void * handle);
> unsigned int (*rv20_custom)(unsigned int * info, void * handle);

are you sure in that handle is the last ?

> unsigned int (*rv20_transform)
>               (
>                 unsigned int input_size,  // +8       read size?
>                 unsigned int output_size,  // +0       write size?
>                 unsigned char * input,// +10      pointer test, readable
>                 unsigned char * output, // +14      pointer test, writable
>                 void * handle  // +18 esi  source? handle?
>               );

imho the order of parameters is reversed?

> transform is a total guess at this point.  And the info structures are 
> totally unknown as well.  the init info structure has some obvious things 
> like width & height, though.

imho most of the stuff in the info struct come from the .rm file header.
at least all win32 codec i know do this - vfw, dshow and quicktime too


A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu