[MPlayer-G2-dev] Re: Data communication between demuxers and UIs

[Andriy N. Gritsenko]

    Hi, D Richard Felker III!

Sometime (on Thursday, January 22 at 19:05) I've received something...
>On Thu, Jan 22, 2004 at 09:03:45AM +0100, Attila Kinali wrote:
>> On Thu, 22 Jan 2004 01:28:22 -0500
>> D Richard Felker III <dalias at aerifal.cx> wrote:

>> > The difficult
>> > end is "repairing" filter chains, renegotiating link parameters, etc.
>> > to accommodate changing options.

>> That's a really good question. Do you have an idea how this can
>> be done ?
>> Or is it a trivial, call config() on all nodes in the chain ?

>Yes, it basically amounts to that, but there are various questions.
>For example if there's a filter that can't change parameters without
>losing frames (due to internal buffering latency), should you
>completely reset this filter and give bad output? Or should you insert
>scale on one or both sides of it to hide the format/size changes from
>it? I don't know what the best answer is...

    If you would like to hear my thoughts I'll tell you I prefer third
way - any filter that may lose frames with internal buffering must use
some API call to scale frame itself. I'm sorry but your way when "API
knows about all better than filters" is too similar to Microsoft way of
writting applications so I don't like it. And I don't like to drop the
frames too. ;)
    And I also want layers' internals to be as simple as possible - layer
have to do nothing but be a glue to its components, and on other hand it
have to have some helper functions for components (modules, filters, etc)
but nothing more. I don't like layers with AI, any AI seems to be hack.
    Forgive me if that offends you, please.

    With best wishes.
    Andriy.