and please use their services
Nikon Capture NX2
- Thread starter Monkey
- Start date
joxby
Suspended / Banned
- Messages
- 8,782
- Name
- John
- Edit My Images
- No
Well, I don't know
The main issue for me is speeeeeeed, I tried it, it took yonks to open an image, sucked 500mb of ram in doing so, thats as far as I went with it, it didn't get over the first hedge.
It is technically superior to NX, but I didn't try the new knobs and whistles....no point, lifes too short.
The main issue for me is speeeeeeed, I tried it, it took yonks to open an image, sucked 500mb of ram in doing so, thats as far as I went with it, it didn't get over the first hedge.
It is technically superior to NX, but I didn't try the new knobs and whistles....no point, lifes too short.
Love it! Works very well on my aging P4 2.8GHz 1.5GB RAM system. I've always used Paint Shop Pro to finish my photos - tidying up, final resize and sharpening, but sometimes I can do it all in CNX2 now.
It's not terrifically fast and I'll probably notice a difference when I upgrade from D50 to D300, but if I win the lottery I'll buy a faster PC as well
It's not terrifically fast and I'll probably notice a difference when I upgrade from D50 to D300, but if I win the lottery I'll buy a faster PC as well
joxby
Suspended / Banned
- Messages
- 8,782
- Name
- John
- Edit My Images
- No
It's not terrifically fast and I'll probably notice a difference when I upgrade from D50 to D300, but if I win the lottery I'll buy a faster PC as well
You will, it was usable with d70 raw's, 5-6mb files, but d200 files are 15mb without exception, I can't be arsed using it for d200 files.
d300 file can only be bigger...
*crosses fingers for ya* in hope, not expectation.
Gandhi
Suspended / Banned
- Messages
- 4,666
- Edit My Images
- Yes
I found it was much better/faster than V1.
Until I started opening d300 files with 14bit raw and ADL turned on.
P4 2.8 & 2gig of Ram though, so not a swift system.
Although NX2 isn't multithreaded, .Net is, apparently. I'm hoping when I finally upgrade next month to a quad-core & 4Gb and some decent hard-drives it'll pick back up to a usable level.
The reason it's a lot slower than CS3 is because NIKON ARE STUPID!!!!!!!
The image quality from it is head and shoulders above the god-awful CS3 raw engine. If they could sort out the speed issues then they'd be onto a real winner imho
Until I started opening d300 files with 14bit raw and ADL turned on.
P4 2.8 & 2gig of Ram though, so not a swift system.
Although NX2 isn't multithreaded, .Net is, apparently. I'm hoping when I finally upgrade next month to a quad-core & 4Gb and some decent hard-drives it'll pick back up to a usable level.
The reason it's a lot slower than CS3 is because NIKON ARE STUPID!!!!!!!
The image quality from it is head and shoulders above the god-awful CS3 raw engine. If they could sort out the speed issues then they'd be onto a real winner imho
Slapo
Suspended / Banned
- Messages
- 2,622
- Name
- Peter
- Edit My Images
- Yes
My experience with .NET is kind of limited to only one project so far, but from what I've learned, .NET isn't multithreaded unless you initiate the threads.
There can be exceptions to that, of course, but code that's not in the framework has to work that way, it seems.
Nikon nor its programmers don't have to be stupid because their app is slower than CS3.
You've said it yourself, Gandhi, that its output is head and shoulders above that of CS3's raw plug-in. Perhaps the slowness is part of the price you have to pay for better quality.
Algorithms yielding better quality results tend to be slower than the 'ugly' ones.
I'm happy with ViewNX/RawTherapee + the GIMP. It's not the fastest solution out there, but it's acceptable and faster than Capture NX 1 was for me.
There can be exceptions to that, of course, but code that's not in the framework has to work that way, it seems.
Nikon nor its programmers don't have to be stupid because their app is slower than CS3.
You've said it yourself, Gandhi, that its output is head and shoulders above that of CS3's raw plug-in. Perhaps the slowness is part of the price you have to pay for better quality.
Algorithms yielding better quality results tend to be slower than the 'ugly' ones.
I'm happy with ViewNX/RawTherapee + the GIMP. It's not the fastest solution out there, but it's acceptable and faster than Capture NX 1 was for me.
joxby
Suspended / Banned
- Messages
- 8,782
- Name
- John
- Edit My Images
- No
You're absolutely right, I'm actually gutted I can't use it, it is the best stand alone photo only app on every level, except the most ridiculous pc spec requirement, to run it successfully.
I mean...are they stupid or what, I was reading somewhere on another forum that even a quad core doesn't bring it up to a comparable level with similar apps run on basic machines.
I haven't heard a reliable, independent, "what the bottom line is" yet short of 2 grands worth of overclocked nitrogen cooled Global Digital Defence Network equipment...
Keep us posted, I'd like to know how it runs on a quad from someone who doesn't have to say it runs like s***offashovel.
"Skynet became self-aware at 2:14am EDT August 29, 1997,"
Slapo
Suspended / Banned
- Messages
- 2,622
- Name
- Peter
- Edit My Images
- Yes
Well, not every algorithm can be rewritten to be multithreaded. In that case, performance per core has the greatest impact, usually.
Btw., Gandhi, if I might ask a favour of you. Could you try out RawTherapee 2.4m1 now and then later on the quad core and see whether there is any difference in performance with both the EAHD and HPHD algorithms (can be changed in program settings)? When saving files and rendering previews (there's a small check box for that).
Thanks
Btw., Gandhi, if I might ask a favour of you. Could you try out RawTherapee 2.4m1 now and then later on the quad core and see whether there is any difference in performance with both the EAHD and HPHD algorithms (can be changed in program settings)? When saving files and rendering previews (there's a small check box for that).
Thanks