DMAbuf flickering from three different sources

[Pekka Paalanen]

On Thu, 4 Oct 2018 05:59:14 -0500
Matteo Valdina <matteo.valdina at gmail.com> wrote:

> 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.

Sorry, I have no idea. I did get a thought about a patch in master, but
then saw it was from you. :-)

Maybe it could be some state mixup around the YUV texturing in
GL-renderer, I would assume that to be rarely tested, especially with
multiple simultaneous clients hitting it.


Thanks,
pq

> 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?  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20181004/1eaa6c96/attachment.sig>