Corruption in last 40 rows of frame with omxh264enc on Raspberry Pi v3B
Locked
Corruption in last 40 rows of frame with omxh264enc on Raspberry Pi v3B
 
|
Hello, I’m using GStreamer RTSP v1.14.4 to create an H.264 encoded stream from the Raspberry Pi camera module v2.1 using a Raspberry Pi v3B. I’m hardware accelerating the encoding using the OpenMax IL element omxh264enc. The problem is that at resolution 800x600@30 fps, the last 40 rows of each frame have a pattern of corruption. My pipeline is: “v4l2src ! capsfilter caps=video/x-raw,width=800,height=600,framerate=(fraction)30/1 ! videoconvert ! omxh264enc target-bitrate=1000000 control-rate=variable ! capsfilter caps=video/x-h264,profile=high ! rtph264pay name=pay0 pt=96” The Pi is running Ubuntu MATE 16.04 LTS with up-to-date firmware: $ /opt/vc/bin/vcgencmd version Oct 15 2018 17:24:22 Copyright (c) 2012 Broadcom version 90bb730cc70ffe95957061587b4d07e26842a4f8 (clean) (release) $ uname -a Linux pi-iot3 4.14.76-v7+ #1150 SMP Mon Oct 15 15:19:23 BST 2018 armv7l armv7l armv7l GNU/Linux I’ve tried other firmware versions including the latest stable (apt-get) firmware/kernel: $ /opt/vc/bin/vcgencmd version Dec 9 2016 15:15:20 Copyright (c) 2012 Broadcom version 2e557d8dac70add28597c3b449cb52c34588d818 (clean) (release) $ uname -a Linux pi-iot5 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux And: $ /opt/vc/bin/vcgencmd version Jun 7 2018 15:37:30 Copyright (c) 2012 Broadcom version 4800f08a139d6ca1c5ecbee345ea6682e2160881 (clean) (release) $ uname -a Linux pi-iot3 4.14.50-v7+ #1121 SMP Mon Jun 18 16:29:47 BST 2018 armv7l armv7l armv7l GNU/Linux But they don’t make any difference. What does work is different resolutions as follows:
Can anybody advise of a way to avoid this issue or at least a way to calculate what resolutions will be fine? _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
RE: Corruption in last 40 rows of frame with omxh264enc on Raspberry Pi v3B
|
|
Anyone? It’s a guess of mine as to whether it’s the last 40 rows that are corrupt… it seemed that way for 800x600 @ 30 fps. Note that I’ve tried two different Raspberry Pi model 3B devices both with the V2.1 camera. The resolution 640x480 @ 30 fps works perfectly so I’m using that for now but I’d like to find a way to calculate which resolutions should work. From: Matthew Thyer
Hello, I’m using GStreamer RTSP v1.14.4 to create an H.264 encoded stream from the Raspberry Pi camera module v2.1 using a Raspberry Pi v3B. I’m hardware accelerating the encoding using the OpenMax IL element omxh264enc. The problem is that at resolution 800x600@30 fps, the last 40 rows of each frame have a pattern of corruption. My pipeline is: “v4l2src ! capsfilter caps=video/x-raw,width=800,height=600,framerate=(fraction)30/1 ! videoconvert ! omxh264enc target-bitrate=1000000 control-rate=variable ! capsfilter caps=video/x-h264,profile=high ! rtph264pay name=pay0 pt=96” The Pi is running Ubuntu MATE 16.04 LTS with up-to-date firmware: $ /opt/vc/bin/vcgencmd version Oct 15 2018 17:24:22 Copyright (c) 2012 Broadcom version 90bb730cc70ffe95957061587b4d07e26842a4f8 (clean) (release) $ uname -a Linux pi-iot3 4.14.76-v7+ #1150 SMP Mon Oct 15 15:19:23 BST 2018 armv7l armv7l armv7l GNU/Linux I’ve tried other firmware versions including the latest stable (apt-get) firmware/kernel: $ /opt/vc/bin/vcgencmd version Dec 9 2016 15:15:20 Copyright (c) 2012 Broadcom version 2e557d8dac70add28597c3b449cb52c34588d818 (clean) (release) $ uname -a Linux pi-iot5 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux And: $ /opt/vc/bin/vcgencmd version Jun 7 2018 15:37:30 Copyright (c) 2012 Broadcom version 4800f08a139d6ca1c5ecbee345ea6682e2160881 (clean) (release) $ uname -a Linux pi-iot3 4.14.50-v7+ #1121 SMP Mon Jun 18 16:29:47 BST 2018 armv7l armv7l armv7l GNU/Linux But they don’t make any difference. What does work is different resolutions as follows:
Can anybody advise of a way to avoid this issue or at least a way to calculate what resolutions will be fine? _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
| Free forum by Nabble | Edit this page |