DMAbuf flickering from three different sources
Matteo Valdina
matteo.valdina at gmail.com
Thu Oct 4 10:59:14 UTC 2018
Hi Pekka,
No the problem is also present on weston 4.0 and 5.0.
One interesting note, all sources use the same resolution (4K and GStreamer
is using format NV12).
The two gstreamer sources are in full screen in two different display.
Best
Matteo Valdina
On Thu, Oct 4, 2018, 05:44 Pekka Paalanen <ppaalanen at gmail.com> wrote:
> On Wed, 3 Oct 2018 11:19:28 -0500
> Matteo Valdina <matteo.valdina at gmail.com> wrote:
>
> > Hi Y'all,
> >
> > I'm working in a Weston-based compositor (4.0 and later on the 5.0) and I
> > faced an issue.
> >
> > I have two different sources (1 QT application and 2 GStreamer
> waylandsink)
> > that provide content a live stream using the linux-dmabuf-unstable-v1.
> > The issue is that the frames of this three sources are displayed in
> > randomly on all these sources.
> >
> > I mean that source 1 display some frame for source 1 and some frame from
> > source 2 or 3. And this is affecting multiple processes (the QT
> application
> > is a different process).
> >
> > It looks like the same DMAbuf pool is shared across all applications.
> >
> > This is a Kernel 4.12, Weston 5.0, Qt5, GStreamer 1.14 Mesa 18.1.7 and on
> > an Intel HD graphics 610.
> >
> > Any suggestions to tackle this?
>
> Hi,
>
> is this problem only on your own compositor, while upstream Weston
> works fine?
>
> How different is your compositor from Weston, what have you modified?
>
> I can't imagine what kind of bug in the compositor could cause mixing
> up buffers from different clients at the dmabuf level.
>
>
> Thanks,
> pq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20181004/8dd0384b/attachment.html>
More information about the wayland-devel
mailing list