Hi,
It seems that the video encoder is able to do 30Hz:
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7008, dropped: 0, current: 29.50, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7015, dropped: 0, current: 29.24, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7015, dropped: 0, current: 29.79, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7025, dropped: 0, current: 31.77, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7030, dropped: 0, current: 29.24, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7031, dropped: 0, current: 29.33, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7040, dropped: 0, current: 29.83, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7045, dropped: 0, current: 28.80, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7045, dropped: 0, current: 27.85, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7056, dropped: 0, current: 30.82, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7062, dropped: 0, current: 33.93, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7062, dropped: 0, current: 31.80, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7070, dropped: 0, current: 27.61, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7076, dropped: 0, current: 27.97, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7079, dropped: 0, current: 31.29, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7087, dropped: 0, current: 33.32, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7090, dropped: 0, current: 27.36, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7093, dropped: 0, current: 26.64, average: 29.99
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink2: last-message = rendered: 7103, dropped: 0, current: 30.42, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink1: last-message = rendered: 7108, dropped: 0, current: 34.53, average: 30.00
/GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0: last-message = rendered: 7110, dropped: 0, current: 32.38, average: 30.00
So the issue is likely in my application. Could be the video encoder setup, or the image consumer taking to much time. For the Image consumer I’m using the FrameConsumer object.
NOTE:
There were a few typos / syntax errors in that last pipeline you sent, here is an updated working one:
gst-launch-1.0 -v nvarguscamerasrc sensor-id=0 ! nvvidconv ! nvv4l2h265enc ! fpsdisplaysink text-overlay=0 video-sink=fakesink sync=0 nvarguscamerasrc sensor-id=1 ! nvvidconv ! nvv4l2h265enc ! fpsdisplaysink text-overlay=0 video-sink=fakesink sync=0 nvarguscamerasrc sensor-id=2 ! nvvidconv ! nvv4l2h265enc ! fpsdisplaysink text-overlay=0 video-sink=fakesink sync=0