Continuing the discussion from Rectification of supported Entron F008A120RM0AV2 Camera Sensor:
DRIVE OS Version: 6.0.8.1
Issue Description: I have exactly the same issue as author of referenced topic had. The only thing is that I was able to fix broken rectification results by cropping original input 3848x2168 to 3840x2160. The rectified image is okay now. My problem is VIC rectification performance is ~15Hz only for 3840x2160 resolution. Is it expected performance?
Dear @vladimir.tchernitski1 ,
Could you please share repro steps? did you use DW rectification sample with input video?Also, may I know is there any dependency on DOS 6.0.8.1 release?
Hello SivaRamaKrishnaNV,
I just use rectifierLDC example and instead of default 1200x800 movie I used our own 3840x2160.
I am going to profile the same scenario on DOS 6.0.10 but I was able to profile slow rectification on 6.0.8
I see that actual VIC processing takes 17.9ms that is closer to my expectation ~55Hz.
But there is NvMediaLdcSetWarpMapParameters - 22.772 ms that happens completely on CPU just before VIC and taking 100% core. How to avoid it?
It does a memcpy type of operation, involves several memory access operations and expected to be slow with big images
Solved. Replaced dwRectifier_warpNvMedia by “manual” flow.
in init: NvMediaLdcSetWarpMapParameters(…) once, in frame loop - NvMediaLdcProcess(…)
Is NvMediaLdcSetWarpMapParameters called multiple times earlier and causing bottleneck?
Correct. Every dwRectifier_warpNvMedia call leads to a call of NvMediaLdcSetWarpMapParameters internally (at least according to the profiler)
Thank you for update.
