After integrating NVDEC into our video management system, I noticed that almost always, after creating new CUvideoparser, it skips first frame (intra) without feeding it into decoder. Since this behavior is problematic for our pipeline, I wrote a custom parser for H264 and populated the CUVIDPICPARAMS with its output.
This indeed solved my problem, but the decoded video starts getting artifacts on objects in motion. I compared the contents of CUVIDPICPARAMS filled from my parser and from CUvideoparser and there’s no apparent difference, except maybe picture index and frame index, which I guess have nothing to do with motion prediction decoding.
I desperately need an assistance with this issue (or maybe there’s a way to make CUvideoparser not to skip frames)