D-Log M signal mapping for scopes and assists #51
erik-sutton95
started this conversation in
Ideas & Feature Requests
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Nano (and Action D-Log M bodies) need honest WAVE / zebra / false color / Face Priority math for D-Log M, not Pocket D-Log (2017) used as a stand-in.
Related: Finish Osmo Nano · Start Action 6 · roadmap index
Current mapping (the gap)
ColorMode.dLogM = 0x00exists and is labeled “D-Log M 10-bit.”MonitorTransfer.init(_ colorMode:)maps both.dLogand.dLogM→.dlog(DJI D-Log 2017, peak 4200%). Scope ceilings in tree are Pocket live-tap measurements:There is no Nano D-Log M measured shelf. ISO tables treat D-Log M like Normal (base 100, Auto allowed), which is not Pocket D-Log’s base 400.
Official Rec.709 cubes are in the bundle:
DJI_Official_Nano_DLogM_Rec709_33.cubeDJI_Official_Action6_DLogM_Rec709_33.cubeDJI Auto can apply them. Built-in Auto does not. Scopes still linearize D-Log M as Pocket D-Log, so middle gray and clip are wrong on Nano.
Workstreams
1. Transfer type
MonitorTransfer.dlogM(do not keep aliasing to.dlogunless a paper + tap prove they match)2. Live-tap calibration
ScopeExposureCeiling(same method as Pocket D-Log / D-Log2)3. Looks
family == .nano && color == .dLogMOfficialDJILUT.dLogM(cameraName:))Do not
Done when
On a Nano in D-Log M, WAVE 0 / 18% / 100 match the paper + measured tap, zebra/false color agree with that, and Built-in Auto can apply the official D-Log M cube.
Concrete threads: Finish Nano · Action 6
All reactions