Can someone explain to me:
nvcamerasrc do-timestamp=true enable-meta=true fpsRange=“30.0 30.0” auto-exposure=1 aeLock=true sensor_id=0 name=nvcam0 ! video/x-raw(memory:NVMM), width=(int)4104, height=(int)3046, format=(string)I420, framerate=(fraction)30/1 ! nvvidconv flip-method=2 ! video/x-raw(memory:NVMM), width=(int)3840, height=(int)2160, format=(string)I420 ! queue ! identity name=tap0 ! omxh264enc control-rate=2 profile=8 bitrate=30000000 ! identity name=tap1 ! …
Why is the number of “handoff” callbacks on tap0 != tap1? i.e. there seems to be missing frames after the encoder? Why?
It’s usually off by one or two frames, i.e after the encoder I’m short a frame or two, sometimes three. I think the longer I let it play, the more I see one or two frames go missing every so often. Is this just a bug in the encoder?
NOTE: jetson_clocks.sh and nvpmodel -m 0 are both set.
On pipeline stop, I see more packets in-core on my tap callback than what’s in the stream (ffprobe confirms). There seems to be some kind of flush bug on pipeline PLAYING -> NULL state.