Ghosting-like Issue on DOL-HDR IMX415

Hello everyone,

We have DOL2 HDR working through nvarguscamerasrc. Driver, INCK/PLL setup, MIPI timing and DOL geometry are all verified at this point. Sensor runs VMAX=2300, RHS1=105, HDR ratio 16. DT mode has active_w=3872, active_h=4534, num_of_ignored_lines=57, num_of_lines_offset_0=50, embedded_metadata_height=1. 30fps confirmed.

Image is mostly correct now. Colors are fine in low and mid exposure areas, and on high contrast edges that are not clipped.

The remaining problem: thin purple/magenta fringing along the borders of clipped areas. For example the roofline of a white car against bright sky, or edges of sunlit white surfaces. It only happens at clip boundaries. Edges that don’t clip are clean. We tested shifting the DOL extraction offset by 1 and 2 lines in both directions — no effect on this artifact, so it’s not geometry. At 1ms fixed exposure where nothing clips, the image is completely clean (screenshots attached).

Our guess is this happens in the WDR merge where the long exposure is partially clipped (green clips first, WB pushes the seam magenta). So it looks like an ISP tuning issue, not a driver issue.

Questions:

  1. Which camera_overrides.isp parameters actually work for DOL WDR on L4T 32.x? Our override file is definitely loaded (other parameters change the image), but wdr.DOL.v4.EnableDOL = FALSE does nothing, and sweeping ae.wdr.DreMin/DreMax from 8 to 64 also does nothing/makes it worse. Is there any documented set of keys for DOL blend / highlight desaturation on this release?
  2. Is there any way to improve clip/highlight handling for a DOL sensor without the partner tuning tools? Or is sensor tuning data the only option? If so, should we go through the module vendor or can we get tool access directly?
  3. Is this magenta fringe at clip boundaries expected behavior for the default untuned WDR merge?

Can share full DTS mode entry, driver code and logs if needed.

Thanks

(A SDR image)

(DOL-HDR image)

What’s the BSP version.

For the HDR image tuning usually have forum user consult with camera partner to help on it.

Thanks

Hello Shane, thank you for your answer.

I am using Xavier NX on JetPack 4.6 (r32.6.1)

uname -r
4.9.253-tegra

So can we say this is an ISP issue, and we require the correct camera_overrides.isp file?

Thanks

Since your HDR image looked washed / low-contrast relative to SDR, on r32.6.1 I’d try this order:

  • reduce ae.wdr.BiasTable bias a bit
  • increase tc.v3.dae.tuning.highlightControl
  • reduce tc.v3.dae.tuning.evCompensation slightly if overall brightness is high
  • increase ltm strength moderately to bring back local contrast

Hello Shane,

I seem to not have these parameters within my camera_overrides.isp file. Should I contact my camera partners?

Thank you.

Yes, please contact to camera partner for image tuning problem.

Thanks