Ugly Hedgehog - Photography Forum
Home Active Topics Newest Pictures Search Login Register
Main Photography Discussion
Lightroom vs. NX Studio
Page <prev 2 of 3 next>
Sep 28, 2021 10:47:45   #
joer Loc: Colorado/Illinois
 
joer wrote:
I'm curious as to the source of your statement.

I used NX Studio for some time and now use Capture One...in my opinion C1 is much better.


Edit: I was not using NX Studio but the earlier version. Still curious about raw editors not using the full raw file.

Reply
Sep 28, 2021 11:30:18   #
CHG_CANON Loc: the Windy City
 
joer wrote:
Edit: I was not using NX Studio but the earlier version. Still curious about raw editors not using the full raw file.


A recent study found that 68% of the statistics on 37% of the discussion boards are 84% made up.

Reply
Sep 28, 2021 14:31:15   #
gessman Loc: Colorado
 
CHG_CANON wrote:
A recent study found that 68% of the statistics on 37% of the discussion boards are 84% made up.


You're just pissin' people off now, dude. LOL

Reply
 
 
Sep 28, 2021 14:35:42   #
CO
 
joer wrote:
Edit: I was not using NX Studio but the earlier version. Still curious about raw editors not using the full raw file.


Camera makers don't share any coding information with third party manufacturers. Third party manufacturers have to reverse engineer everything whether it's for software or lenses.

Reply
Sep 28, 2021 15:10:08   #
CamB Loc: Juneau, Alaska
 
CHG_CANON wrote:
A recent study found that 68% of the statistics on 37% of the discussion boards are 84% made up.


Are you 100% sure of this?
...Cam

Reply
Sep 28, 2021 15:17:41   #
CamB Loc: Juneau, Alaska
 
StLouie1970 wrote:
I'm trying to learn more about Lightroom, but currently I am using Nikon NX Studio.
Is anyone familiar with both?
I'm trying to find out if Lightroom does THAT much more than NX Studio to justify the cost.
I'd say 80% of my photos are kids/sports related...although I'm trying to learn more nature photography.
I'd love to hear any input. Thank you.


I'm sure NX is a fine editor for Nikon files but it is not a full solution for keeping track of your files and your work. It doesn't 'talk' directly to Photoshop and it doesn't use keywords or other photo finding techniques. I would be lost without a quickly searchable and customizable data base. NX won't find files featuring "red themes taken in England in the last ten years." This is the type of information I need from my programs. Plus being able to edit them.
...Cam

Reply
Sep 28, 2021 22:33:44   #
JD750 Loc: SoCal
 
joer wrote:
I'm curious as to the source of your statement.

I used NX Studio for some time and now use Capture One...in my opinion C1 is much better.


“Nikon software will automatically apply camera settings such as picture controls, dynamic lighting”

Since aftermarket programs do not do this they are not utilizing all the information in the raw file.

Raw files contain the images and other info. So the statement “aftermarket programs don’t use all the raw info” does not mean aftermarket programs don’t process all of the image.

However only the manuf knows the secret raw formula, the other companies have to reverse engineer it.

Reply
 
 
Sep 29, 2021 06:37:04   #
joer Loc: Colorado/Illinois
 
CHG_CANON wrote:
A recent study found that 68% of the statistics on 37% of the discussion boards are 84% made up.


I believe this...just like this one.

Reply
Sep 29, 2021 09:01:27   #
Bill_de Loc: US
 
joer wrote:
I'm curious as to the source of your statement.

I used NX Studio for some time and now use Capture One...in my opinion C1 is much better.


I first heard it at an Adobe seminar with Jeff Schewe. I believe it was also pointed out in a book, "Camera Raw" by Jeff Schewe and Bruce Fraser

From Adobe website:

The Adobe DNG Converter enables you to easily convert camera-specific raw files from supported cameras to a more universal DNG raw file. Another benefit of using the DNG Converter is backward compatibility.

I can't remember the source (it was from Adobe somewhere) but it was said that when you process an NEF file, for example, through an Adobe product it uses the same data as if you first converted it to a DNG file. It doesn't delete data, so it is still there if you decided to use the camera manufacturer's software.

Reply
Sep 29, 2021 10:47:17   #
JD750 Loc: SoCal
 
Bill_de wrote:
I first heard it at an Adobe seminar with Jeff Schewe. I believe it was also pointed out in a book, "Camera Raw" by Jeff Schewe and Bruce Fraser

From Adobe website:

The Adobe DNG Converter enables you to easily convert camera-specific raw files from supported cameras to a more universal DNG raw file. Another benefit of using the DNG Converter is backward compatibility.

I can't remember the source (it was from Adobe somewhere) but it was said that when you process an NEF file, for example, through an Adobe product it uses the same data as if you first converted it to a DNG file. It doesn't delete data, so it is still there if you decided to use the camera manufacturer's software.
I first heard it at an Adobe seminar with Jeff Sch... (show quote)


Just out of curiosity have you tested this? I would expect that converting to DNG changes the raw file and the manuf software won’t read it after that.

Reply
Sep 29, 2021 10:59:18   #
CHG_CANON Loc: the Windy City
 
JD750 wrote:
Just out of curiosity have you tested this? I would expect that converting to DNG changes the raw file and the manuf software won’t read it after that.


I have tested it. The 'conversion' of the camera RAW to a DNG strips the camera- / brand-specific EXIF that is proprietary to the camera. Adobe retains most of the original data (the EXIF standard values), and then also adds their own EXIF along with this stripping. The most obvious loss is autofocus information, data that would allow the photographer or others to analyze camera set-up issues within the image.

Both the software from Nikon and Canon will retain this info into the output JPEG from their converted RAW formats. Adobe strips this info from the export / save-as results of a converted RAW, as well as when converting the RAW to DNG.

In 2021, there's no valid reason to just 'default' to DNG. The Adobe products operate on native RAW formats after failing to displace RAW, in the marketplace, with their DNG. All the competition software titles also operate on the native RAW formats. The only 'space' saving a DNG could initially obtain is via this replacement of the EXIF, data that is nothing more than text values in the 'header' of the image file. The image data 'payload' under that header is read-only and not changed in size nor structure via the DNG. Also, as you begin to edit the DNG and Adobe writes their own edit-instructions into the header area, the overall file size of the DNG increased beyond the original RAW size on disk.

Reply
 
 
Sep 29, 2021 11:47:00   #
Bill_de Loc: US
 
JD750 wrote:
Just out of curiosity have you tested this? I would expect that converting to DNG changes the raw file and the manuf software won’t read it after that.


Sorry. Converting to DNG creates a new file, but does not alter the NEF (Nikon) file. If I convert to DNG I also save the NEF. I have read that the NEF can be saved within the DNG, but I have never tried it.

The Digital Negative specification allows for not only all of the pixel information stored in current raw formats, but also for all of the additional, proprietary metadata that many manufacturers include. The Adobe DNG Converter may, in some cases, ignore some of this proprietary metadata, and only include the basic information necessary for creating a high-quality image file. The original raw file, however, can also be embedded in the new DNG format to ensure that proprietary metadata from the manufacturer is not lost.

https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html

--

Reply
Sep 29, 2021 14:31:17   #
JD750 Loc: SoCal
 
CHG_CANON wrote:
I have tested it. The 'conversion' of the camera RAW to a DNG strips the camera- / brand-specific EXIF that is proprietary to the camera. Adobe retains most of the original data (the EXIF standard values), and then also adds their own EXIF along with this stripping. The most obvious loss is autofocus information, data that would allow the photographer or others to analyze camera set-up issues within the image.

Both the software from Nikon and Canon will retain this info into the output JPEG from their converted RAW formats. Adobe strips this info from the export / save-as results of a converted RAW, as well as when converting the RAW to DNG.

In 2021, there's no valid reason to just 'default' to DNG. The Adobe products operate on native RAW formats after failing to displace RAW, in the marketplace, with their DNG. All the competition software titles also operate on the native RAW formats. The only 'space' saving a DNG could initially obtain is via this replacement of the EXIF, data that is nothing more than text values in the 'header' of the image file. The image data 'payload' under that header is read-only and not changed in size nor structure via the DNG. Also, as you begin to edit the DNG and Adobe writes their own edit-instructions into the header area, the overall file size of the DNG increased beyond the original RAW size on disk.
I have tested it. The 'conversion' of the camera R... (show quote)


That is good info thank you for providing that.

Reply
Sep 29, 2021 14:33:07   #
JD750 Loc: SoCal
 
Bill_de wrote:
Sorry. Converting to DNG creates a new file, but does not alter the NEF (Nikon) file. If I convert to DNG I also save the NEF. I have read that the NEF can be saved within the DNG, but I have never tried it.

The Digital Negative specification allows for not only all of the pixel information stored in current raw formats, but also for all of the additional, proprietary metadata that many manufacturers include. The Adobe DNG Converter may, in some cases, ignore some of this proprietary metadata, and only include the basic information necessary for creating a high-quality image file. The original raw file, however, can also be embedded in the new DNG format to ensure that proprietary metadata from the manufacturer is not lost.

https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html

--
Sorry. Converting to DNG creates a new file, but d... (show quote)


Ok I assumed you converted to DNG then deleted the NEF. So what is the purpose of creating the DNG if you are also saving the NEF?

Reply
Sep 29, 2021 14:46:44   #
DirtFarmer Loc: Escaped from the NYC area, back to MA
 
Bill_de wrote:
Sorry. Converting to DNG creates a new file, but does not alter the NEF (Nikon) file. If I convert to DNG I also save the NEF. I have read that the NEF can be saved within the DNG, but I have never tried it.

The Digital Negative specification allows for not only all of the pixel information stored in current raw formats, but also for all of the additional, proprietary metadata that many manufacturers include. The Adobe DNG Converter may, in some cases, ignore some of this proprietary metadata, and only include the basic information necessary for creating a high-quality image file. The original raw file, however, can also be embedded in the new DNG format to ensure that proprietary metadata from the manufacturer is not lost.

https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html

--
Sorry. Converting to DNG creates a new file, but d... (show quote)


It is possible to embed the original file into the DNG file but I don’t see any point to that. That will increase the file size. Why convert to a larger size when the original file will work fine.

The only reason to use DNG in my opinion is when you have a new camera and your editing software hasn’t caught up with the new camera format. That is normally a temporary condition so you should keep the original raw file for future use.

Reply
Page <prev 2 of 3 next>
If you want to reply, then register here. Registration is free and your account is created instantly, so you can post right away.
Main Photography Discussion
UglyHedgehog.com - Forum
Copyright 2011-2024 Ugly Hedgehog, Inc.