Nikon Capture - where's the rage?

Running XP 2.4 gig chip with 1 gig memory I dont use noise reduction often. Love the shadow inhancement part. It saves kinda slow sometimes. Batches well,, far better than PS 5.5. In fact I often use PS for titleling and cropping and cloning only. Yes the tool boxes are larger than they need to be.
--
Im having too much fun with my D 100 to worry about what camera comes next
 
I certainly find NC 4.4 to be quite good.

The NEF plug in for PS CS2 is SO SLOW as to be unusable, going back to ACR yields a conversion I'd call mediocre at best, tried Bibble Pro and it has awful artifacting, Capture 1 is OK, Lightroom is fast and I like it best so far, but NC 4.4 is OK in my book and yields the best RAW conversions from the D200 so far.
--
Cheers,
Joe
 
I spent a few hours on the phone with Nikon unable to load Capture on my G5, apparently has issues with Macs, previously used it on my G4, insanely slow, Capture may be OK with PCs but its not happening with Mac.
 
NC works for me very well. It is not at all dismal for me. I do almost all my post process in NC and only when I have a special need for processing part of my image, do I launch PS from NC.

--
Speed is significant and interesting but accuracy is downright fascinating
http://www.pbase.com/pradipta
 
I don't really see what the hubbub is...I just opened a D200 compressed .NEF using Windows explorer (edit with Nikon Capture) 10MB in size in size in six seconds. Seems fast enough for me. Ever since I got the D200, I don't have to fiddle around with the .NEF as much as I had to do with the D70 so I have been using Nikon View more.

I just wish that CS2 can save in .NEF.

--
Cliff
 
I don't really see what the hubbub is...I just opened a D200
compressed .NEF using Windows explorer (edit with Nikon Capture)
10MB in size in size in six seconds. Seems fast enough for me.
Ever since I got the D200, I don't have to fiddle around with the
.NEF as much as I had to do with the D70 so I have been using Nikon
View more.

I just wish that CS2 can save in .NEF.
I opened a multi-image session.
Clicked on an image.
It only took 13 seconds to open.
Just 13 seconds.

Just did the same in Bibble.
It took 0 seconds.
That's right. The second I clicked on it, it appeared for editing.

Hmmm, that makes it 13X faster? No, not really, that would be if it only took 1 second to open in bibble.

I think in mathematics 13 is infinitely greater than 0.

You get my thinking.

I processed 430 images in Bibble last Saturday afternoon.
That's ==93 minutes less== in Bibble than in Capture.

And that doesn't count the time you wait to view each change.
That's where bibble falls down just a little bit.
It takes about a second to see a really big change.
One that takes oh, 5-10 seconds in Capture.

So if you add all of my hand-changes to the 430 pictures...
Well, I would say that Bibble was 3-4 hours faster than Capture.

But you're right, no big deal... if you have the patience and the time. :-)
--
AAK - http://www.aakatz.com
 
I'm not sure what the AMD 64 bit processor is going to contribute to NC which is a 32 bit program. I've tried capture with a 3GHz Intel HT and it running 2GB of CAS2 RAM (OZ) and it seems to run great. As I mentioned in another post, I went from Windows Explorer to full stabilized image using NC 4.4 in 6 seconds. I have done retouching of the image and it didn't seem sluggish to me. CS2 seems far more sluggish than NC 4.4.

As far as stability goes, I have IE crash much more than NC 4.4.

--
Cliff
 
-- Are people just shooting JPGs and living with it?
Okay, so if I get this right, no matter how good NC can convert RAW files, you dislike it because it's slow. This means you don't have time for good images. So why don't you use Jpegs? I mean, isn't this all what's your post about?

I use the best there is (IMHO) and I don't care how fast or slow it Batches while I sleep...
 
some folks have such a hard time with Capture. I don't have anything fancy, just 3.0 PIV and 1 GB RAM, but Capture has always worked great for me. I would be totally bummed if I couldn't use it to do the initial adjustments to all of my NEF's. Most of the time I use it for exposure adjustments, if needed, and a little bit of initial UnSharp Mask. I will also use it as a quick color balance for the shadows using curves.

I find the little bit of UnSharp Mask in Capture makes a better foundation for CS2 UnSharp as opposed to using CS2 for the entire sharpening. I've tried every iteration of Photoshop RAW conversion and so far feel they all soften the image a bit plus I can't save the adjusted NEF.

I do think the new Shadow/Highlight tool in Capture 4.4 was a step backwards and have all but stopped using it in favor of the CS2 tool.

The only thing I can figure is folks may have their cache set up wrong or have something conflicting or hungry running in the background. I usually have CS2, Capture and NikonView running all at the same time. I only open one or two images at the same time, but I've never actually wanted more than that cluttering up my desktops.

I guess I would recommend folks put cache for Capture and CS2 on a seperate drive and partition. I have my cache set up on my backup drive and on a seperate partition. Seems to work fine.

Bests,

Howard
 
nc is slow

mostly because it uses plenty of resources. D-lighting and Noise Red. add to the problem.
results are perfect, no problem with that.

But in the end: it is slow and imho nikon should do something about that, quickly, because nefs are getting bigger.

wim
 
sheesh, loved nikon capture and lived with the slow, clunky performance. Then I got CS2! just bridge alone is worth the $250 compared to capture and view.
 
So much energy is being expended here on worrying about easily
corrected (or maybe imaginary) D200 problems like back focus
(hardware), banding (firmware), etc. But I am frankly surprised at
how little vitriol is saved for Nikon's absolutely dismal
post-processing software. Where's the rage about that?
works fine for me, gives the best raw conversion I've seen. Maybe rage isnt needed. You may not like it, but many folks I know do use it and like it.
-- Are people just shooting JPGs and living with it?

-- Or are they resigned (as I am) to using third-party batch
software to make up for Nikon's poor programming, slow operation,
and impractical controls?

I am a little surprised that people keep clamoring for a
full-frame, 23mp sensor when Nikon can't seem to master the
programming for efficiently processing 12-16mb NEF files (maybe
they should hire some of the software engineers who did Kodak's
software?).

And I never thought that Photoshop was a particularly efficient
vehicle for raw conversion until I spent a lot of 'quality' time
with Nikon Capture. Lightroom is a step ahead, except for its
oddball interface (clearly Adobe never had two screens in mind when
it designed the "main window" concept).

Thoughts?
--
Harris

PBase/DPReview/NTF supporter
Egret Stalker #4, WSSA #29

http://www.pbase.com/backdoctor
 
Nikon Capture is not slow. On my PC it runs just as fast as CS2. NC speed is due to the PC hardware configuration. I'm running a 3 year old Athlon XP processor, with 1.5 mb of Mushkin ram and WD Raptor 75 gig HD for programs & Matrox video card. Get the new 150 gb WD Raptor if you want speed, runs at 10,000rpm's and is quiet.
 
Like alot of other folks I simply gave up on the product. It's abysmal speed wise for even processing the smaller NEF's from my D70 and D100. I can't imagine what kind of supercomputers people run to make it tolerable with D200 or D2X NEF's. Even if it were as fast as the third party offerings it would still be buggy and have the poorest interface of any of the serious offerings.

I know some people believe that Nikon actually reads these forums. I doubt it but on the off chance they do, I'll say that if it weren't for the third party software offerings I would abandon Nikon all together over this one issue. I'm that dissappointed in what they offer with NC.
--

Fit for release from a mental institution but banned from the 3-0-0-D forum since 6-2005.
 

Keyboard shortcuts

Back
Top