[MPlayer-dev-eng] [PATCH] Realplayer codec support

[Florian Schneider]

Arpi wrote:
> Hi,
> 
> 
>>finally, i'm pretty sure that the decoding problems are related to the
>>transin1 structure. my first thought was it's an array of pointers to
> 
> 
> yes!
> 
> in transform wrapper make a temp[16] containing that 1,0,0,0,0, and
> replace original transin1 pointer to point to temp.
> you'll get the same garbage as with mplayer. the same!
> 
> now, we only have to guess what are those strange numbers...
> 
> 
>>transin1[0x845d490]: {0} 0x1 (nil) 0xf90efd85 0x11 (nil) (nil) 0x845d468
>>transin1[0x845d4e8]: {2} 0x1 (nil) 0x1 0x256 0x1 0x496 0xfec00967
>>transin1[0x84310b8]: {0} 0x1 (nil) 0x28 0x61 0xb0 0x90 (nil)
>>transin1[0x81e5ea8]: {0} 0x1 (nil) 0x28 0x19 0x40861700 0x8431ad0 0x5ba
>>transin1[0x81e6188]: {0} 0x1 (nil) 0xa030001 0x20200001 0x30 0x11 0x81e6150
>>transin1[0x81e5ef8]: {0} 0x1 (nil) 0x28 0x19 0x81e61c8 (nil) 0x81e5ee0
>>transin1[0x81e6218]: {0} 0x1 (nil) 0x28 0x19 0x40861700 0x8432c10 0x5ba
> 
> 
> i have the feeling that they are somehow prefixed pointers and other data.
> the 0x8?????? seems to be memory pointers, while the others looks like
> special codes or counters. maybe this is a huffman table or other kind of
> codebook?
> 

The 0x8xxxxxx are pointers to the global heap, the 0x4xxxxxxx are 
pointers to the codec and other dynamically loaded dll's. I think that 
somewhere in a previous transformation (or somewhere else) these data 
will be constructed - at least I hope so. Or a thorough look at the code 
  might help a bit.
If you are interested, I can send the disasm of the codecs to you.


> 
> A'rpi / Astral & ESP-team
> 
> --
> Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu
> _______________________________________________
> MPlayer-dev-eng mailing list
> MPlayer-dev-eng at mplayerhq.hu
> http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
> 
>