Re: Compositor not using the fastest/biggest source
Le jeudi 07 juin 2018 à 08:22 +0000, Weber, Holger a écrit :
> I try to mix different video streams with the compositor. I add and
> remove streams with different sizes and framerates dynamically (by
> The documentation says, that the compositor uses always the fastest
> and biggest video stream as output stream.
> So at the beginning I only add one live-source with the size of the
> biggest frame I expect and also the highest framerate.
> Some time later while the pipline is playing I add another stream an
> link it to the compositor. What I can see, is that it uses the
> geometry and framerate of the
> added newly added source and not that one of the first source (with
> higher properties).
This sounds like a bug. Would be nice to file a bug about this on
bugs.gnome.org. We can discuss there what we want as a final logic and
implement unit tests for that. I'm surprise we do change the output
caps after compositing have started. Most app I've wrote fixate the
output caps, so that logic is not being used.