[Bug 797280] webrtcbin: video pixelated

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797280

--- Comment #6 from Dmitriy <degtyaryov at gmail.com> ---
(In reply to Nicolas Dufresne (ndufresne) from comment #4 and #5)
> We'll need to create a new word for that. Maroblockelated ?
Excuse me. I'm from Russia. I don't speak English. I do not understand the
meaning of this word. Please explain.

> The drain() warning happens on gaps and discont(), so clearly there is some lost.
But why the video is not restored. I admit the short-term appearance of
artifacts, but it should be restored immediately.

> Something to keep in mind is that GStreamer does not implement the Google rate control feedback. That usually mean a highly conservative rate and deadline is pick, combined with possible storm of keyframe request (can be check by monitoring the RTCP flow), it can easily fall apart.
I do not think that this is somehow related to this problem. After all, the
problem has a place to be at communication gstreamer <-> gstreamer. In
gstreamer exists FEC and NACK-PLI.

> I think you should share the encoding parameters that you are using, vaapi default are aiming constant quality, so they generally behaves better then vpxenc default.
The problem is not in encoding, but in decoding. This should not be a problem.
gstreamer <-> gstreamer vp8enc deadline=1. for acceleration i using
vaapih264enc without parameters.
Chrome encoding parameters I can't know. Problem in gstreamer decoding.

It seems to me to understand the problem about which I speak you just need to
reproduce it.

To reproduce it need:
1. Take any mediocre computer, such as the Intel Core i5-2300(I tried others).
2. Install the OS, for example Fedora 28(I tried AltLinux 7, irrelevant).
3. Compile gstwebrtc-demo.
4. Open in chrome https://webrtc.nirbheek.in
5. Specify the best quality for your camera constraints {"video": {"width":
{"exact": 1280}, "height": {"exact": 800}}, "audio": true}
6. Run everything on one computer, localhost connection.

I always have a problem. Is it not reproduced by anyone?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.