GNOME Bugzilla – Bug 796337
rendering issue
Last modified: 2018-11-03 11:04:09 UTC
starting from 1.14.0 I start getting rendering issues on the screen. there are nothing in the logs that can help so i recorded the screen to explain the issue: https://drive.google.com/open?id=1efura-SUDfCvC5IyPdK71gyjoKBEP9AJ sender pipeline (linux): gst-launch-1.0 fdsrc ! h264parse ! rtph264pay pt=96 config-interval=10 ! multiudpsink clients=192.168.1.23:5002 receiver pipeline (android device): udpsrc port=5002 ! application/x-rtp, payload=96 ! rtph264depay ! avdec_h264 ! videoconvert ! glimagesink sync=false it was working fine with 1.12.1 on the android device and 1.14.0 in the linux box. in addition, i tried it in both huawei handset (android 8.0) and samsung (android 4.4) so i think the handset is not the issue here.
This could be a number of issues. 1. you don't have a jitterbuffer so could be out of order packets which avdec_h264 is then outputting as gray. There's a setting on avdec_h264 to not output corrupt frames 2. I would assume there's wifi involved which complicates things. 3. Could you try to determine what causes the issue by simplifying the pipeline by e.g. starting with videotestsrc ! glimagesink, then moving up to videotestsrc ! x264enc tune=zerolatency ! queue ! avdec_h264 ! glimagesink and then possibly adding payloading as well as trying to play from a local file on the phone. 4. Another option is that there's a problem from the source. Does playing the source on the linux laptop work ok with e.g. gst-play-1.0? In other programs like vlc/ffmpeg? 5. Failing all that some basic GStreamer debug logs would be a good start in determining what may be the problem.
thanks for the steps. 1. Ignoring the corrupt frames works (output-corrupt=false). still I'm not able to understand why it was working with the older gst 1.12 without this issue. 2. indeed. it is connected via wifi 3. videotestsrc ! glimagesink -> works fine. videotestsrc ! x264enc tune=zerolatency ! queue ! avdec_h264 ! glimagesink -> works fine 4. gst works totally fine in windows so i guess only android client is affected. 5. i couldn't see any logs the case is much worse in the older handset that i have giving me indication that corrupt frames might be related to the performance of the device. was there any major optimization done in the latest version.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-docs/issues/14.