Mike Chaney's Tech Corner

 
I’m trying to do something I’ve done loads of times.
6 nef photos with filters applied
Put all in queue
Click convert, click Tiff button, new output folder accepted
Click OK, at the bottom it says 1/6 and Processing followed by file name.
After a few seconds I get the error message: Range check error.
If I click the error message OK, it goes away but I can do nothing.
I’ve retried the sequence.  Closed QU and started again but each time the same thing happens.
Any ideas what’s happening?

Just so I can try to repeat the error message, can you supply some more details?
For example, Is auto crop on?
Do you have a check in Honor Print Crops and Stamps?
Have you cropped the images?
Are there both raw filters and editor filters applied?  (qrs and flt)

Have you tried other Nefs?
Can you repeat the error message with 4 images instead of 6?

Anything strange in the filters?  Meaning, anything you made and saved as a filter for future use?

Anything you can think of?

Is the folder for the images very far down with many sub folders?

Fred

Thanks Fred,
Not sure what you mean by Auto crop, the crop box is ticked in the edit screen and looks OK
Honor print crops not ticked, but get same error when it is.
Some images are cropped, only flt filters
Error with 4 or even 1 image, Tiff or jpg
Filter not saved originally, but I’ve just saved a filter – same error.
Folder not far down but I’ve tried saving to desktop, same error.

Lurcherjohn.

Found Auto crop scissors, (I forgot they were on the Print properties box) but same error if button up or down.

and the last question, does it happen with other nefs?
Will it happen with 6 copies of the same NEF; trying at least two different ones?

Obviously, I cannot repeat the error as yet.
Have you tried rebooting the computer for a fresh start in case something is interfering?
Also, I have seen Anti virus software actually shred files that are being created in order to check for contamination.
If you have such a drastic security system running, see if that can be disabled.
Fred

Doesn't work with other nefs, works converting tiffs to jpgs.
I've rebooted a couple of times  - same error.
I'll play with anti virus and see what happens.

Some progress Fred.
I took a couple of photos and copied and pasted them from card reader to the desktop.
Converting them worked fine. Tiffs in a new folder no error message.
I then downloaded the same photos with QU flashcard copy and camera profile as usual.
Tried to convert them and it worked with no problem!
A mixed batch of well behaved nefs and baddies failed but when I took the baddies out of the queue it was fine.
So it seems to be a camera setting and if I go back a couple of days it's OK so Im going to look at the exif info on goodies and baddies to see if I can spot the difference. Wish me luck, I'll report back if I find anything.

Super!!
Sometimes, it helps just to kick it back and forth!

Fred

Haven't spotted anything in the EXIF info but don't know what to  look for regarding 'Range check error'.
Irfanview batch conversion worked with no problem so it's a difference between Irfanview and QU as well.
Photoshop Elements and Paintshop Pro can also open these NEF files and save as TIFFS.
What are Irfan, PSE and PSP doing that QU can not do?
AND if I use the QU Flashcard/Copy method I can batch convert those same NEFS to TIFFS with no problem.
So it's the QU Convert Images method that doesn't like those files, of course that's what I'd prefer to do so I can use the filters.

If anyone wants to try this here is a link to my page with a couple of the NEF files with their flt files:
http://www.lurcherjohn.com/Filenefs.html
   Lurcherjohn


 

I opened the images in Qimage, and I see you did not use REFINE at all, so there's no qrs filter.
I did look using INFO in Qimage at the exif, and the ISO is all  messed up.  See attached snap
That's probably the best clue.
We will have to ask Mike.... but everything else works fine on the images, just the Create Image.
Qimage is probably checking the header for something....
Fred

PS Were these 2 NEFs run through another program before you opened it in Qimage? How do the other NEF ISO look?

John,
I think I spotted another clue.
I told Qimage to create JPGs instead  of TIFs.
It managed to make one JPG before it crapped out withe Range Check Error.
When I look at that header, the ISO that Qimage was trying to copy from the original NEF you sent, is missing altogether.
So the problem has to be  the fact that Qimage is copying header information from Raw to destination, and finding something non standard, Stops.

That's my guess.

No, I loaded the nefs from my camera using QU Flash card copy/move then edited and filtered all in QU.
Yes I found one jpg too but assumed I had got confused! Glad you found one or perhaps we're equally confused? Hope Mike can sort it out. Cold you get Flashcard copy/move to convert them to Tiffs?

John,

I looked at the NEF's and discovered that the EXIF info is corrupted.  I suspect these particular NEF's were opened and resaved in some Nikon software, right?  You said the ones you loaded straight from the flash card to QU were fine.  A lot of times when you open/save raw files from other software, they get altered so they are unreadable by third party tools.  dcraw is designed to work with the "real" raw files: unaltered.  As soon as you open them (whether you modify them or not) and resave the NEF via other software, the format of the NEF is changed.  Then the third party software can't decipher the headers.  Might be what happened here.

In any case, the ISO was showing as -1.  That's what caused the problem.  I'll fix it in the next release so it just defaults to ISO 100 if it sees an invalid ISO.

Regards,
Mike

Thanks for the explanation about the ISO corruption.
The nefs on my website have low index numbers because they were downloaded via NKremote but I have others directly from camera to QU Flashcard but renamed on downloading that give the same error. The ones I took today to test were OK so whatever was going on seems to have stopped. I'll leave things as they are and try again with the next release.
  Regards, John

They work fine with the new release.
Thanks Mike, much appreciated.