nikon d810 & nx2 incompatibility question

[locosmike]

hi everyone,
I've been using NX2 software since ages with my D700 oldschool camera, but I got d810 recently and NX2 doesn't work with 810's  nefs anymore.
I know that is the tool raw2nef but the biggest drawback is that after conversion the file size is double than initial ( which makes the proccessing really laggy and eats my hard drive easily)

So I've modified the 810's exif by updating the CAMERA MODEL to nikon d800.
Suprisingly NX2 has no problem with opening it but there has to be something more done in order to display the picture correctly:


so my question is - do you think this pinky colour cast is due to wrong exif data input by nx2 or d810 file structure is different than d800 (last camera model supported by nx2) ? 

if this is regarding exif reading - what exif tag would need to be updated as well as camera model ?

ps
except for this colour cast - the file itself works like a charm, can be modified and processed without a single issue.
any advise would be appreciated !

[Phil Harvey]

The pink cast could be caused by incorrect black level metadata.  Generally, I would think that the structure of the files should be compatible if the cameras have the same sensor.

- Phil

[locosmike]

Phil,
Thanks for reply and your suggestion, really helpful!

When I compared the files, only d810 ones have implemented black level tag.
The other difference I've found is the WB Levels tag - RGGB vs GRBG

[MakerNotes]    WB RGGB Levels                  : 514 256 256 323   d810
[MakerNotes]    WB GRBG Levels                  : 256 505 352 256   d800

So I got more questions now:

1) how to remove black level tag  (I've tried: exiftool -BlackLevel= FILE, but it doesn't work / is this tag even removable ? )
2) do you think that WB level data can be messed up because of different RGB channel order for each camera?
3) CFA Pattern  tag - can this tag be modified from RGGB to GRBG one ? 

thanks

[Phil Harvey]

The different channel order (RGGB vs GRBG) is a killer, and is likely the result of a different sensor layout.

Given this difference, I don't think there is any metadata change that will allow you to do what you want.

- Phil

[locosmike]

thanks again, seems like no easy goal.