Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-bad gst-plugins-bad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 989
    • Issues 989
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 132
    • Merge requests 132
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #1009

Closed
Open
Created Jul 06, 2019 by Neil Young@foreverneilyoung

Webrtcbin: Artefacts in received video from various sources, various codecs after a while of no movement.

I'm using the GStreamer plugin webrtcbin from a Java app. GStreamer version is 1.16.0. With various remote webrtc clients (web apps, native apps, Raspberry PI UV4L) I'm having the problem, that the received video on the webrtcbin side is starting to show artefacts, which become more and more until the entire image is full of "coloured soap". This goes away after a while, if I e.g. "swipe" over the remote camera.

If I'm using a browser client from the same machine against all other targets, there are no such increasing artefacts.

I have checked the FIR rate but found, that practically neither the GST nor the browser is sending FIRs. It is also completely irrelevant, if the remote side delivers H.264 or VP8. After a while of no-movement at remote GStreamer shows these artefacts.

I know, a similar issue has already been raised a while ago, but I found no solution there:

#799

What can I do in order to approach the problem? At least for the Raspberry PI and the browser client at remote I would have all the debugging abilities, if somebody would like to know something. What I can exclude are major problems with the connectivity.

So again - reproducible artefacts if GStreamer webrtcbin is the receiver, nothing like this at all if a browser receives and displays the images.

Assignee
Assign to
Time tracking