You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support needed for new Nikon RAW image codecs called "High Efficiency" and "High Efficiency Star", both of which are still stored in file containers with .NEF extension
#1508
Is your feature request related to a problem? Please describe
Hello. Nikon has released two new RAW image file compression formats with their latest flagship Nikon Z8 and Z9 cameras. The formats are called "High Efficiency" and "High Efficiency Star". RAW image contents compressed into files by these Nikon cameras with these new codecs are still stored within the container whose extension is .NEF, but they utilize new codecs not currently supported by Magick.NET.
The problem: the program ImageGlass uses Magick.NET to decode image formats, according to its author, @d2phap. Therefore ImageGlass cannot properly decompress and display images stored using these new Nikon codecs: all that can be seen in ImageGlass is the small embedded JPEG (?) image thumbnails but NOT the full RAW image. So support within Magick.NET for these new codecs is needed in order for these new Nikon files to be usable in projects using Magick.NET (such as ImageGlass).
Describe the solution you'd like
I respectfully suggest adding to Magick.NET the ability to decompress contents within the Nikon .NEF file container that use the new Nikon codecs mentioned above. Thank you for considering this! Sincerely, GitHub member "OldNikonShooter"
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
You will need to request for support for this in the libraw library that is being used to read those files. And it would be wise to add an image (zipped) to the issue here so I can test if support was added when I update the libraw library.
Hello @dlemstra. Can you please provide information how to connect with the owner/author of the libraw library you use in Magick.NET, so that I can make the requested suggestion to the appropriate party? In advance, thank you on behalf of the large community of Nikon owners affected by this issue.
@OldNikonShooter The Nikon Raw High Efficiency formats are from a codec that has a pending patent, so it will require proper licensing if LibRaw wants to avoid risks in the future by distributing it. Currently, I see LibRaw only supports the non-compressed versions, not the HE ones.
However, you can freely download the codec from Nikon's website (since Nikon has obviously licensed it), so perhaps it's possible to integrate it another way.
Is your feature request related to a problem? Please describe
Hello. Nikon has released two new RAW image file compression formats with their latest flagship Nikon Z8 and Z9 cameras. The formats are called "High Efficiency" and "High Efficiency Star". RAW image contents compressed into files by these Nikon cameras with these new codecs are still stored within the container whose extension is .NEF, but they utilize new codecs not currently supported by Magick.NET.
The problem: the program ImageGlass uses Magick.NET to decode image formats, according to its author, @d2phap. Therefore ImageGlass cannot properly decompress and display images stored using these new Nikon codecs: all that can be seen in ImageGlass is the small embedded JPEG (?) image thumbnails but NOT the full RAW image. So support within Magick.NET for these new codecs is needed in order for these new Nikon files to be usable in projects using Magick.NET (such as ImageGlass).
Describe the solution you'd like
I respectfully suggest adding to Magick.NET the ability to decompress contents within the Nikon .NEF file container that use the new Nikon codecs mentioned above. Thank you for considering this! Sincerely, GitHub member "OldNikonShooter"
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: