[MPlayer-G2-dev] Re: Question for Arpi :)

[Andriy N. Gritsenko]

    Hi, D Richard Felker III!

Sometime (on Thursday, July 24 at 18:23) I've received something...
>> >>     Could you point me to detailed description of new VF API? I don't
>> >> want to make mistakes so I want description of all API functions. :)
>> >no new vf api, it's teh same as in g1 with little differences i described
>> >here on the ML
>>     Sorry, may be I've lost something but I still don't get exactly how
>> new flag drop works in get_pending_image() and process_image() - does it
>> allow framedropping by filter or does it force drop pulled frame?

>That's a very misleading way to talk about it. What it allows is for a
>filter to generate frames in such a way that there is no one-to-one
>correspondence between input frames and output frames.

    It's unavoidable in many cases when we're changing framerate.

>>     Another question is what get_pending_image exactly does. Does it just
>> return frame if filter already has one in buffer without pulling it from
>> demuxer, doesn't it?

>Again, that may be true with certain filters, but it's a misleading
>way to describe it. I'm still confused over this whole api so I'm not
>sure what the correct description is. Better to read the ML
>archives...

    So I'm confused with API too. It's why I want _really_ exact API
description. Then there will no way to say "that may be true but may be
not". If we have good defined API then we'll avoid headaches in the
future - then with any changes in function it's behavior will never
change due to strong API. :)
    I've got that question when I attempted to port my dint filter from
G1 to G2 and get confused with new API then.

    With best wishes.
    Andriy.