Everyone seems to see how a dynamic iris works differently. I'm usually pretty sensitive to them when they're working. I hope others complain and JVC releases a further firmware to address some of the more glaring aspects of this particular implementation. I never had the chance to see an eshift 5 JVC so I can't comment on how that performed. But I do know the eshift 3 and 4 models had a much better implementation. I saw no large gamma shifts and essentially no clipped whites.
Were you watching SDR or HDR? I've been using the DI in SDR with the iris closed to -10 or less for years, lastly on my rs500, but in HDR, with the manual iris above -6, there are *lots* of gamma artifacts, up to the point that I've stopped using it in HDR most of the time.I'm not talking about pumping but about awful gamma artifacts, at least on the rs500.I'll look at this closely and I'll report, I got a call from UPS today, my rs2000 is in the UK, delivery expected Monday or Tuesday.
Are you using auto 1 or auto 2 ?
I haven't even bothered using the HDR modes on the eshifters. Without a ton of help it never looked that great. So I've been converting to SDR with madVR. No obvious issues with the DI.
I only mentioned SDR or HDR because of the iris setting that is likely to be different. The way you tonemap doesn't really matter.Whether you tonemap with custom curves or using MadVR pixel shader, it's the iris setting that causes the gamma artifacts, at least on the rs500.Iris = 0 worstIris = -6 worseIris = -10 decentIris = -15 no issueSo you're more likely to see issues in HDR (tonemapped by MadVR or custom curves) with the iris at 0 than in SDR with the iris at -10 or less, at least on the older models. and I mean HDR or SDR content, not the way you tonemap.Of course auto1 is more agressive than auto2, so I'm assuming auto 2 (the above is using auto 2).Hence my question again: what is you manual iris setting during these DI evaluations?