NikonGear'23
Gear Talk => Processing & Publication => Topic started by: Fons Baerken on March 04, 2021, 10:23:42
-
Nikon offers new editing software, NX studio.
About NX Studio
NX Studio software offers a full-fledged suite of intuitive tools for viewing, processing, and editing photos and videos. It combines the photo-and-video-viewing features of ViewNX-i with the photo-processing and retouch tools of Capture NX-D in a single, comprehensive workflow. Not only can it be used to process RAW pictures, but its editing tools—including tone curves and brightness and contrast adjustment—can also be applied to JPEG/TIFF images. It also offers a variety of features for such tasks as editing XMP/IPTC data, managing presets, viewing maps that show shooting locations based on location data embedded in pictures, and uploading pictures to the Web.
https://downloadcenter.nikonimglib.com/en/download/sw/195.html (https://downloadcenter.nikonimglib.com/en/download/sw/195.html)
-
Here's an initial review:
https://www.dpreview.com/reviews/nikon-nx-studio-review
-
Quick edit with nx studio
no adjustments
D3s 24-70/2.8
-
It doesn't look like I'll be able to use NX Studio on my older MacBook Pro. :(
-
Thanks, did not see that one coming - interestingly, the review comes before DPR has published the official announcement. It is on the Nikon site though:
https://www.nikon.com/news/2021/0304_soft_01.htm (https://www.nikon.com/news/2021/0304_soft_01.htm)
I am looking forward to try it out, but I think I will start with a check out in a fresh VM first as I am not sure if we can keep both CNX-D and the CNX Studio at the same time.
-
Thanks for the link Fons ! I am now downloading it, and reading the link, thanks Akira.
-
Tried it out quickly on my MacBook Pro (2015) with 16 GB memory and 2.8 GHz processor. It seems very slow. When I make an adjustment, I have to wait some seconds until I get a response.
-
Tried it out quickly on my MacBook Pro (2015) with 16 GB memory and 2.8 GHz processor. It seems very slow. When I make an adjustment, I have to wait some seconds until I get a response.
I have a Windows 10 Lenovo T460S from 2017 and even on battery power and editing 45 MP files, it responds quickly. Not instantly but quickly (most adjusments with << 1 s delay). Exporting takes several seconds though.
-
I just downloaded and is much quicker than NX-D I used to work in my laptop :)
NX- D still working
-
Tried it out quickly on my MacBook Pro (2015) with 16 GB memory and 2.8 GHz processor. It seems very slow. When I make an adjustment, I have to wait some seconds until I get a response.
After a reboot it responds much quicker :)
-
Imo software should be left to specialists. Also, Nikon software has a bad reputation on compatibility with new versions for operating systems. I would prefer if Nikon spent the resources and money on speeding up the release of new Z-lenses and thus broadening it's user base.
-
I guess it works, but the above image is a result of not changing anything ;)
Z6 105DC
below the ACR result (all without any crop)
-
NX Studio will not open *.ndx files used to "Save all adjustments." This is a major monkey wrench for me. Utterly Stupid! :o
What this means to me is I'll have to open ever NEF file I ever developed with Capture NX-D. Apply an NDX file to make sure the *.nksc (side car) file is current. If I have made several NDX files I'll have to do this for each one. Close CND-X. Open NX Studio and save all adjustments as a new *.NKA file.
I'm trying NX Studio on a school HP ProBook i5 with a cheep, dim, ugly color display. Maybe I'll find a way to convert the NDX files to NKA files. I doubt this. Nikon did fix Capture NX-D so it would read the edits of Capture NX2. I don't know how well that worked. I'll have to read the Read Me file for NX Studio.
I might like NX Studio. I'll have to see but Nikon really dropped the ball on this one.
Dave
-
I like the new UI, it's more or like DxO Photolabs, but more basic.
It has some basic DAM features (good enough for me) and selection possibilities.
This replaces Capture NX-D, ViewNX-1 and Nikon Transfer.
-
*.NDX files (Capture NX-D, Save all adjustment files) are not mentioned in the NX Studio Readme.rtf.
-
It appears that NX Studio will open *.NDX files but one cannot select the *.NDX file [from a list] in NX Studio, Load all adjustments dialog. [One can cut and paste the NDX file name and paste it into MX Studio and NXS will open the NDX file.] More experimentation needed. [I may be talking trash.]
Dave
Why this matters to me...
In Capture NX-D and I'd think NX Studio the user has little if any control over the *.nksc side car files. Because of this I have mostly ignored the side car files as Nikon's temporary files. I don't save TIF/TIFF files from D800 and D850 DSLR(s). They are too large. I use the TIF files to transfer the developed NEF to an older version of Photoshop. If I need another TIF file I create it again by applying the NDX file and exporting to TIF again. I don't need this frequently so this is a minor annoyance.
Dave
Please send FREE 12T SSD drives!
-
May be I am missing something here, but if you have edited files normally in CNX-D, the adjustments have been saved in the .nksc files in the NKSC_PARAM sub-folder. So I do not understand the problem with the .NDX files. Those would normally only be written to save very specific settings, before to applying them to new files. (I.E. it is a format to transfer settings.) No need to save an .NDX file for every .nef file.
(Edited in parallell with last post, but still confused. It is a misconception to treat the ,nksc files as temporary files - they are the edits.)
-
Very interesting but stupid!
One can rename an NDX file to NKA, open it and it does nothing! There is no error message and there should be.
Hopefully Nikon will fix some of the rough edges in a sooner than later update to NX Studio.
Dave
NX Studio and Capture NX-D can run simultaneously. More testing needed.
-
May be I am missing something here, but if you have edited files normally in CNX-D, the adjustments have been saved in the .nksc files in the NKSC_PARAM sub-folder. So I do not understand the problem with the .NDX files. Those would normally only be written to save very specific settings, before to applying them to new files. (I.E. it is a format to transfer settings.) No need to save an .NDX file for every .nef file.
(Edited in parallell with last post, but still confused. It is a misconception to treat the ,nksc files as temporary files - they are the edits.)
The user has little or no control over the *.nksc side car files, e.g. make some edits, CNX-D saves those in the nksc file. Change your mind. Now what? Try to remember what you changed and change it back. Might be easy or if multiple steps changed near impossible.
Nikon controls the *.nksc files I control the *.ndx files. This has worked fine for me since Capture NX-D became stable enough to replace Capture NX2. 2
...also how do you save two or more *.nksc files for different use?
Dave
-
My first guess experimenting with NXS on a i5. Windows 10 laptop with a dubious flat screen outdoors in bright light: NX Studio is probably a major improvement over CNX-D. It's very difficult to see the menus and tools. I can't do any real developing of NEF files but I'm trying to get a feel for NX Studio. New cameras will probably not be supported by Capture NX-D forcing diehards to switch to NX Studio.
Dave
I kept CNX2 on my Windows desktop for a year or so until I didn't need it and then switched completely to CNX-D. I'll do the same with NXS.
-
Run batch processing is missing as it was in NX-D but you can edit multiple files the same time ;D
-
Can you not make a copy of the NEF file and then give each copy their own edits and those are stored by the software?
-
Boring. Installation was "successful", but after installation I could find no trace of the software, no shortcut, etc. Can somebpdy tell me where (which folder, in Win 10) the files are installed by default?
-
C:\Program Files\Nikon\NXStudio
-
Adjustment masks (gradient and brush) were a good thing in Capture NX. They are long gone in both NX-D and NX Studio.
-
Thanks. But there is no such folder...
During the installation process, I got (twice) a message that some old version of C++ redistributable failed to install (I presume because it's already there and used), install proc asked if it should proceed, replied yes, then install was successful. Hard to imagine that a missing redistributable would prevent the program from appearing under such circumstances. I gues I'll have to skip that one.
-
I found that it keeps NX-D but uninstalls View-NX-i which is not a big loss. (It also want to uninstall ViewNX2, but I have tricked it by renaming the folder.) At its current state it is lacking in some aspects of the user interface. For instance if one decide that there is need to adjust the crop, CNX-D will allow fine adjustment of the previous crop. Studio will reset the crop.
Also I am missing the ability to keep a bar with additional settings on the side as in CNX-D:
-
Can you not make a copy of the NEF file and then give each copy their own edits and those are stored by the software?
Yes but that involves taking a lot of space on a HD or worse the premium space on an SSD. NDX are about 10KB in size and NKA files only marginally larger.
NX Studio should be able to open NDX files and apply them to an NEF file if only in a read only mode. Additional edit could be saved in the new NKA file format. That would be enough for me.
Again the user has no control over the NKSC side car files. Some find them annoying and delete them. They are so small I just ignore them.
Dave
-
For instance if one decide that there is need to adjust the crop, CNX-D will allow fine adjustment of the previous crop. Studio will reset the crop.
:o >:( >:(
Quick test confirms this. Holding the shift key doesn't constrain the crop ratio but jumps to 100%. This is in opposition to many other programs (or at least my version of Photoshop). If I need a particular crop ratio to fit an xx Pica by xx Pica frame and I want to tighten the crop holding the sift key while adjusting the crop really help but the previous crop is thrown out so...
It looks like NX Studio will need a lot of work as Capture NX-D did when it was new. I'll probably like NX Studio in about a year.
<Ctri> + Z (Command + Z) will not undo the last crop. Not quite ready for Beta Testing.
Dave
Was NX Studio pushed out too soon due the the new M1 CPU (or whatever) Apple MAC(s)
-
Run batch processing is missing as it was in NX-D but you can edit multiple files the same time ;D
I just batch converted 4 NEF files to JPG files but there is no progress popup as in CNX-D. It looks like NX Studio is playing dead until the JPG(s) show up in the ribbon under the preview image.
To batch convert select thumbnails and then click the export button on the upper right. I still don't see a progress report. ???
Silly me! I should have looked in the opposite corner (extreme lower left).
Also if you check "beep" in options NXS will play La Cuccaracha or one of a hundred other WAV files in Windows.
Gone to look for a box or raisins...
Dave
The current NX Studio looks like a late Alpha Release almost read for Beta Testing. Is this familiar?
-
Boring. Installation was "successful", but after installation I could find no trace of the software, no shortcut, etc. Can somebpdy tell me where (which folder, in Win 10) the files are installed by default?
Yes I had to search to find it too... Only after restart the program logo is visible in my taskbar
-
The current NX Studio looks like a late Alpha Release almost read for Beta Testing. Is this familiar?
I don't really agree, I think NX Studio is more mature than ViewNX-i and Capture NX-D ever got, neither of which update the list of files in the directory being worked on in a timely manner. When exporting files using NX-D to create TIFFs, if the output is in the same directory as the originals, I have to close the app and restart it before the output becomes visible in the thumbnails. In ViewNX-i, if I grade the images with numbers are remove all the 2's, for example, and turn off filters, it can take 10 minutes before it updates the displayed thumbnails. I've learned a "trick" to get around that by moving to a different directory and then back to the one which I was working on, that usually results in the files being shown. But these kind of problems I have not run into with NX Studio. It appears to be a much more stable foundation to build software on. And I like it a lot. Simple, just works, no crashing, no "taking a lunch break before showing the images to the user".
The crop tool does need improvement.
-
Yes I had to search to find it too... Only after restart the program logo is visible in my taskbar
The old proven reboot procedure did not yield anything... no files, no shortcut. Bizarre.
-
It is quite good for a first release.
-
The old proven reboot procedure did not yield anything... no files, no shortcut. Bizarre.
Hmm.
C:\Program Files\Nikon\NXStudio is the directory where the application NXStudio.exe has been installed.
The installation put the link to the program to the Start Menu, including the recently added section at the top, there is also a NX Studio subsection of the Start Menu where it is. I dragged and pasted the link from Recently added to the tiles on the right so it'll be easy to find. NX Studio also got an icon on the desktop.
-
It works great for non pro image manipulation and will serve all Nikon social media posters.
I think social media posters are quite a heterogeneous group of people. ;-) We are posting on this forum which is a kind of social media. Some posters do minimal edits on a phone, some do extensive post-processing in Photoshop or equivalent.
-
+A couple of nice discoveries improved over CNX-D:
It is now possible to choose background shades of gray for thumbnails and image preview.
One can now choose to save adjustments either as sidecar files or into the NEF files. (However jpg preview in the NEF did not appear to be updated, could be a bug or feature.)
- As Ikka commented, undo is not possible. It is always grayed out in the menu. Thus it seems likely that this is a feature that was not completed in time (or there is a bug). It seems unlikely that this will not be fixed with time, but it presently looks like an unacceptable omission for professional use.
-
Since the edits are non-destructive, I don't necessarily "must have" Undo. But the crop tool not being integrated with rotate (as it was in NX2) and not allowing refinements after initial commitment to a framing looks very 1.00.
Perhaps we could suggest Nikon to allow a Lightroom-like "virtual copy" concept to be implemented; in this, multiple sidecar files would be introduced and one could choose to keep different versions of the edits without losing the access to the raw conversion settings.
I am just glad that the update thumbnail problem seems to be gone and that the program offers integrated browsing and more comprehensive raw conversion settings than ViewNX-i did. I'll still use LR and PS a lot, as I need LR for printing multiple images on one sheet of paper in an easy and automated way, and PS for access to more comprehensive retouching and sharpening tools as well as masks, but this simplifies the initial stages of editing for me and makes Nikon algorithms more accessible.
I think it may be a good idea to send bug lists and feature wishes to Nikon customer feedback, such as:
- if crashed or not installed correctly, which computer and OS was used?
- crop tool needs to be grown to NX2 level (i.e. can be readjusted at will at any time, integrated rotate by turning from sides or corners)
- undo should be available
- multiple sidecar files per one NEF file i.e. similar to Lightroom's Virtual Copies
- keyboard shortcuts
- interfacing with other software: the tags added in different software should be readable (I know this means some coordination between software makers is needed, but do it anyway)
-
I have a small question, which may or may not be answerable by any here:
When I travel, I use a rather antiquated little "netbook" running Win 7, and because my cameras came with it and it's a little less dreadfully slow, I still have a copy of VNX-2 for basic raw operations. I know that VNX-i is said to overwrite it and have never installed it. I do have CNX-D on that and my other computers, and the two run together. I keep VNX-2 because it processes files differently, and for certain very basic operations its a little faster and simpler (the netbook is not just slow - it's glacial!).
So my question is, does anyone know whether the new NX Studio overwrites VNX-2? If so, can one reinstall VNX-2 without conflict? I know I can get used to not having it, but would be happy to keep it if possible.
Meanwhile, I pine for the day that someone manages to make a cheap little Chromebook equivalent that runs Windows.
-
The more serious issue is that NX Studio will not install under Win7 :( Nikon has a long tradition of restricting their software to the latest OS generation.
I still keep some Win7 boxes for heavy data lifting and no-nonsense non-bloated operation.
-
The more serious issue is that NX Studio will not install under Win7 :( Nikon has a long tradition of restricting their software to the latest OS generation.
I still keep some Win7 boxes for heavy data lifting and no-nonsense non-bloated operation.
Right, but my understanding is that Win 7 is no longer a supported version and thus it could become a security risk if new holes are found. At least my employer notified about 1.5 years ago that Win 7 computers cannot be used on the network and if we do, the IT can disable such computers.
-
They run under a closed network section. No 'net access.
-
The 'Map View' feature of NX Studio is quite useful, by the way. And how nice it would be to have dockable windows. Never been a fan of monolithic software in terms of UI.
-
I realize Studio won't run under Win 7, which is why I am wondering whether it will clobber the View NX2 I have on Win 10, which I keep for compatibility with the version I have on Win 7, or whether I must stick with Capture NX-D (which does run on 7), but seems to work even slower there than the snail's pace of NX2.
-
Stupid: Very Stupid!
Because the shift key is used to view at 100% pixels a host of keyboard shortcuts no longer work and worse have no new or replacement keyboard shortcut. The only way to access the features that lost their shortcuts is to use the menu system.
Example: Ctrl + G to toggle grid in CNX-D. In MX Studio View> Image viewer options> (x) Show grid. No keyboard shortcut
Have I missed something? Am I talking trash?
There is a grid button on the lower edge but still no keyboard shortcut. I will survive!
Dave
More study needed.
-
Well, I played with NX Studio for a while and then . . . I scurried back to ACR!
The NX UI is not efficient.
Too many vital controls are hidden in the Prefs and require a restart every time before any changes to the Prefs become available to the User.
The Adjustments Panel is interminably long and needs excessive Scrolling.
There are no KBSCs.
NX seems to have been designed for those who shoots JPGs instead of RAW.
There doesn't appear to be a way to import my own xRite-engendered Camera Profiles.
NX Studio makes heavy use of the camera's internally recorded Settings and Picture Controls (which are something that I never use). It also wants to honour Active D-Lighting (something that is applicable to JPGs); and seems to base operations on other settings included in the camera's EXIF (all of which I inevitably ignore!).
NX also lacks many of the advanced tools (including Color Grading and a Smart Object workflow into Ps) which ACR now provides.
Neither did I get the impression that NX is any faster than ACR.
Bottom Line:
My previous impression of Nikon's Software has now been re-confirmed.
My copy of NX Studio has now taken a trip to Never-never Land via the Uninstaller.
-
NX seems to have been designed for those who shoots JPGs instead of RAW.
I doubt it. I've never been a JPG shooter; I felt it was too much of a compromise.
I use Nikon software for browsing, image selections and some editing because the software defaults to using raw conversion settings set in the camera. This saves time as when I view the images, the processing applied is as I have intended. I still refine the image adjustments when needed, but I have a better starting point because while shooting the adjustments made are respected by the browser and raw converter.
Furthermore, Nikon software shows the focus points and settings used in the camera. This helps me see what worked and what didn't and allows me to investigate why.
The Nikon software also obeys the white balance settings made in camera whereas ACR/LR makes its own interpretation of the white balance which is often quite different from Nikon's.
I also like sometimes to use D-Lighting and I can activate this in post-processing using Nikon software. There are also useful tools such as axial color aberration correction and PF flare correction.
Finally, I feel the conversions made by Nikon software look more natural and three dimensional and I feel this is lost when using other raw converters.
There doesn't appear to be a way to import my own xRite-engendered Camera Profiles.
Nikon software is useful for accessing Nikon profiles, picture controls and algorithms and applying them to raw files; other software exists for working with X-rite profiles and algorithms.
NX Studio makes heavy use of the camera's internally recorded Settings and Picture Controls (which are something that I never use).
Right, it produces almost exactly the same results as the camera at the selected processing settings (but with higher quality as JPG compression is not applied unless requested).
It also wants to honour Active D-Lighting (something that is applicable to JPGs); and seems to base operations on other settings included in the camera's EXIF (all of which I inevitably ignore!).
D-Lighting is a good algorithm and being able to adjust its settings when needed is one of the reasons to use this software.
NX also lacks many of the advanced tools (including Color Grading and a Smart Object workflow into Ps) which ACR now provides.
It doesn't prevent you from using ACR. Just set Open with to open Photoshop and voila, you have access to ACR conversions.
Neither did I get the impression that NX is any faster than ACR.
I am sure that it does convert files faster than I can adjust the ACR settings to match in camera settings for each image (if I have made such adjustments). I find it extremely annoying that even after 22 years of NEF file availability Adobe still haven't bothered to read in the in-camera settings and obey them. It's a productivity disadvantage, in my opinion. I time and time again ask them to address this issue but their effort, when it finally came, is half-hearted. ACR now can read the camera profile used but it doesn't do it correctly if I use multiple photo shooting banks in the camera. It always seems to take the picture control used in Shooting Bank A rather than the shooting bank which was active at the time of shooting.
My copy of NX Studio has now taken a trip to Never-never Land via the Uninstaller.
Good for you.
I will use NX Studio for most of my projects for browsing, image selections/deletions, and as a platform to make Nikon raw conversions, launch Photoshop on the produced TIFF images, launch ACR/Photoshop or DXO Photolab as alternative raw converters and editors that I use in specific cases, depending on what kind of processing I want to do to the image. I will still use LR for editing studio photographs which is where I use X-rite profiles (e.g. to homogenize the colors from LED and flash lights, though my subjects often prefer Nikon profiles, I like the X-rite for fully controlled lighting situations), and for when I need to print multiple photographs on one piece of paper, which LR allows in a very convenient way. I generally do the later steps of photo editing in PS or LR. What varies is mostly just the raw converter which I select depending on image.
Luckily there are different software available to suit individual photographers' needs.
-
"NX Studio makes heavy use of the camera's internally recorded Settings and Picture Controls (which are something that I never use). It also wants to honour Active D-Lighting (something that is applicable to JPGs); and seems to base operations on other settings included in the camera's EXIF (all of which I inevitably ignore!)."
I think that complaint of Ann's applies to all the Nikon software that precedes this. It's a blessing and a curse, I guess. For example, if you start out with D-lighting on, you can't turn it off in View NX-2. But you can turn it on if it wasn't there before. Similarly, other settings made in the camera are carried into the program, and though you can alter some, you can't always diminish them or remove them completely. On the other hand, if you're more or less satisfied with what you started with and what you saw on the camera's screen, you don't have to do anything to get there. I prefer to do as little post processing as I can get away with, and don't mind that, but I can see how someone not used to it would find it quite annoying.
-
NX Studio makes heavy use of the camera's internally recorded Settings and Picture Controls (which are something that I never use). It also wants to honour Active D-Lighting (something that is applicable to JPGs); and seems to base operations on other settings included in the camera's EXIF (all of which I inevitably ignore!).
Active D-Lighting is definitely not limited to JPG(s). This is a the point of view of people who use Adobe Camera Raw and other non-Nikon software that cannot make use of Active D-Lighting when developing NEF(s). I do not shoot JPG and I do use Active D-Lighting when I find it useful. I have it set to low in my D850 as Capture NX-2 didn't allow Active D-Lighting with my D300s unless it was on in camera. When developing an NEF I turn Active D-Lighting off or up to normal as needed.
Note that Canon and other camera makers use the same technology as Active D-Lighting under different names. I believe they all license it from the same company.
Dave
I apologize I just edited this an hour or two after posting it. If the following post quotes me and doesn't match it is because of my edits. I felt a need to clarify what I wrote and naturally there were typos and cut & past errors which are my hallmark.
-
To clarify, I never use ACR's (or anyone else's) Camera Profiles because I have made a complete set of Profiles for each of my cameras and also (for each camera individually) for every regular and odd-ball light-source that i have been able to find.
I use xRite's ColorChecker, followed by DNG Converter, to build these personalised Camera Profiles and I have imported them all into ACR.
Now I simply Batch-select all of the images from a shoot and apply the appropriate Camera Profile for the camera which was used, and the light-source under which the images were shot, and that provides my starting point.
Thus I mostly start the image processing with my Colour Balance and White Point in need of minimal tweaking.
Then I multi-select images which may need similar brightness, contrast or changes to some of the other controls and Sync the settings for the whole group.
This is probably not the way that most people like to work but it is actually very fast and I can easily process over a thousand RAW images this way in a day into a reasonably complete and usable state.
(Return from a trip with over 12,000 new Nefs, and you can understand why this workflow is helpful!)
When shooting, I simply use Neutral and leave all Picture Controls (especially Sharpening!) set to the Minimal or Off position.
ACR suits my own (perhaps rather idiosyncratic?) ways of shooting and processing because I always Process with the intention of storing my files still as RAW Nefs. I Keyword them and save them as Nefs with xmp Sidecars
When I need to use one of them, I re-open the NEF in ACR, make any additional tweaks that seem necessary and then "Open Object" (as a Smart Object and ProPhoto RGb 16-bit) directly into Photoshop.
I make final adjustments and refinements in Ps; apply (as the last step and always in a separate Layer) the exact kind of Sharpening needed for my Output purposes. That is because Press, Printer and Web require entirely different kinds and degrees of Output Sharpening
I then Save the file (in the appropriate format and Color Space) and can now Export it into a Page Layout program for the Press; or for Printing on my inkjet; or for inclusion in a Web Site and for Posting on the Internet.
I realise that mine is much more of a Production-oriented workflow than many Photographers will wish, or need to adopt; but, for the past 40 years, I have been in the rather unusual position of being the Photographer, the Art Director and the Production Manager for everything that we have produced.
Perhaps this also explains why I find that ACR provides me with the more complex editing tools and capabilities that I need; and why it also offers me a far more complete and versatile Workflow than NX Studio seems able to provide so far.
-
I mostly ignore Nikon's *.nksc (side car files) but rather save *.nxd (Save all adjustments) files in Capture NX-D. NX studio doesn't read these. >:( NX Studio introduces *.nka files that replace the *.nxd files. The only bridge I know of between *.nxd files and *.nka files is the *.nksc side car files.
It's possible to have both Capture NX-D and NX Studio running at the same time. So far they haven't crashed each other. 8)
---
At first Nikon ignored that users had a great deal of time invested in Capture NX-2 saved NEF files with many adjustments. Early version of Capture NX-D blissfully ignored these people's work. Now NX Studio blissfully ignores the hours invested in *.nxd adjustment files.
Here is how I move the edits saved in *.nxd files to *.nka files. Open Capture NX-D and open an NEF. Load the adjustments in a paired *.nxd file. Move to another NEF file so Capture NX-D saves an *.nksc file. Open the NEF just opened in Capture NX-D in NX Studio and "Save all adjustments" in the new *.nka file format. Yes, I know NX Studio is free. NO IT'S NOT. Those who buy Nikon cameras that produce NEF files are paying for NX Studio when they pay for their new black beauties. Nikon needs to fix NX Studio so it can read an *.nxd file and then save an *.nka version. NX Studio need not and probably should not save adjustments in the old *.nxd file.
I normally save only one paired *.nxd file, e.g. D850_DSC0000.nxd for each D850_DSC0000.NEF. Sometimes I save several *.nxd files per NEF. I'm sure there are good reasons for the new *.nka file but this change without real accommodation will waste many hour of my time. Every D800 NEF I've developed in CNX-D will have at least one *.nxd file associated with it.
A fine rant if I say so myself. :D
Dave
-
The Nikon File transfer module (import) is now a lot faster. !! It's still a pity it can't read other RAW files, like the RAF from Fuji.
Thanks for the Open-With link, Ilkka. It is fast to go directly to ACR. I also use Faststone for image-review, but need to see if Nikon NX Studio is just as fast.
-
I mostly ignore Nikon's *.nksc (side car files) but rather save *.nxd (Save all adjustments) files in Capture NX-D. NX studio doesn't read these. >:( NX Studio introduces *.nka files that replace the *.nxd files. The only bridge I know of between *.nxd files and *.nka files is the *.nksc side car files.
It's possible to have both Capture NX-D and NX Studio running at the same time. So far they haven't crashed each other. 8)
---
At first Nikon ignored that users had a great deal of time invested in Capture NX-2 saved NEF files with many adjustments. Early version of Capture NX-D blissfully ignored these people's work. Now NX Studio blissfully ignores the hours invested in *.nxd adjustment files.
Here is how I move the edits saved in *.nxd files to *.nka files. Open Capture NX-D and open an NEF. Load the adjustments in a paired *.nxd file. Move to another NEF file so Capture NX-D saves an *.nksc file. Open the NEF just opened in Capture NX-D in NX Studio and "Save all adjustments" in the new *.nka file format. Yes, I know NX Studio is free. NO IT'S NOT. Those who buy Nikon cameras that produce NEF files are paying for NX Studio when they pay for their new black beauties. Nikon needs to fix NX Studio so it can read an *.nxd file and then save an *.nka version. NX Studio need not and probably should not save adjustments in the old *.nxd file.
I normally save only one paired *.nxd file, e.g. D850_DSC0000.nxd for each D850_DSC0000.NEF. Sometimes I save several *.nxd files per NEF. I'm sure there are good reasons for the new *.nka file but this change without real accommodation will waste many hour of my time. Every D800 NEF I've developed in CNX-D will have at least one *.nxd file associated with it.
A fine rant if I say so myself. :D
Dave
While I absolutely agree that Studio should be able to read the CNX-D .nxd files and I am encouraging you to file a report with Nikon on it, I do not understand why you want to avoid relying on CNX-D and NC Studio automatically saving the .nksc files. It is effort free, appears compatible between CNX-i, CNX-D and NX studio. I am even able to get the edits automatically back to CNX-D after editing in Studio. There might be something I do not quite understand about your workflow, but without any further knowledge I would highly recommend you to in the future to rely on the .nksc files to store the edits and stop deleting those NKSC_PARAM folders if that is what you are doing.
-
I do not understand why you want to avoid relying on CNX-D and NC Studio automatically saving the .nksc files.
The problem with relying on the *.nksc files is if I experiment with adjustments and Capture NX-D has saved the *.nksc file then how do I get back to my best efforts (before experiments) on adjusting a image? If I've saved an *.nxd file I can load it and i'm back to a known set of adjustments.
I don't delete *.nksc files and I move NEF(s) from one folder to another with ViewNX-i or Capture NX-D as this keeps the *.nksc files associated with the NEF files.
To me the *.nksc files are Nikon's temporary files and other than moving NEF(s) with ViewNX-i or Capture NX-D I ignore them. Their size is only about 10KB so they don't use much space on an HD or SSD.
Dave
-
While I absolutely agree that Studio should be able to read the CNX-D .nxd files and I am encouraging you to file a report with Nikon on it...
How do I send Nikon a report or offer suggestions? Can someone drop a link?
I've sent an email to Nikon but it was probably send to the wrong place.
I am quite displeased with NX Studio's crop feature. It's unfinished and I think Alaph test quality, not even ready for Beta tesing. It's a major step backwards. I note that an image can be cropped in Capture NX-D and NX Studio honor the CNX-D crop but if the crop tool is clicked the CNX-D crop is history.
Also there are many times where Undo and Redo are grayed out. This should not have escaped in a v1.0.0 release. Again this is to me an Alpha test release. At least with Capture NX-D the first released were 0.9.x releases. They were rather rough but at least the user was forewarned.
Dave
---
My impression is Edit> Undo/Redo is so frequently grayed out I wonder why it is found in the Edit menu. :o
-
OK, I understand better now. May be one thing we should wish for though feedback is a versioning system, like in CNX2.
When CNX-D was released Nikon had a special bug/feedback reporting page, however we do not see that for NX Studio (yet). So feedback will probably have to go though the regular support channel: https://www.nikonimgsupport.com/ni/NI_ask_support?ctry=US&lang=en_US (https://www.nikonimgsupport.com/ni/NI_ask_support?ctry=US&lang=en_US) (or google 'Nikon customer support').
Keep in mind that a number of things were missing in CNX-D in the beginning, and Nikon did listen to a number of specific wishes, like the control points and ability to import files edited with CNX2. The inclusion of IPTC editing tab in studio and choice of saving edits to nefs seems to echo a suggestion I (and probably many others) made to improve CNX-D. It seems like while Studio looks somewhat polished in some respects, others did not make it in time like the undo. Perhaps they hoped to get it out CP+ and got rushed. With proper feedback we are probably going to get there, but it might take some time. Until then CNX-D will work well enough for me.
-
Perhaps they hoped to get it out CP+ and got rushed. With proper feedback we are probably going to get there, but it might take some time. Until then CNX-D will work well enough for me.
My guess is NX Studio was rushed out due to the Apple M1 CPU Mac(s).
I wish I could buy one. My old MacBook Pro is living on borrowed time. There may be a problem with the SSD in it but my fear is video ram is going bad. A friend's MacBook Pro, about 1 year newer than mine, needed a new logic board for $700.00 (USD). A Crystal Ball would have helped her. That $700.00 could have gone toward a new MacBook with the M1 CPU.
Thank you for the link!
Dave
-
I finally managed to install it on my other Win10 laptop. Strange it does not want to install on the M$ Surface pro.
For a CNX-D user, the new software feels familiar, and I have yet to find out the biggest changes.
One thing does not change, alas : there is no way to correct distortion manually - did I miss something ? as I am using lots of non-Nikkors, that's a small problem.
-
[Bored] The second time I try and launch NX, it freezes:hourgalss spinning, and some low CPU activity going on for hours. Had to kill it via the task manager. Third and subsequent time : same phenomenon. Pretty crappy release, it seems.
-
Even on one of my smaller laptops, NX Studio runs well. Snappy response in general. No hiccups so far. This is on a 16GB box with 1 TB SSD.
-
That's sure not the lack of RAM... just the usual poor stability of the Win platform when lots of apps have been installed, I'm afraid.
-
I have had NX Studio crash, disappear suddenly once maybe twice. Other wise it installed and has run without issues on a Windows 10 Enterprise i5 laptop.
Has anyone seen the Undo/Redo feature working? I think it's grayed out 100%. This is not indicative of a finished v1.0 release.
I find the LCH and Levels & Curves tools too small for precise adjustments. In Capture NX-D these tools could be un-docked and made large for precise adjustments. In Photoshop this type of adjustment can be bumped 1 or 10 points at a time numerically.
I hope NX Studio will mature in to a viable program sooner than later.
Dave
-
Has anyone seen the Undo/Redo feature working? I think it's grayed out 100%. This is not indicative of a finished v1.0 release.
Grayed out on macOS as well. Tested several edits, but the Undo option stayed grayed out.
Whn I quit Nikon NX, the edits was saved without confirmation.
-
Grayed out on macOS as well. Tested several edits, but the Undo option stayed grayed out.
Whn I quit Nikon NX, the edits was saved without confirmation.
Edits saved without confirmation is the reason I don't rely one the *.nksc (side car files). If I make edit and want to discard them they can easily be save against my will. It I experiment and make a half dozen changes then I would have to do a half dozen Undo or Ctrl + Z or Command + Z depending on the OS. With the *.nxd or new *.nka (save all adjustments) I'm in control. I can and sometime do save version and later delete those I don't need or want.
Anyway no undo/redo is not indicative of a version 1.0 program.
Dave
-
Even on one of my smaller laptops, NX Studio runs well. Snappy response in general. No hiccups so far. This is on a 16GB box with 1 TB SSD.
I have the same experience on both my desktop and laptop: it works well, pretty fast.
-
I have the same experience on both my desktop and laptop: it works well, pretty fast.
Same for me.
On a 2016 MBP and a 2019 iMac (both on Big Sur).
-
I'm trying to communicate with Nikon regarding the failure of NX Studio to read and apply the adjustments saved in *.NXD files to an NEF being edited in NX Studio....
"Can you please explain what you mean by .nka and .nxd files as all raw files edited by Capture NX-D or NX Studio are all NEF file types." --Nikon
NXD files are Capture NX-D files the user can save that contain all the adjustments the user has applied to an NEF file. In the Capture NX-D menu: Adjust> Save All Adjustments> to save an NXD file and Adjust> Load Adjustments> to apply adjustments to one or many NEF files.
NKA files are NX Studio files the user can save that contain all the adjustments the user has applied to an NEF file. In the NX Studio menu one will use Adjust> Save All Adjustments> to save an NKA file and Adjust> Load Adjustments> to apply adjustments saved in an NKA file to one or many NEF files.
Users can have hundreds or more hours in Capture NX-D *.NXD files. It is a grave oversight for NX Studio to fail to read and apply an NXD file saved in Capture NX-D to an NEF file being edited in NX Studio. This is reminiscent to Capture NX-D ignoring adjustments saved by Capture NX2 in NEF files for many versions. Nikon should have learned and not release NX Studio without the ability to read and apply the settings in an NXD file.
—
“As long as the sidecar file is present in the correct folder, NX Studio will be able to read these as well.” —Nikon
This is irrelevant to NX Studio’s failure to read and apply NXD files to an NEF file being edited in NX Studio. Again the user can have hundreds or more hours saved in NXD files and Nikon should not lightly obsolete the users work saved in the NXD files.
...I hope this makes sense. I'm sure there are bunch of typos. I tried to get this logical and cleaned up before sending to Nikon.
Dave
-
It's possible to use the *.nksc (side car files) as a bridge between *.nxd and *.nka files but one will have to run both Capture NX-D and NX Studio, open the NEF in Capture NX-D, apply *.nxd adjustments, close the NEF file to save the *.nksc file. Then in NX Studio open the NEF file and save an *.nka files. If there is more than one *.nxd files associate with an NEF file then this scenario will have to be repeated for all *.nxd files. This is slow and cumbersome. I'll have to do this for every NEF file from my D800 that I developed in Capture NX-D or start from scratch in NX Studio.
I've tried the above with a few NEF(s) from my D850 and it works. Converting all the *.nxd files to *.nka files associate with my D800 will take many hours, probably at least 100 hours. I don't have many NEF files I've developed from my D850 so the problem with D850 NEF(s) is relatively small.
Don't take your love away from me
Don't you leave my heart in misery
Cause if you go then I'll be blue
Breaking up is hard to do
--Neil Sedaka, Howard Greenfield
There is always a lyric for every occasion. :)
Dave
-
I am having problems with NX Studio crashing. If I resize my image using the mouse wheel the computer crashes and restarts. This has happened on 3 computers all with 16gbs of RAM. Can anyone offer me any help on this? I enjoy the program until it crashes.
-
I am having problems with NX Studio crashing. If I resize my image using the mouse wheel the computer crashes and restarts. This has happened on 3 computers all with 16gbs of RAM. Can anyone offer me any help on this? I enjoy the program until it crashes.
My advice is report the problem to Nikon. NX Studio V1.0.0 is clearly a Beta text version not a finished v1.0 program.
I would uninstall NX Studio and wait for an update, e.g. NX Studio v1.1.0 or similar. I would install the latest version of Nikon Capture NX-D. Under the hood CNXD is pretty much the same functionally. My observation is CNXD is slower than NXS. Otherwise anything you can do in NX Studio can be done in Capture NX-D.
Given time I expect NX Studio will be a useful program giving very good results, perhaps better than others, for developing Nikon NEF image files.
I'm in hurry up and wait mode.
Dave
-
A couple of questions for those that use NXStudio:
Where is there any option of semblance of a [Save] icon/button. Saves the Cntrl-S methodology every time I have a need for it. Not annoying but close to it.
Also, how to version a file? Versions appear at the bottom of the edit tools, but I see no way to create a version.
My version of Versions really only has an unusable greyed out button to click that with an arcane step saying "Apply Adjustment Steps". It cant' be clicked or anything. pretty much useless.
I edited an NEF(expendable file). Adjusted stuff randomly and obviously. Hoped to have an ability to see a version or something in the Versions tab. Zip!
Anyhow, after adjustments made, I saved as and over wrote the original NEF file. Made a few more edits again. now just did a save to overwrite the file yet again.
Went into Adjustment -> revert to original .. and back to original as stated it would do.
I have a small question, which may or may not be answerable by any here:
When I travel, I use a rather antiquated little "netbook" running Win 7, and because my cameras came with it and it's a little less dreadfully slow, I still have a copy of VNX-2 for basic raw operations. I know that VNX-i is said to overwrite it and have never installed it. I do have CNX-D on that and my other computers, and the two run together. I keep VNX-2 because it processes files differently, and for certain very basic operations its a little faster and simpler (the netbook is not just slow - it's glacial!).
So my question is, does anyone know whether the new NX Studio overwrites VNX-2? If so, can one reinstall VNX-2 without conflict? I know I can get used to not having it, but would be happy to keep it if possible.
.....
Yes it does.(both View-NXi and Studio) overwrite and delete VNX2.
But it's no issue to reinstall VNX2 back onto the system again, it will install again with no problem .. and from my experience works without problem.
Only change to ViewNX2(and maybe not something to worry about) is that the Picture Control Utlility doesn't get installed(actually a good thing), as ViewNXi, CNXD and NXStudio all install the later version of the utility.
If you do use the PC utility, the link to it via VNX2 will still work and opens the latest version if you have any of the other Nikon software installed.
It is irritating that for every update of the software, VNX2 will always get uninstalled again. In effect you need a copy of the last version of VNX2 on your system for when you do an update to ViewNX-i and I assume same with Studio too.
I never used ViewNX-i just brief looksy to see what it can do, if it can do anything .. but never used it.
I rarely used CNX-D too. Every now and again tho .. more so to not feel all Jurassic tho rather than any need. Had plans to update camera and CNX2 may have been made a bit redundant. I did get the hang of CNXD to a degree, and it felt like home when CCPs made a return to Nikon software.
ViewNX2 is still my go too 'viewer' for any NEF files I upload to the PC.
Still faster than anything else I tried. FSViewer came nearly close when used in jpg-preview mode.
@ Ann.
No matter that you do or don't use Nikon Picture Controls(profiles) .. the fact is that you can't escape it. The camera uses Nikon's profiles.. ie Picture Controls.
This is a point that is inescapable. Only reason you believe that you don't use them is that you don't use Nikon software, but the NEF straight out of your camera has data in the exif that shows the Picture Control values set in the camera.
I used to use Picture Controls quite a bit years ago in the sense that you could easily create your own Picture Control with Nikons' software and upload it to the camera.
in terms of 'batch processing' this is a method that simply cannot be beaten for speed. Every image out of the camera would have been 'batch processed' to your requirements without the need for any batch processing software external to the camera.
Anyhow the point is moot ... we each have our own biases and prejudices and we stick with that no matter the alternatives.
But what would have been nice for Nikon to have catered for would be that the camera owner could have tweaked the Picture Control settings with more allowances and the ability to use other software's profiling results translated into Picture Control settings for transfer to the camera.
I think back to the film reversal silliness that Nikon introduced with the D850 and how it was limited to jpg shooting only. Why they(Nikon's software developers) diddn't use the Picture Control system for colour reversal beggars belief!
They instead chose to 'choke the cameras firmware' with a superfluous menu item that most people will never look at or use .. where they could have easily accounted for it in Picture Control memory banks that most users leave untouched!
-
A couple of questions for those that use NXStudio:
Where is there any option of semblance of a [Save] icon/button.
Right, this is an issue, and although I use NX Studio, I haven't conclusively explored all its features. It seems the 1.0 version simply doesn't have all functions implemented.
What you can do is make copies of the NEF file and name and process those differently. Then whatever changed you make is "saved" to a sidecar file in the background.
But what would have been nice for Nikon to have catered for would be that the camera owner could have tweaked the Picture Control settings with more allowances and the ability to use other software's profiling results translated into Picture Control settings for transfer to the camera.
This would be nice, as soon as NX Studio became available I've started to use it again as my primary raw converter (as I used to with Capture NX2 which unfortunately doesn't support most of my cameras' NEF files). I just find Nikon's conversions more balanced and pleasant to look at and prefer their interpretation of the white balance as well. And I like to set the on-camera settings as close as possible to get the playback image to look the way I want it to look in most cases.
However, if it were possible to use picture controls and other processing settings in camera as starting points for third-party NEF conversion, it would be a valuable feature in my opinion. It would allow the photographer to use the settings in camera when they have time and then avoid having to do a lot of post work for those files where the photographer got it right in camera. For difficult or missed shots one could then adjust the settings.
I think Adobe simply would like each camera to be the same so that they don't have to taken into account any camera-specific features. But they are a big and highly profitable company and they could easily be able to afford the development time to more closely interpret Nikon's files and give closer heed to user settings in the camera. And they can do it for each major camera manufacturer.
I think back to the film reversal silliness that Nikon introduced with the D850 and how it was limited to jpg shooting only. Why they(Nikon's software developers) diddn't use the Picture Control system for colour reversal beggars belief!
I think this is a bit of an experimental feature that Nikon provided to make digitization easier and hopefully they will improve it over time.
Color negative reversal seems to be a topic which is not so easy to figure out yourself, how to do it with the kind of results you'd see with conventional printing or even a minilab. Nikon Scan did a really good job of it, and the GEM and ICE worked very well for color negatives. Let's hope these features find their way into cameras or post-processing software as well.
-
I edited an NEF(expendable file). Adjusted stuff randomly and obviously. Hoped to have an ability to see a version or something in the Versions tab. Zip!
Anyhow, after adjustments made, I saved as and over wrote the original NEF file. Made a few more edits again. now just did a save to overwrite the file yet again.
Went into Adjustment -> revert to original .. and back to original as stated it would do.
NX Studio v1.0.0 shows promise but it's a woefully unfinished beta release at best.
For saving various versions that won't be over-written automatically and without your choice there is an Adjustments> Save all adjustments> and Load adjustments> feature that saves an *.nka file that saves all your adjustments. Capture NX-D has the same feature but saves *.nxd files that are currently incompatible with NX Studio. I asked Nikon via some help page about the NX Studio's lack of ability to read and apply *.nxd files saved in Capture NX-D and they clearly showed they had no idea what the Save all adjustments and Load adjustments feature was for.
You can name the *.nxd and *.nka files anything you like so a description of the features used and the NEF for which they are intended is easy to note. These files will be written wherever you saved the last one so it's cumbersome to save them in the folder where the NEF resides. The *.nxd and *.nka files can be applied to any NEF file so if several NEF files need the same post processing you simply select those NEF files in a thumbnail view and load the adjustments. It's really lame that Nikon hasn't made the use of this feature smoother for the user and the failure of NX Studio to read and apply *.nxd files to NEF files is as I see it inexcusable.
Capture NX-D and NX Studio are not free! Those who buy Nikon cameras are paying for these programs. Just a small amount of additional effort on Nikon's part could make them smoother to use. They do produce excellent results.
For now I'm continuing to use Capture NX-D as NX Studio is so unfinished.
Dave
-
I have a small question, which may or may not be answerable by any here:
When I travel, I use a rather antiquated little "netbook" running Win 7, and because my cameras came with it and it's a little less dreadfully slow, I still have a copy of VNX-2 for basic raw operations. I know that VNX-i is said to overwrite it and have never installed it. I do have CNX-D on that and my other computers, and the two run together. I keep VNX-2 because it processes files differently, and for certain very basic operations its a little faster and simpler (the netbook is not just slow - it's glacial!).
So my question is, does anyone know whether the new NX Studio overwrites VNX-2? If so, can one reinstall VNX-2 without conflict? I know I can get used to not having it, but would be happy to keep it if possible.
Meanwhile, I pine for the day that someone manages to make a cheap little Chromebook equivalent that runs Windows.
To avoid repeating the reinstall of ViewNX2 every time NX Studio etc. is updated, just rename the program folder that contains ViewNX-2 (for instance to 'ViewNX 2-P', P for persistent 8) ) and recreate the shortcut.
However I have noticed one little annoyance lately: While viewNX2 will happily will change star ratings on the original nefs, once CNX-D has created a .jpg file, ViewNX-2 refuses to update the star rating or the color rating. I tried a reinstall without a folder rename and also to the very latest version (I have been running ver. 2.10.2 as that has been more stable), but that did not fix the issue. Likely a new version of CNX-D made some changes in how labels the created the JPGs. It seems that files edited last summer were OK, while at least from January the problems started to pop up.
Edit: I just tested a jpg exported from NX Studio and the good news there is that ViewNX2 does not have the same problems with re-rating those jpgs as the ones output from CNX-D.
Edit 2: I have to take that back, it appears that these problems only happens with certain files (all that were compared were captured with D500, but it also happens at least with AW1 files), and if so it happens similarly with output from both CNX-D and NX Studio. I have worked with a file that does not display the problem, but anything I do in CNX-D does not provoke the problem. It was compared to a problem file that was right before it in capture sequence.
-
For now I'm continuing to use Capture NX-D as NX Studio is so unfinished.
For me NX Studio has worked well and I use it as my daily browser / raw converter, have done so since it came out. I use it only to make the raw conversion and then continue in Photoshop to crop and do further adjustments, resize, sharpening and such things. I could use ACR/PS and for some things I do, but I enjoy the Nikon white balance and raw conversion algorithm output more. In NX Studio it is easy to activate either method.
What bothers me most among bugs in the first version is that if I rate the images by pressing a number key, sometimes it beeps and will not take in the rating, and so I have to repeat it to get it down. After setting a rating, I can move to the next image with arrow keys but not further than that, which is very annoying. I have to use the mouse to click on another image if I want to continue browsing.
It would be nice to get a more fully-featured editing and browsing product from Nikon. Perhaps NX Studio can get there over time.
-
Now I realized that after giving a rating, if I wait long enough, it will let me continue moving to other images with arrow keys, there is just a delay of several seconds which I must wait before attempting to move beyond the next image. Not a bug, just slow software. But the raw conversion seems to be happening at OK speed in NX Studio, so that part I'm quite happy with. Anyway, this observation will help me avoid frustration. I am just used to key presses being remembered so I can type as fast as I want, but this is not the case here.
-
... Not a bug, just slow software. ...
I used to have deathly slow response from Capture NX-D. Lately it's been much better. I don't know why. I tried the following and saw no change, probably no need. I may have tweaked this setting and forgot about it. Anyway I think it's worth a try. This has something to do with memory compression.
Nikon Gear...
Possible Speedup for Capture NX-D on Windows 10... (https://nikongear.net/revival/index.php?topic=10002.msg171747#msg171747)
Flickr...
Helpful Hint Improve Speed of Processing/Rendering when using
Capture NX-D (may work for Photoshop as well) (https://www.flickr.com/groups/1567431@N22/discuss/72157718933799740/)
Dave
---
On occasion I've found locating the Capture NX-D cache files and deleting them helps when CNX-D is acting strangely. The cache files can be deleted from inside Preference. Sometimes that helps, sometimes opening the cache folder and manually deleting everything inside it is required. I think this will work for NX Studio as well. I quit CNX-D. Delete the cache but do not empty the Recycle/Trash until I'm sure CNX-D is working correctly again. Again I believe this can fix things in NX Studio if the cache gets corrupted. In all cases the cache files are recreated as needed.
I've had problems with Photoshop where the preference get corrupted and have to be deleted. I learned to backup my PS preference so I can restore them (over-write the corrupted prefernces) to correct problems. If the PS preferences are deleted PS will create new default preference.
Dave
-
Although I discontinued to use Nikon software for years now, in favor of Lr/Ps; I still install the latest versions, mainly to check / verify some Nikon related parameters eg focus points. I’m running this on the latest Mac OS Big Sur release, without any apparent bugs or speed problems . :)
-
Although I discontinued to use Nikon software for years now, in favor of Lr/Ps; I still install the latest versions, mainly to check / verify some Nikon related parameters eg focus points. I’m running this on the latest Mac OS Big Sur release, without any apparent bugs or speed problems . :)
The speed problem that I have is just that when I rate images (I typically give five stars if it is a really good image, four if it may be somehow useful but is imperfect) I want to type the rating and move to the next image to be rated really quickly. In NX Studio, after I have pressed the digit key corresponding to the rating, I can move to the next image immediately using arrow keys, but if I want to skip giving that a rating, then moving to the next-next image doesn't work immediately, I have to wait 3-5 seconds before it lets me go there. If I am patient enough, no problem. But I'd like to be able to do this very quickly (i.e as quickly as I can type). Otherwise the NX Studio works well on my system. Export (raw conversion and writing to TIFF file) takes maybe 3 seconds.
I can try the trick David proposed to see if that affects the performance.
-
Nikon can do so much more with their Picture Controls .. quite frustrating in a way. And more so because it just oozes incompetence from the folks that make the choices that this or that software is now their new push.
Does anyone know, or have any hint of who is actually developing Nikon's recent software? .. anyhow doesn't matter, if they just outsourced it to a crew that knows how to make software .. and then listen to some of the feedback!
With the colour reversal comment .. it was so easy in CNX2 to adjust the tone curve to colour reverse the negative, save that job and use it to batch edit any other negatives I'd digitized.
In the utility, you can reverse luminance, just not colour tones. I can't imagine why they'd create such a limitation. Then(as they did back in the D3 - D300 era camera period) .. set up a website dedicated to Picture Control again where you can download Picture Controls, and make it a community based site where people can create and share their own efforts. If colour editing was incorporated into the tone curve variables, it would allow for the ability to reverse negatives .. thus negating the need for the colour negative entry in the D850's menu .. and only in jpg!!??
Yes definitely not free, but if Nikon sold 1 million ILCs in a year, that cost burden on the camera may only be one millionth of a cent! ;D .. it seems to be approximately the amount that Nikon seem to invest in some of their recent software!
I stopped using CNX-D as soon as I tried Studio for the first time.
CNX-D on my 7 year old desktop was slow, and they never updated the font sized well enough for a 4K monitor(and not at all in ViewNXi, that I ever saw).
As I still cling to D800 and earlier cameras for now, CNX2 was still enough for me when I did get to take a photo, and most times VNX2 was enough, with a tweak to picture control/WB/exp/highlight/shadow .. that usually sufficed for a bit.
I don't doubt that Studio will progress like Nikon's other software ended up doing so.
I recall the beta versions of CNX-D operated very nicely on this old box .. then came the official releases and lacked pretty much every editing tool you got used too, and slow and buggy.
In the end for me it was just slow.
Øivind! .. awesome reminder .. thanks. Also must remember to change the link to it in Transfer, as I have transfer set up to open VNX2 upon completion of upload.
Illka, the other weird happening with ratings in Studio that I see pretty much all the time: I have every image that I deem to be worth saving 'rated' in some way, numbers or stars, as has been Nikon's method since day dot.
Up to CNX-D and VNXi, all those ratings were saved in the maker section of the exif.. ie. in the NEF.
Why Studio can't see (pretty much) most of those ratings across so many images .. strange indeed.
It's random too tho, some come up with a rating .. most don't.
Also, whatever Nikon's new method of embedding into the original file means .. doesn't appear to be the same as what it used too mean.
Any rating made in Studio will not appear in previous software that I've seen. That is their notion of having embedded the saved edit/info into the original file has changed from previous years.
I just re-installed CNX-D to confirm this too. So it seems that the rating system, at least, in Studio is a bit flaky.
In VNX2(sometimes CNX-D) any rating and keyword(into ITPC) is saved into the image itself(NEF, I don't shoot jpg).
I use a very old .. laughably so! .. Microsoft program from about 100 years ... Photo Gallery. It shows me that ITPC info, and catalogs it for me too(bit of a help, but not vital). Photo Gallery(no longer available) work with Windows itself, and in combination with the Nikon's codec, Windows also understands this keyword/tagged info too. So in effect, my 'cataloging sytem' is Windows' indexing/searching. ie. negates the need for any catalog system.
Only 'downside' in terms of loss of the 'database' is really, only if I lose a file itself. The database itself is not important, so if I reinstall Windows, yeah, I need to rebuild the 'database' but Windows is continually updating it's database anyhow .. and it doesn't take long either.
This system works for me if i ever need to find an image .. just type it in Windows search.
Anyhow, In CNX-D(and VNX-i) even tho they only use sidecar file systems for saving any edits .. they still respected the keywording and rating I gave any file via VNX2(mainly) and sometimes in CNX2, if I forgot too in VNX2.
This is pretty much my #1 reason for using VNX2. Any keyword entered into the edit, is saved in the NEF .. and any image that opens this NEF will also see this keywording.
Note: the point of this info is not about my 'database' system .. it works brilliantly and this is my 'vice' or prejudice .. for now I need nothing else.
So CNX-D and VNX-i were really of no use to me. VNX2 was really my main go too software. I had hoped that Studio could replace VNX2 .. eg. if I get myself a newer model camera .. and Studio did indeed save edits into the file in the traditional way it used too in days gone by .. but they changed something.
None of the previous software will read Studio edits, or ITPC/keyword data, Windows won't either.
Question is, is it just a bug? or is it an inherent change in the method for saving into the original image.
I have no fear to save data into the original image.
In 15+ years of doing so with Nikon software, I've never had an issue.. and that I've seen even the older method of saving edits 'destructively' is not really.
While it's true that the camera original image has been edited, the file can be restored faithfully back to the originally as shot parameters as set in the camera(ie. tones and colours and whatnot).
What can't be reversed tho is that if you ever wanted to reload that 'original' image back into the camera to view it on the camera again! .. why anyone would NEED this specific ability, is not something I can comprehend.
So while it's true that the 'revert to original' is not explicitly true in the technical sense .. it is as original as needed by most folks.
Nikon's software edits are only written to the 'maker notes' section that describe how the raw file should be converted into an image on screen. In effect it's non destructive anyhow.. just no need for external sidecar files and saved copies of images that are just duplicates of the out of camera NEF, and then backing up those files again over and over .. simplifies backups.
So far as can be noted... Studio has now broken some part of a previous Nikon file ecosystem .. so be careful with it. I'm treating it purely as beta software .. a bit of a curio until it's bugs are worked out.
Speed. can't complain on this old FX8350(AMD) slug of a desktop. Fast enough SSDs seem to keep it ticking over at reasonable pace. Better than CNX-D(reconfirmed just now too).
Viewer sped is still not VNX2 speed tho. More so at initial start up, as once opened and images in a folder viewed previews are fast enough.
Seems like the preview database/thumbnails may only be temporary in some way?
Apologies for the tedious reply .. finding stuff as I type ..
So as I type, I also find that there is no way to set the preview images as the NEF file or the jpg preview file. obviously the jpg file will be quicker, maybe this could be why I see slower previewing for now after every start up of the program, and why once viewed preview is then instant.
In VNX2, preview is instant, except for the condition that any new NEFs uploaded and viewed for the first time. once the thumbnail database has been built, it's instant preview every time.
Overall VNX2 is still much faster. SO much so that if I have a series of images shot moments from the previous and next images, holding the left/right arrow keys the preview on the main window looks like a 15fps video.. ie. instant preview for as long as you like.
IN Studio, all I see is a black screen, and the film strip moving, but the highlighter on the thumbnail not moving with it .. ie. much slower.
In a one at a time keystroke from image to image, Studio is good enough as a viewer, 1 sec display, but not instant like VNX2 is.
CNX-D glacial on my desktop .. blurry image for a couple of seconds .. then finally! .. kind of experience.
-
Arthur, it's good to know that the ratings are incompatible across different Nikon software.
I can understand why they'd want to use sidecar files instead of modifying the NEF itself as a modified NEF may or may not work in 3rd party software or the camera. For example NEF files edited by Capture NX2 could not be used in DXO raw converter, a major problem for me at the time. That the edits are no longer stored in the NEF is a good thing from my perspective as I can choose to use DXO PhotoLab for specific images even if I have created TIFFs from them using NX Studio.
Ratings are a really important part of my editing workflow, and it's a pity that they are not maintained across different software.
-
From some quick experimenting it appears to me that VienNXi and NX Studio save and share XMP/IPCT data through the *.nksc, sidecar files. Capture NX-D and NX Studio share all adjustments for an NEF file in the *.nksc sidecar files as well.
I'm not aware of Capture NX-D ever writing to an NEF file, only to the *.nksc sidecar files. I recently did some bit by bit comparison of NEF files with and without XMP/IPCT data confirming this data is stored only in the *.nksc files.
ON1 Perfect Browser stores XMP/IPCT data in sidecar files as well. I don't remember the ON1 sidecar file extension. I haven't used ON1 Perfect Browser in a long time and don't have access to the computer it's installed on at this time.
Since the *.nksc sidecar files are probably proprietary to Nikon other programs that cannot access the *.nksc files will not see the XMP/IPCT data.
I hope I'm not talking trash: please correct me if I'm wrong. :)
Dave
-
Yes, it is one way street from ViewNX2 to the later versions that use sidecar files. Same with IPTC information. That is why I still like to initially rate and keyword in ViewNX2, as this information will stick to the file, and in case one want to start the edit over again by erasing the sidecar or want to use non-Nikon software, then that information is preserved and can be read back in to the sidecars again.
-
Yes, it is one way street from ViewNX2 to the later versions that use sidecar files. Same with IPTC information. That is why I still like to initially rate and keyword in ViewNX2, as this information will stick to the file, and in case one want to start the edit over again by erasing the sidecar or want to use non-Nikon software, then that information is preserved and can be read back in to the sidecars again.
I don't think ViewNX2 will work for me. My primary camera is a Nikon D850. I wonder about ON1 Perfect Browser 10? It saves XMP/IPCT data in sidecar files but files I think ViewNXi could read them. I'll have to check. If so then the ON1 sidecars would not be proprietary. At the time I gave up adding XMP/IPCT data with ViewNXi as ViewNXi and Capture NX-D became deathly slow when previewing an NEF with XMP/IPCT data added. Perhaps my windows desktop had an issue with memory compression.
At this time I have too many NEF files with no added XMP/IPCT information added to help me locate a file. I save NEF in folders with names in the form of <user name> <Pictures> <Nikon_D850> <D850_2021-mm-dd_00000> with a file name of "D850_DSC0000". This means I have to remember the camera and approximate date of a photograph and then look at thumbnails to fine a specific photograph. This is a default method of saving NEF that I never improved as time went on. It's out of hand at this point and takes too much time to locate a specific file.
Thanks for your replies. I'm in need of a practical system since I'm now on my 4th DSLR and I rolled the odometer over on my D800 once and it's about to roll over a second time. It would have rolled over a second time if I hadn't bought a D850.
Dave
-
I finally got it running. The issue was with the C++ redistributable.
First impressions
- display is slightly more speedy, but
- output is definitely slower (I get that annoying message "wait until blabla gets prepared" for about 5 seconds, during which everything is prozen)
Still wondering what the point is for this new release.
On the other hand, the menu is a bit less messy, but I still miss the possibility to correct distortion of non-registered lenses (old Nikkors, Zeiss, etc.). Basic functionality.
-
Still wondering what the point is for this new release.
Well, on my computer, ViewNX-i would sometimes (not always) take tens of minutes before it was willing to show the thumbnails in a folder after ratings have been set and 0's deleted, for example (no such problem with NX Studio). NX-D doesn't allow me to export to the current directory without each time setting the directory manually (also fixed in NX Studio). For my needs (which includes browsing, location map viewing, rating, raw conversion with Nikon algorithms with subsequent processing in Photoshop), NX Studio is a big improvement and has become my primary browser and raw converter after a seven-year exodus. Although I recognize it doesn't have all the features of NX-D (which in turn doesn't have all the features of Capture NX2) but these missing features are not ones that I would do in this part of my workflow (e.g. I crop in PS).
For some things I use Lightroom Classic instead of Nikon software. For example, for studio images I use xrite profiles and I apply them in LR. Also, I use LR for printing typically when I need to print multiple images on one piece of paper, or generally for batch printing. I could otherwise use LR as a starting point in general but it doesn't show focus points, fine tune settings or much other camera-specific data.
-
Still wondering what the point is for this new release.
The ViewNXi and Capture NX-D scheme is a bit disjointed and probably relates to "Free" ViewNX2 and extra cost Capture NX2. Since ViewNXi and Capture NX-D free it makes sense to combine them in a single viewer and NEF developing program. NX Studio probably was pushed out before its time because of the MAC M1 and M1X CPU computers and compatibility problems with new releases of macOS. For the time I think Nikon will continue adding compatibility for new cameras to Capture NX-D but not for long.
I'm still using Capture NX-D as NX Studio is so unfinished and beta quality. I hope a more finished version of NX Studio is coming soon as I'll switch gladly when it does. Capture NX-D was a mess even when a v1.0.0 was released but in time I stopped using Capture NX2 as I found Capture NX-D more useable.
I hope people will keep pressure on Nikon to finish NX Studio into a ready for prime time offering. As of now even Undo and Redo are grayed out. This is shameful. I feel Nikon is shooting itself in the foot the way it did by dumping an unfinished Capture NX-D on DSLR customers.
Dave
---
Well, on my computer, ViewNX-i would sometimes (not always) take tens of minutes before it was willing to show the thumbnails in a folder after ratings have been set and 0's deleted, for example (no such problem with NX Studio). ...
No wonder you have switched already.
Dave
-
An example of a Nikon algorithm that I have started to like and an example application.
Here I show the original image of a gull attacking a swan. I had just arrived and positioned my tripod and setup behind some grass in a place where I can get it close to the level of the water, the swan arrived and a gull made multiple attacks on it. I hadn't had time to make exposure adjustments.
This is what came out of the camera unadjusted and after application of Active D-lighting Extra High 2 and minor adjustments (curves + cropping), and the third image is with D-lighting Normal. I could have made masks in Photoshop for the birds but it would have taken time and with D-lighting I was able to recover a viewable image of a high-contrast situation with minimal work. D6, 300/2.8, f/2.8, 1250s, ISO 100.
-
Arthur, it's good to know that the ratings are incompatible across different Nikon software.
I can understand why they'd want to use sidecar files instead of modifying the NEF itself as a modified NEF may or may not work in 3rd party software or the camera. For example NEF files edited by Capture NX2 could not be used in DXO raw converter, a major problem for me at the time. That the edits are no longer stored in the NEF is a good thing from my perspective as I can choose to use DXO PhotoLab for specific images even if I have created TIFFs from them using NX Studio.
Ratings are a really important part of my editing workflow, and it's a pity that they are not maintained across different software.
Interesting!
DXO Photolab is the only thirdparty(ie. non Nikon) software that I haven't deleted off my PC. All others tried have been uninstalled.
My test bench method for comparing the ability of thirdparty software is to always compare images edited in CNX2 to the new software, so always edit in CNX2 then try to edit file to a similar 'look' in new software. I've never seen any issues out of Photolab having edited the image in CNX2 first.
Don't really use Photolab any longer, as CNX-D got an update and introduced colour control points again, even tho I rarely used it too, and now Studio has this ability. I'm fairly inept at editing without CCPs. My primary reasoning for using all these software was the future outlook when the time came to update to a model no longer supported by CNX2 and VNX2.
In fact this software is so important to me, that back in the day when the D5600 was available at a reasonable price, I still pined for a D5500 simply because of compatibility with CNX2 and VNX2. D5500 was not a must have the latest and greatest purchase, it was a whimsical spur of the moment click of the buy button for my daughter who suddenly had an interest in proper .. ie. non smartphone! .. photography.
-
Not a bug, just slow software.
I think there is a cleverly almost hidden progress bar perhaps on the lower left that shows the progress of saving those *.nksc sidecar files. I'm typing on a MAC that can't run NX Studio so I can't check.
If your computer is saving to a hard disk that has gone to sleep it may take some time for it to spin up. If this is the case the HD can be set to spin down or sleep only after it has not been used for perhaps 1 to 2 hours. Even at 2 hours an HD won't be left spinning 24/7. It's probably best not to spin an HD up and down frequently. If the computer in question is a laptop with an SSD then there is no need to have the SSD sleep. Some laptops have both an SSD and an HD so HD spin down could be an issue with these.
I don't think it's good to have an HD spinning 24/7 but also I read it's not good to have one spin up and down frequently. I think 1 to 2 hours is a good compromise. Did I just repeat myself? :)
Some have reported that Capture NX-D was deathly slow and other that it wasn't too bad. Maybe HD spin down was the issue. If so HD spin down would cause the same problem with NX Studio. Again? ???
Dave
I'm too tired to fix this post.
-
NXStudio appears to have a bit of a personality complex.
I re-installed CNX-D a few days ago to do some tests.
I had a folder from last year with images of my brother and I camping.
NXStudio doesn't seem to be consistent in how to display files previously edited by various software .. or more accurately it creates the illusion of inconsistency to the viewer.
In that folder of images I refer too, I used VNX2 as a primary editing tool. I find it's easier to edit for example whitebalance/picture control maybe some exposure .. etc. all in batches where needed on some, most or all images ... depending on image results.
VNX2 as a detailed editor is far too basic, and on some images I then send them to CNX2 for spot editing using for example colour control points here and there.
CNX-D, I used for 'optional' editing on some images .. more as a test for possible switch to this program if I needed too based on camera model purchases.
VNX2 and CNX2 both edit the NEFs with embedded instructions for how to display the NEF and in capable viewing software which depends on the NEF codec installed(ie. Windows Explorer and my use of Windows Photo Gallery).
So edits in VNX2/CNX2 are displayed as were edited .. perfect!
CNX-D as we know uses the sidecar file system and creates a folder(NKSC_PARAM) in the main folder where images are stored and edit steps are stored in .nksc files. Delete those sidecar files and CNX-D edits are gone.
If a file is not edited in CNX-D, the embedded edits are honoured by CNX-D. Once the .nksc file is created CNX-D ignores the embedded edit and uses it's own edit sidecar file.
NXStudio then comes along and it appears to me to honour the latest software edit processes.
That is, if no .nksc edit files are present it honours the embedded edit(VNX2/CNX2) without issue. Displays the rating/label made in those software too.
But if I edit the already edited images in CNX-D too, Studio prefers the CNX-D edit over the embedded edit instead. If I change the rating(already set in VNX2) Studio also maintains the CNX-D rating(if it has been altered).
Delete the NKSC_PARAM folder or individual .nksc sidecar file .. ie. nullifying any CNX-D edits and Studio then reverts back to the VNX2/CNX2 embedded edit. Studio can also revert the VNX2/CNX2 edited image back to it's original unedited state too if required.
I totally forgot that I edited the images in CNX-D in this folder(shot back in June 2020) and couldn't work out why my CNX2 edited images didn't look right in Studio .. then noted the hierarchy preference for displaying NEFs when edited.
@ David: Following on from the ITPC thread, if you used VNX2 to rate and tag your D850 images then used Studio to edit them you shouldn't have any issues. As long as you use Studio to view those images again, and not VNX2.
You should see parity between those two software at least in terms of tagged data, but edited images in Studio(as yet) will not display in that way in VNX2. Nikon seems to have altered the embedded editing method from VNX2/CNX2's embedded method now, in Studio.
As my edits in CNX-D were only ever for testing and maintaining some semblance of contact with the future of Nikon software .. I'm going to do a PC wide search for all NKSC_PARAM directories and delete them all so as to not confuse myself when using VNX2/CNX2 and Studio.
Have to say too, a bit disappointed that Studio will not add tag/keyword data in the same way of old when supposedly embedding it. Hope they will fix that aspect one day.
What happens is that using VNX2 to embed tag data, my Windows workflow works fine. Using EXIFToolGUI one can easily see the embedded XMP and ITPC data entered via those methods. But not the supposedly embedded Studio keyword data.
Where this is supposed to be saved too in the image, and it appears to be saved going only via Studio itself, it's not saved neither in the XMP or IPTC area of the raw files.
-
Here is an example of what can be done with Color Control Points in NX Studio. In this case I used Capture NX-D since NX Studio requires a newer OS than High Sierra and this old MacBook Pro won't run a newer macOS than High Sierra. As far as I can see the Color Control Points feature is the same in NX Studio as it is in Capture NX-D. I used nine control points to darken features surrounding the artichoke bloom to make the bloom look as though it was in a spotlight. To an extent the bloom was somewhat spotlighted by a Nikon SB-800 but it took the CCP(s) to enhance the effect. Out of the nine sliders offered by CCP I used smaller Size, lower Brightness and less Saturation. I used LCH, master lightness curve to darken the shadows and increase the contrast in the mid tones and high lights and also chroma to lower the saturation of the greens. A few other tricks were used but the most important was Color Control Points.
(https://live.staticflickr.com/65535/51233015903_51cf73d007_b.jpg) (https://flic.kr/p/2m4hAGp)
Globe Artichoke (https://flic.kr/p/2m4hAGp) by Dave Hartman (https://www.flickr.com/photos/mr_speedlight/), on Flickr
The lens used was an AF-S 105/2.8G IF-ED VR Micro-Nikkor. I was standing on stairs so a tripod was out of the question. I used AF-C, continuous servo auto focus and VR. The Artichoke was lit by a hazy sky and a Nikon SB-800 speedlight with a diffusion cap. The SB-800 was on the right and above. I would have had one hell of a time getting anything with my manual focus 105/4.0 AI Micro-Nikkor.
Here is the stright out of camera photo...
-
Here is an example of what can be done with Color Control Points in NX Studio. In this case I used Capture NX-D since NX Studio requires a newer OS than High Sierra and this old MacBook Pro won't run a newer macOS than High Sierra. As far as I can see the Color Control Points feature is the same in NX Studio as it is in Capture NX-D. I used nine control points to darken features surrounding the artichoke bloom to make the bloom look as though it was in a spotlight. To an extent the bloom was somewhat spotlighted by a Nikon SB-800 but it took the CCP(s) to enhance the effect. Out of the nine sliders offered by CCP I used smaller Size, lower Brightness and less Saturation. I used LCH, master lightness curve to darken the shadows and increase the contrast in the mid tones and high lights and also chroma to lower the saturation of the greens. A few other tricks were used but the most important was Color Control Points.
(https://live.staticflickr.com/65535/51233015903_51cf73d007_b.jpg) (https://flic.kr/p/2m4hAGp)
Globe Artichoke (https://flic.kr/p/2m4hAGp) by Dave Hartman (https://www.flickr.com/photos/mr_speedlight/), on Flickr
The lens used was an AF-S 105/2.8G IF-ED VR Micro-Nikkor. I was standing on stairs so a tripod was out of the question. I used AF-C, continuous servo auto focus and VR. The Artichoke was lit by a hazy sky and a Nikon SB-800 speedlight with a diffusion cap. The SB-800 was on the right and above. I would have had one hell of a time getting anything with my manual focus 105/4.0 AI Micro-Nikkor.
Here is the stright out of camera photo...
It is interesting (to me at least) that I prefer the original shot. It has better tones as well as including the lovely curves in the foliage.
-
A feature of NX Studio and Capture NX-D that may be under used is the Adjust> Save all adjustments/load adjustments feature>. This allows one to save multiple sets of adjustments for one NEF. The complete suite of adjustments are saved when the user chooses and can be saved with a meaningful name, e.g.D850_DSC2562_ccp.nxd or for the following rendition D850_DSC2562_ccp_lite.nxd (meaningfull to me anyway). Again on the old macOS I'm using Capture NX-D. If I were on a new macOS using NX Studio the file extension would be *.nka. The feature works the same way on NX Studio as on Capture NX-D but they don't read each others files. :o The only bridge currently between CNXD's *.nxd and NXS' *.nka files is the *.nksc side car files.
In the following version of this photo I've backed off the Color Control Points' negative brightness settings to reduce the darkening of the periphery, removed the LCH master lightness curve and there is almost no crop, just a sliver on the left. The Save all adjustments/Load adjustments feature allows me to save as many sets of adjustments as I like. I always include the NEF file name as a part of these adjustment files' name.
I'm using the old MacBook Pro because it has a very good display. The alternative is a school loaner HP Probook with a display that totally sucks.
Dave
(https://live.staticflickr.com/65535/51237192443_a0c41c9ac0_b.jpg) (https://flic.kr/p/2m4E1eH)
Globe Artichoke, alternate processing (https://flic.kr/p/2m4E1eH) by Dave Hartman (https://www.flickr.com/photos/mr_speedlight/), on Flickr
-
What happens is that using VNX2 to embed tag data, my Windows workflow works fine. Using EXIFToolGUI one can easily see the embedded XMP and ITPC data entered via those methods. But not the supposedly embedded Studio keyword data.
Where this is supposed to be saved too in the image, and it appears to be saved going only via Studio itself, it's not saved neither in the XMP or IPTC area of the raw files.
NX Studio is saving the XMP/IPCT metadata in the *.nksc sidecar files in the NKSC_PARAM folder. The lack of standards on where and how XMP/IPCT metadata is stored is making a mess. :o :o :o
Dave
I may try installing ViewNX2 in Yosemite and then copy and paste the app and it's library support files into High Sierra. I'd prefer a modern and supported app that can embed the XMP/IPCT data in the NEF that runs on the macOS. Which macOS is the 64,000 Dollar question. ???
I'm finding Adobe Bridge over-heats this old MacBook Pro. :o :o
-
In the following version of this photo I've backed off the Color Control Points' negative brightness settings to reduce the darkening of the periphery, removed the LCH master lightness curve and there is almost no crop, just a sliver on the left. The Save all adjustments/Load adjustments feature allows me to save as many sets of adjustments as I like. I always include the NEF file name as a part of these adjustment files' name.
I'm using the old MacBook Pro because it has a very good display. The alternative is a school loaner HP Probook with a display that totally sucks.
Dave
I think the green in the foliage in the original offsets the purple in the center. I'm saying this after viewing on a few different screens.
-
With the colour reversal comment .. it was so easy in CNX2 to adjust the tone curve to colour reverse the negative, save that job and use it to batch edit any other negatives I'd digitized.
Arthur,
This is still possible in both Capture NX-D and NX Studio using the Levels and Curves tool. Grab the lower left point (zero) and raise it to 255 then grab the upper right (255) and drag it down to zero. This is in the Levels and Curves tool not the LCH tool.
Note that doing this in NX Studio is a bit flaky either because of a bug or the small size of the tool graph. If the image reverses from positive to negative with a film negative scan you can drag the now upper left point to the right one pixel and the tag will still read "255" and the negative scan will again appear as a positive image.
Don't confuse LCH and Levels and Curves and you'll be fine. This reversing of color can be saved in various ways. I haven't explored this with a scan of a film negative so I can't be too specific but perhaps a custom Picture Control could be created.
Dave
Creating a Custom Curve in Picture Control Utility 2 might do the trick.
-
NX Studio 1.0.1 is available for download.
-
Thanks for letting us know. Have you tried it? Any improvments?
Dave
-
Thanks for letting us know. Have you tried it? Any improvments?
Dave
The download page lists a long list of small changes.
https://downloadcenter.nikonimglib.com/en/download/sw/199.html
"
• Added support for the Z fc.
• Added support for Russian.
• NX Studio can now link with the Wireless Transmitter Utility to display pictures immediately after shooting. You will need to:
- choose NX Studio for Open images with this application after transfer in the “select destination folder and application” dialog for Wireless Transmitter Utility version 1.9.5 or later and
- have placed a check next to Show Image Immediately After Shooting in the NX Studio File menu.
Support for a link with Camera Control Pro 2 is expected with the next public release of Camera Control Pro 2.
• Cropping a previously-cropped picture will no longer reset the previous crop.
• Anchor points can now be deleted from tone curves using the delete key.
• “Favorites” can now list up to 300 items.
• Albums can now hold up to 100 items.
• Rotations are no longer included when adjustments are copied or saved using Copy All Adjustments, Save All Adjustments, or Record All Adjustments.
• Disabling the Crop Tool now also disables:
- the crop selection pull-down menu,
- the “rotate crop” button,
- the crop dimension text-entry boxes, and
- the Show Cropping Grid check box.
• Addressed an issue that prevented export of large numbers of pictures using Export.
• Fixed the following issues:
- Color control points added after a picture was cropped would sometimes not be in the expected position.
- Tone curves with a slope of -45° would not be applied to pictures.
- Changes to rotated pictures using the retouch brush would not appear where expected.
- Saving pictures after adjusting labels and/or performing other adjustments would sometimes cause labels to disappear.
- Saving pictures would reset adjustments made by the user after:
▹ using Paste Adjustments to apply adjustments copied using Copy All Adjustments,
▹ using Load Adjustments to apply adjustments saved using Save All Adjustments, or
▹ applying adjustments using Record All Adjustments.
- Track logs created using the D6 could not be read.
• Adjusted the monitor scaling used when Auto was selected for Options > View > Size of Text and Icon.
• Fixed the following issues:
- A blue screen would in rare cases be displayed when pictures were opened.
- Paste Adjustments would not be applied when selected in the context menu displayed by right-clicking thumbnails.
- The export dialog would sometimes appear at the bottom left corner of the display.
- The cursor would return to the left end of Japanese-language file names entered in the Save All Adjustments “Save As” dialog when input was complete.
"
I installed it and it seems to work.
I had experienced the mentioned bug that the export dialog would sometimes appear partly outside of the screen, now that has been apparently fixed. Also it's nice the one can use delete key to remove curves control points without having to reset the whole curve as was previously the case.
One of the more annoying things with the 1.0.0 version was that after giving ratings to images it would slow down the responsiveness of the user interface to arrow keys. I'll be checking to see if there has been any improvement in that area.
-
Undo/Redo still does not work! :o :o :o
Nikon NX Studio is still a beta test program.
NX Studio still can't read Capture NX-D's *.ndx files. This is just like Capture NX-D could not to read Capture NX2's edits. This is a basic compatibility issue. Nikon doesn't learn.
Dave Who will continue using Capture NX-D for now.
-
I noticed a strange bug in the latest version of NX Studio. When I mark a set of thumbnails by clicking on one image (to start a range) and then shift-clicking on the last thumbnails (to signify the end of the range), sometimes the first selected image has changed so the included set of images in the selection include a few additional images earlier in the display than the first selected image. Thus before deleting the selected images, I have to check that the software is working correctly and does not end up deleting images that I did not intend to delete. Nikon always seem to find a way to introduce new bugs into the software, and the type of bugs that make one a bit worried whether one should or should not be using their software in the first place.
-
Nikon always seem to find a way to introduce new bugs into the software, and the type of bugs that make one a bit worried whether one should or should not be using their software in the first place.
I suggest using ViewNX2 to delete or cull images. Then move the deleted images out of the Recycle or Trash to a temporary folder and double check. ViewNX2 will allow viewing the embedded JPG in an NEF in D850 NEF(s) and I believe D500, Z6 II and Z7 II NEF(s) if you install the latest Nikon Codec into Windows or in the case of macOS the Codec needs to be installed in the version of the macOS. It was so stupid of Nikon not to fix the install program so it worked with El Capitan. The install failure occurs on the install attempting to install the movie editor.
To install ViewNX2 in version of the macOS that it will run with it has to be installed in Yosemite first and copied to later versions. I installed ViewNX2 in Yosemite and copied the ViewNX2 folder into High Sierra's Applications folder and it works. I ignored the Library Support files as there were files there from installing ViewNXi and Capture NX-D on this old MacBook Pro.
Even easier is to keep using ViewNXi and CaptureNX-D until Nikon gets its act together. I don't understand why Nikon keeps shooting its self in the foot. Is management so dull they don't know this is costing them customers?
Dave
For those with the latest Intel compatible macOS and those with the M1 chip I don't think any older Nikon software will run. I might be talking trash here. I'm not sure because I'm stuck at High Sierra on this Early 2011 MacBook Pro.
-
Something I do to avoid errors is I select a single photo as something might be selected elsewhere I can't see if there are many thumbnails on a page. Then I select the first image to be part of a group and hold the shift key and go to the last image and the group is selected without an error.
I do the same when holding Control or Command to select various photos not in a line or chain. Again by doing this I know pretty well that I'm not going to include a thumbnail that's out of view. After selecting one and being sure only one is selected I hold Control or Command and then select additional thumbnails.
These might help. They help me avoid errors. :-[
Dave
-
Something I do to avoid errors is I select a single photo as something might be selected elsewhere I can't see if there are many thumbnails on a page. Then I select the first image to be part of a group and hold the shift key and go to the last image and the group is selected without an error.
Right, this is how I do it as well but sometimes Studio adds images to the selection on its own (when making a multi-page selection). It's pretty scary actually, I'm wondering what images I may have deleted accidentally. Now I just check the selection from end to end before deleting and this seems to work correctly (after deleting the images NX Studio sometimes adds from the selection)
I can't go back to ViewNX-i; well I could, but it has its own issues. NX Studio is more usable to me. I'll figure out ways around the bugs in it and when I have time, I'll try to report them to Nikon.
-
How is NX Studio doing on M1 CPU MacBook Pro(s)? Is it useable if inconvenient?
My Early 2011 MBP froze up and took about 8 to 10 tries to reboot. Usually it can be booted in 3 tries. Once it gave me the dreaded blue screen with vertical black stripes. The logic board is defective. The AMD Radeon HD 6750M display is shot. I read it's a typical problem with these unibody MBP(s).
Any feedback appreciated.
Dave
-
I have just installed version 1.0.1 and still cannot get adjustments to save back to the original NEF files. Am I missing something.
-
I have just installed version 1.0.1 and still cannot get adjustments to save back to the original NEF files. Am I missing something.
Nikon software released since 2014 has not written edits into NEF files, instead, they are stored in sidecar files. To get the edits into image files, you can use export or open with.
-
Nikon software released since 2014 has not written edits into NEF files, instead, they are stored in sidecar files. To get the edits into image files, you can use export or open with.
No, in the settings/options for NX Studio you now have the option to save adjustments to the original file.
-
I have just installed version 1.0.1 and still cannot get adjustments to save back to the original NEF files. Am I missing something.
I also just installed it and I must say I have some cognitive dissonances with respect to my previous work habits :). Same as you, I can't find the possibility to save the edits or save a copy. However, I noticed it saves edits automatically in a NKSC-PARAM folder in the origin folder. Edits are automatically applied when reopening the file :)
-
No, in the settings/options for NX Studio you now have the option to save adjustments to the original file.
I see. After doing so, will third-party software be able to use the edited file? Previously, DXO software was not able to read NEF files edited by Capture NX2. I suspect this move back to storing edits in NEF files may take some raw converters by surprise.
-
I just installed this for testing on my laptop (Surface Pro).
-
Now v. 1.1 is available for download. This includes undo/redo functionality, according to the list of changes:
"Added support for the Z 9.
• NX Studio can now link with NX Tether.
• NX Studio can now be used to enhance pictures downloaded from the camera via Camera Control Pro 2, Wireless Transmitter Utility, or NX Tether.
• The Undo and Redo options in the Edit menu now also apply to image adjustments.
• The default source folder in the export dialog is now that containing the picture currently displayed in NX Studio.
• Context menus in the adjustments palette can now only be displayed by right-clicking tool title bars or the names of the principle tool controls.
• Tools in the adjustment palettes are now identified by an icon in addition to the tool name.
• The info palette now supports display of the items listed below.
- Exposure > Shutter Speed now displays the shutter type.
- Camera Info > Vibration reduction now shows ON (Normal) for pictures taken with vibration reduction enabled and set to normal.
- A number of the existing mode names for Camera Info > AF-area mode have been altered to match those displayed by the camera.
• Addressed an issue in which the “before-and-after” display would not respond to the “update” and “restore original” buttons.
• Fixed an issue that caused NX Studio to crash when opening certain TIFF files.
• Fixed an issue in which the edges of RAW pictures to which vignette control was applied would not display normally when opened in NX Studio.
• Fixed an issue in which crops applied to NEF pictures would not be preserved when the pictures were saved in JPEG format.
• Fixed an issue in which NX Studio would sometimes display different names for custom Picture Controls saved in NCP format."
-
Just a concurring note...Nikon's new "NX Studio" seems to be good, though it does not incorporate the functionality of "Picture Control Utility 2" which I find useful...e.g., the predefined color tints.
I generally prefer moderate-sized laptops coupled with a larger external monitor. However, the acquisition of a larger Windows-based machine (DELL) with a 17-inch UHD monitor has changed my perspective. The 17-inch screen is sufficiently large for photo editing, while the UHD screen improves significantly on the resolution of the stationary monitor, which was a little dated.
Nikon Gear's ongoing dialogue is always engaged...Thanks to All, Robert
-
A note that Nikon released a list of supported applications for Windows 11:
https://www.nikon-image.com/support/whatsnew/2021/0916_01.html (https://www.nikon-image.com/support/whatsnew/2021/0916_01.html)
(may need google translate).
Of course NX studio is on the list of supported applications, but it is disturbing to see Capture NX-D already listed as unsupported. One could worry that Nikon makes a test if the application is supported vs. the system version on install, and if not on the list, blocks it from installing. This happened in the past with Windows 10 vs. Windows 7. (In that case it was the other way around, CNX-D newer versions would not install on an older system, even if I personally confirmed that it could run once installed with a workaround). It would be nice if anyone could confirm that CNX-D will install on Windows 11 (although I have no immediate plan for an upgrade). I do not see NX studio able to replace the functionality yet.
-
A note that Nikon released a list of supported applications for Windows 11:
https://www.nikon-image.com/support/whatsnew/2021/0916_01.html (https://www.nikon-image.com/support/whatsnew/2021/0916_01.html)
(may need google translate).
Of course NX studio is on the list of supported applications, but it is disturbing to see Capture NX-D already listed as unsupported. One could worry that Nikon makes a test if the application is supported vs. the system version on install, and if not on the list, blocks it from installing. This happened in the past with Windows 10 vs. Windows 7. (In that case it was the other way around, CNX-D newer versions would not install on an older system, even if I personally confirmed that it could run once installed with a workaround). It would be nice if anyone could confirm that CNX-D will install on Windows 11 (although I have no immediate plan for an upgrade). I do not see NX studio able to replace the functionality yet.
I guess Nikon don't realize that some of us need the features of the older software and yet in many cases we have to install the latest version of the OS due to security concerns or place of employment's requirements etc.
I am still feeling sour about lack of support for modern OS's in Nikon Scan.
-
Me too - and goodness only knows how many other Coolscan owners that are out there in cyberspace.
...
I am still feeling sour about lack of support for modern OS's in Nikon Scan.
-
Now v. 1.1 is available for download. This includes undo/redo functionality
Finally! I was losing my mind (what's left of it) last night, when I kept losing my edits and/or had to rework images from scratch on write-protected files. (Yeah... I'm an idiot.)
-
Finally! I was losing my mind (what's left of it) last night, when I kept losing my edits and/or had to rework images from scratch on write-protected files. (Yeah... I'm an idiot.)
There is no need to loose all your edits. You can "Save all adjustments" found in the "Adjust" menu. NX Studio will save an *.nka file (as I recall) in the folder you specify (or the last one you used). The same is available in Capture NX-D but the file saved is an *.nxd file. Note that Nikon in their wisdom has offered no way for NX Studio to read the older *.nxd files.
Dave
-
I don't understand what's goign on with NX studio. Sometimes (i.e. at some sessions) I'll do the adjustments as usual, but on export to JPG (Ctrl+E), the original image gets exported. All adjustments are just for naught (crops, straightening, etc.).
That's also a reason for my not posting for a long time, tired to have a session and no results.
-
Apparently, this is a bug corrected in version 1.1, all the more annoying because it was "random".
-
I don't use cropping or straightening in NX Studio, but do use D-Lighting, Picture Control settings, white balance, tone curve and such things, and haven't noticed settings not being followed in exports to TIFF files. I recall in NX-D initially the straighten and crop tools didn't work properly so I haven't tried to use those in NX Studio. I just want Nikon's raw conversion algorithms and use Photoshop or LR to work on the finishing touches to the images (including cropping and straightening). Ironically / sadly, the crop tool in NX2 was one of the nicest in the industry. NX2 never included any empty area in the corners like Photoshop often does. PS can prevent corners being outside of the image when the first time crop/straighten is done, but if making further adjustments, it'll often slip and include white area outside the original image area. It's very annoying. What is wrong with the world when things that are implemented like crap replace things that worked fluidly and perfectly?
It's a good idea to report bugs to Nikon, they will usually correct the reported bugs in a future release of the software.
-
NX Studio has been out almost 11 months now.
I've resisted using it up till now, but after several frustrating weeks, am interested in how the rest of you are finding it?
Specifically
- Performance.
I have a reasonable spec Windows machine with 16Gb ram.
Performance is worse than any previous NX product I've used.
Just doing some simple changes or zooming in/out regularly pushes CPU usage up to 100% - Some features now seem worse.
I'd got used to Active D being a tool I could apply & get reasonable results in previous versions of the NX tools
Now, I rarely get results with it that i want to keep.
I have to resort to Colour control points to manage underexposed areas - I'm struggling with documentation, plus where to find features
- Gaussian Blur?
- Unsharp Mask?
- Being able to selectively copy certain adjustments to use on other images?
etc
As background, the version of Nikon editing s/w I found most usable and gave me consistent results was Capture NX2.
I only moved away from it to be able to process my D500 files.
NX-D seemed worse, but partially usable.
So far, I haven't found anything in NX Studio that I like better than earlier versions :(
How about you?
-
It can give good results, but is too slow, clunky and limited in facilities. It is overpriced.
-
ColinM,
My suggestion is if your camera(s) are supported by Nikon Capture NX-D I'd use NX-D until Nikon NX Studio becomes more mature or you have to due to camera support. From my limited use of NX Studio it will probably be a better organized program in time. Everything is there in NX-S but when it's not familiar it's frustrating. I'm not sure everything works.
So I recommend ignoring NX Studio until it's ready for prime time.
Dave
I'm not using NX-S much because my old MacBook Pro is stuck at High Sierra and I can't install it.
-
I'm surprised you'd find the results any different from previous Nikon software (is this specific to D-lighting)? I use D-Lighting with NX Studio quite often to create quick solution to too high scene contrast without having to resort to laborious masking etc. I also like it that the auto and natural light auto WB settings are available on NX Studio.
I don't do sharpening or cropping in NX Studio; I transfer the image to Photoshop CC and do the late-stage edits there, or in Lightroom. The reason I use NX Studio at all is because of Nikon's algorithms and camera settings are available and sometimes I need them. I recognize that it's not a full image editing software that can be used to do all the steps, and I never expected it to be that. It's a browser and raw converter. None of Nikon's Capture versions was a full image editor in that sense (there were just too many bugs to rely on it for photofinishing and printing for me). NX-D was the only variant which I found unusable; I've happily used Capture NX2 up until 2014 and now NX Studio. The speed of the latest NX Studio software is okay on my computer.
I find that there is something special about Nikon's algorithms which seem more "wholesome" and "balanced" in terms of how the images are rendered. I also think the raw converters in general should pay detailed attention to camera settings so that the user can set a starting point on how the image should look in the camera and this should be the default conversion in post-processing software. Only Nikon software do this.
-
Like Ilkka, I also find NX-Studio quite useful and not too slow on a decently specified machine. Besides, my usual Photo Ninja workflow is at present hampered as it does not support Z9 files. PN can process them, but the outcome is not optimal. Thus NX-Studio comes to the rescue.
What annoys me the most with this software are two things; firstly, how slow it reads files across a local network, and secondly, that the user interface cannot be expanded to multiple monitors /separate windows are not detachable, This makes the UI cramped and hard to read, and even harder to use in a relaxed manner. To be honest PN also shares some of these traits, but as its UI is much simpler the problem is better mitigated.
I would wish Nikon was less eager to make prior Windows versions "obsolete" as seen from the software's point of view. NX-Studio will only run on Windows 10/11 (OK, Macs too I presume but these are of no interest to me). Technically it should run on Windows 7 as well, and a pipe dream is seeing Nikon software run under Linux. Photo Ninja does even though the maker doesn't mention this fact.
-
No speed issues with 45 MP Nefs on a MacBook Pro 8-core 32GB RAM and 1TB SSD ;D
-
I've tried searching and haven't found anything useful. I also asked Nikon USA help and found those responding didn't understand what Nikon's Capture NX-D's *.nxd files are and how they are used so I'm asking here...
Can the latest release of Nikon NX Studio open and apply *.nxd files from Capture NX-D to NEF files.
Are there any utilities from any source that can convert an *.nxd file to an *.nka file?
In the past I found the only bridge between edits applied in Capture NX-D to processing an NEF file in NX Studio to be the *.nksc or side car file.
Thank you for any information regarding applying edits to NEF files done in Capture NX-D to NEF files in NX Studio.
Dave
-
David,
I just tested this on my MBP (late 2020) with both NX-D and NX Studio installed.
As you stated already the bridge btw both applications is the *.nksc file. Changed settings of a NEF in NX-D apply without any issue when you open the same raw file in NX Studio.
Adjustments saved in NX-D as *.nxd can't be opened (gray'd out) in NX Studio (and vice versa for *.nka).
Renaming *.nxd to *.nka makes these files selectable but settings won't be applied (IMHO no surprise).
I am not aware about a utility to convert these files.
-
Thanks Wally,
I was afraid of all this. I could not check when I asked as I don't have a Windows PC available where I am and my MacBook Pro is too old to install NX-Studio. The MacBook Pro I'm using is a 2011 and needs to be replaced badly.
Dave
-
There is no need to loose all your edits. You can "Save all adjustments" found in the "Adjust" menu. NX Studio will save an *.nka file (as I recall) in the folder you specify (or the last one you used). The same is available in Capture NX-D but the file saved is an *.nxd file. Note that Nikon in their wisdom has offered no way for NX Studio to read the older *.nxd files.
Dave
Thank you for that clarification! I'll make note of what you said.
-
There is a new version of NX Studio available (1.20).
Maps feature has been removed. I am not sure why they introduce features then people start using them then they remove the features. I now have to burn my external GPS data into the NEF files in order to be able to see it (and I have to use other software to view it). I was quite happy using Nikon's side car file approach to store the GPS data and view it on the map in NX Studio. Of course that was always limited to that software and so using more sophisticated tools to search for files in a certain area were not available. However, I don't get it why they removed these features, I thought it was quite handy.
Nikon seem to add stuff and remove it on a seemingly random basis. It doesn't help in forming trust in the company.
I guess David's problem of how to move adjustments from NX-D to NX Studio is a similar case. Nikon just don't think anyone would use their software seriously and need to keep the changes over a long period of time.
-
NX Studio version 1.1.2 ;) is the latest,
https://downloadcenter.nikonimglib.com/en/download/sw/215.html (https://downloadcenter.nikonimglib.com/en/download/sw/215.html)
-
NX Studio version 1.1.2 ;) is the latest,
https://downloadcenter.nikonimglib.com/en/download/sw/215.html (https://downloadcenter.nikonimglib.com/en/download/sw/215.html)
I meant 1.2.0, I somehow merged those into 1.20. 1.1.2 is the previous version to the current.
From here you can download either version.
https://downloadcenter.nikonimglib.com/en/products/564/NX_Studio.html
-
There is a new version of NX Studio available (1.20).
Maps feature has been removed. I am not sure why they introduce features then people start using them then they remove the features. I now have to burn my external GPS data into the NEF files in order to be able to see it (and I have to use other software to view it). I was quite happy using Nikon's side car file approach to store the GPS data and view it on the map in NX Studio. Of course that was always limited to that software and so using more sophisticated tools to search for files in a certain area were not available. However, I don't get it why they removed these features, I thought it was quite handy.
Nikon seem to add stuff and remove it on a seemingly random basis. It doesn't help in forming trust in the company.
I guess David's problem of how to move adjustments from NX-D to NX Studio is a similar case. Nikon just don't think anyone would use their software seriously and need to keep the changes over a long period of time.
Bummer, the map feature was just about the only feature I used in Studio so far. It was not only the ability to view the map but also to import GPX log for log matching images to GPS data. I cannot see the log matching featuret any longer - it was accessed under the map menu after selecting the route icon. Perhaps they have problems with compatibility of the interface towards google map, as there was a message in the previous version about a compatibility problem. (The map feature has been there from ViewNX2 on. ViewNX2had problems with finding the correct map server towards the end too). So Nikons simple solution to "fix" this problems is to remove the feature! For now I have reverted to the previous version.
Anyone know of a free utility that will provide the same functionality?
-
Exiftool can match GPX logs and image data. That is the manner in which I geolocate captures from non-GPS enabled cameras like the Sony NEX-5N and Panasonics. Dump the GPX log file into a folder with image files, fire up Exiftool and that's it. You can opt for adding GPS either to jpgs or RAW files (or other formats as long as the file format supports EXIF). If your camera clock is off, Exiftool can correct that on the fly. The matching is perhaps not blazingly fast, but not very slow either.
Google Maps API will not support an IE-based interface from mid '22 onwards. That affects a lot of software out there.
-
Exiftool can match GPX logs and image data. That is the manner in which I geolocate captures from non-GPS enabled cameras like the Sony NEX-5N and Panasonics. Dump the GPX log file into a folder with image files, fire up Exiftool and that's it. You can opt for adding GPS either to jpgs or RAW files (or other formats as long as the file format supports EXIF). If your camera clock is off, Exiftool can correct that on the fly. The matching is perhaps not blazingly fast, but not very slow either.
Google Maps API will not support an IE-based interface from mid '22 onwards. That affects a lot of software out there.
Does this mean that the map feature stops working also if we stick to the old version of NX Studio?
I will try exiftool to embed the GPS data.
-
Yes, as long as the software relies on an interface Google Maps will decline later this year. There are hacks to circumvent this, but likely these will not hold up over a longer time. So the map parts of the programs have to be completely rewritten, which likely will not happen immediately.
Exiftool relies on the correct setting of the camera clock for optimal matching to the GPX log. Start each [day's] session by shooting a watch or similar to see whether there is a difference betrween camera and world time. The difference can be input to Exiftool so it uses the correct time setting. This matters if you are moving around a biut during the shoot.
-
Exiftool can match GPX logs and image data. That is the manner in which I geolocate captures from non-GPS enabled cameras like the Sony NEX-5N and Panasonics. Dump the GPX log file into a folder with image files, fire up Exiftool and that's it. You can opt for adding GPS either to jpgs or RAW files (or other formats as long as the file format supports EXIF). If your camera clock is off, Exiftool can correct that on the fly. The matching is perhaps not blazingly fast, but not very slow either.
Google Maps API will not support an IE-based interface from mid '22 onwards. That affects a lot of software out there.
Thanks, I found the menu in ExiftoolGUI. However when I tested it on D500 nefs (originals to be sure), I am getting error of the kind
Time is too far beyond track in File:Geotime (ValueConvInv) - 2021-08-16-1852N-4063.nef
Warning: No writable tags set from 2021-08-16-1852N-4063.nef
I previously have successfully imported .GPX data to these files with NX Studio (then residing in the nksc files and being output to JPG on conversion) and the location seems correct. The GPX log is sampled at 1 sec intervals, so should have enough time resolution. If I assume that the GPX file contains UTC time stamps and EXIFtool is unaware of the time zone, thus set an offset of -2 hours (daylight savings time in Norway for the folder tested), I am not getting the "Time is too far beyond track..." message, but only the first few files are changed and for the rest I am getting report that nothing is changed and that there are no writable tags for each of the files. The location of the changed files are incorrect, getting the coordinates that were logged at a later time. Apparently something is going on with the interpretation of the time stamps vs. time zones and/or daylight savings time. I might need to do a new test while capturing new files under controlled conditions.
Beyond this, there is still the issue of not being able to see a plot of where multiple image were captured on the map. Currently Irfanview has some buttons to show location on different types of maps, however this is just for a single file.
[Edit: Offset was set with the wrong sign, so daylight savings time in Norway with +2 hours offset gave correct import in ExiftoolGUI.]
-
Exiftool and its documentation cna be quite terse, to put it mildly. However, all the answers are there once you understand the logic. Always best to make a pilot test to learn how things should be set up.
For date/time, UTC zones might need to be taken into account.
-
Yes, and it is not alway obvious what is positive and negative offsets. :)
ExifToolsGUI actually has a GoogleMap tab in addition to the Metadata tab, but it is grayed out and does not respond to anything
-
The ambiguous offsets are a major reason for initiating any series by a picture of your watch ... Compare to the reported EXIF time of a file and you get the offset.
ExifGUI hasn't been updated for years and probably used an older IE-based ActiveX to connect to Google Maps.
-
Regarding manually adding gps exif data-
Not being a fan of Google's data collection in return for use of their services I use a freeware program called Viking. It is available for Windows, Linux, BSD and Mac Os. In Windows if you associate the .gfx filename extension with Viking simply "clicking" on the .gfx file will bring up a point of interest or a route taken in Open Street Map. Link to VIking-
https://sourceforge.net/projects/viking/ (https://sourceforge.net/projects/viking/)
Prior to each session where I wish to use Exiftool I take a photo of an analog clock that has a sweep second hand that is on my computer desktop. Time is consistent as it is updated daily by the timeserver of my choice. I don't know that this method is any better than using a wristwatch, this is simply what I do.
At least on my Windows 10 Enterprise workstation I do not have to take the hours that I'm behind UTC into account (I think that the exiftool "geosync" function must have been changed at some point to read the offset from Windows.) Caution- I don't know when the change was made or if it applies to any other version of Windows or any other operating system. Do note that as Birna pointed out the difference between the time reported by the GPS unit and the camera is important. In my case Windows is compensating for the hours but has no idea what time the camera thinks it is. I do need to add the appropriate offset in minutes and seconds.
For what it's worth even though exiftool remains command line based you can add reasonably accurate (2 to 3 meters ususally) data to a whole folder of your images in under a minute provided that you have a consistent workflow. Batchfiles are also possible if you have used multiple cameras.
For what it's worth I also have written a simple exiftool script for each lens that is typically used on a bellows (or view camera) to add the appropriate but missing exif data to my processed files.
Bob
-
Thanks Bob, looks very useful. File - Acquire - Geotagged images will place thumbnails on the selected map layer. It even had access to the Topo maps that my previously preferred GPS viewer (GPXsee) also provides, but seems a more advanced and GIS oriented. (What I am still missing in relation to NX Studio is the ability to click on a marker to open and edit the image.)
There is no need to use command line with ExifTools for a number of purposes as the ExifToolsGUI provides access to a number of features, if not all, but I could see that it could be very useful with scripting. It is not surprising that I am getting problems with offsets etc. as I move between time zones for much of my vacation, and then typically edit images in a different time zone than where they were captured. (Add to that forgetting to change camera clocks at the first part of a travel and forgetting to set daylight savings time... , but these kind of issues had already been caught when I captured the images I tested above :) ).
There could perhaps also be variations in how the GPS logging app writes the files. I use an open source app on my Android phone suitably named GPS Logger which is quite accurate and suitable for hikes and not dependent on any external service other than the satellites. (There are a couple of others with the same name - this one has a red field at the top of the screen that identifies it. ) I notice I had a setting to show GPS time in local time zone turned on, but I am not sure if that also affected the written log. I also see options for which version of GPX standard to use, I used 1.0.
-
I prefer using a wrapper around Exiftool instead of the brute-force command line approach. Just a matter of convenience as I need other EXIF data points to be read or updated anyway when the images are entering the database.
Viking is slow and not very stable when I tested it on a Windows 10 box. A pity, since I'm currently a a true -- literally -- 'Viking', being a citizen of the Viken county (until end of next year at least). By rules of standard Norwegian grammar, a member of Viken is a viking :). Viken however will be split into separate counties in the near future, if the politicians don't go against demands of the public majority (again). Hope not as Viken is not a natural region of Norway.
I'll download it on a Linux system instead to see whether the software fares better there.
-
I use Windows out of sheer commercial necessity (sigh,) and the enterprise version because it (alone in many instances) allows the removal or disabling of many, many "features" in W10. If or how my modifications to W10 Ent. affect the performance of Viking is something that I'm not prepared to speculate on.
I do use ExifToolGUI; it's more than adequate for many of my needs but in some cases use the command interface because it's more efficient.
As I reside in a rural area where cell phone service is, at very best poor, and often frequent areas where three is simply no signal available, the use of Android or iOS apps is not something that I've considered.
I had a short, but by no means exhaustive look this morning at some of the wrappers for ExifTool. A couple look as if they may be worth trying. Given the fate of Centos(7) where my database currently is, I'll be moving on, perhaps to Debian, in the near future.
-
An annoying change is that when using Open With in v. 1.20.0, the created TIFF file always goes to the directory set in Options / Destination for Files Opened in Other Applications, which then has to be set every time manually to the directory where the original file is, if I want to keep them in the same directory. What's more, it copies the NEF into a second file if the settings are not used (so I can get to ACR I need to choose this option; otherwise it will do the Nikon conversion and open that TIFF in PS). This will be a royal pain to put up with.
-
Sounds like Nikon have fully embraced the Microsoft way of thinking: all users are created equal, have the same wishes and requirements, and don't worry, we know what these are. Windows is getting more tiresome for each new "evolution".
-
So sadly true.
No longer do the evolutions arive in the acceptable/unacceptable/acceptable.... sequences of old such as 2000/Me/XP/Vista/Win7....
...................................................
Windows is getting more tiresome for each new "evolution".
-
problem solved
-
problem solved
Now that statement does not solve or clarify anything?
-
The error message for map view in NX Studio 1.1 clearly shows why the feature has been removed from v.1.2. Nikon evidently uses the ActiveX technology of IE and this will no longer be supported by Google Map API from June, 2022.
As the problem is on the program side not with the Map API as such, it ought to be solvable in future versions of Studio.
However, true to the concept of declining backwards compatibility, NX Studio 1.1 now no longer is willing to read my Z9 NEFs after the Z9 has been updated to firmware v.2.0. Oh Brave New World. Indeed.
-
Now that statement does not solve or clarify anything?
Sorry Birna, I had posted an issue I was having in NX Studio not being able to ready my latest files from the Z9 after I had updated the firmware to 2.0 on the camera. I downloaded what I thought was the latest version of NX Studio 1.1.2 and it was not working for me. To my surprised I check the Nikon download site again and noticed the NX Studio version 1.2, and after downloading that version, I was able to work with the Z9 raw files again. I attempted to erase my previous post without success so I simply updated it as "problem solved". My bad. The problem solved statement is not related to the issue you mentioned with the map view.
-
OK, understand now.
Evidently I'm not the only one finding NX Studio not working with Z9 NEFs after the firmware upgrade to 2.0. The "solution" is updating (not upgrading) NX Studio so as to lose features there. A classic between rock and a hard place scenario.
-
quick bump: when rating pictures i use keyboard from 1 to 5 to set a star rating. for reject i am suppose to use - (minus) key. The thing is that when i press it, nothing happens. Am I missing something?
Thanks!
-
quick bump: when rating pictures i use keyboard from 1 to 5 to set a star rating. for reject i am suppose to use - (minus) key. The thing is that when i press it, nothing happens. Am I missing something?
Thanks!
Pressing a number key has always set the color label, not the star rating (0 removes color label). Ctl+number sets star rating, (Ctrl+0 removes it). Minus does not appear to do anything.
However the strange thing is that when I first tested pressing a number key now, the very first times it set the star rating, but then after some fumbling it consistently behaves as my above comment as is also the case in ViewNX2 and Capture NX-D. Seems to have been a glitch, unless I hit a hidden switch by accident that I am not aware of. For the record this is running under Win 10.
-
Heads-up about update:
https://downloadcenter.nikonimglib.com/en/download/sw/234.html
-
The software by default saves the setting in a sidecar file. You can turn it off by going into Edit > Options (Ctrl+K). Select "Save" from the Menu within Option box and select "Save adjustments, labels, ratings to the original image file".
This has improved my overall RAW editing process. Lightroom is faster but doesn't replicate the look I can see in the camera, hence I have been using the native software for my editing.