Thanks Mike.

I just went thru unclogging my Epson 4800 using Epson driver routine  - it is a process that always stresses me out as I listen to all the whirring and clunking in the printer thinking of all that $/ink going into the waste tank, and not knowing if that last unclog routine will be the final one or not.

My Qimage upgrades ran out at .240 - having an automated 'keep printer flowing' routine is enough to convince me to re-new upgrades for a year!

I have Qimage set up now with same page size, same driver settings, profile, etc.

Manually copying settings that are in print driver is what I had to do.

I have copied the job history files over and can see them, but don't have the time to update them.

This is a great Qimage feature, but I have not tried it.

Keeping that in mind...
Does this only run on 8.5x11" ?
The added feature to run on an set interval is great, to keep printer unclogged.  I wonder if that could be done with a less ink - that is just exercise the nozzle, but not as much ink as is used for unclog routine.

I fresh installed Win 7-64 on a new SDD along with Epson 4800 Win7 drivers and have Qimage up and running recognizing printer.
My XP system in still on old HDD and if needed can boot up and/or copy files from it to new SDD.
All my data files (images, etc.) are on third HDD.

My question is what files from my prior XP Qimage install can I transfer over to get my print history, printer driver settings, cut outs, etc and what needs to be done manually (print driver settings perhaps)
Anything that is auto generated (thumbs) I don't want to transfer but anything that is custom settings that affect print job or print job history I do.
Thanks.

I found this which probably answers my Q's:  http://ddisoftware.com/tech/qimage-ultimate/migrate-qi-stuidio-jobs-list-to-qu/

If you change the in camera jpeg processing contrast setting (picture style) you can change that.  Set it to low (0) and it will be much closer to flashing only when the RAW is overexposed.  This is applicable even if you are not savings images as jpeg in camera.

Mike-

As you explained Qimage/DCRAW is not simply transferring exif data as it should, but in the case of the 30D, modifying the model name. That is the root of the problem.  Modifying the model name is not standard practice and is also not self consistent with how Qimage/DCRAW is handling the model name for other Canon cameras, where 'Canon' is not removed from the model name in exif.

For the exif 'date/time original' field, this is not a maker tag, it is a standard exif tag (see the .txt previously attached).  It is also a basic field that holds a very essential piece of data, that is when the image was taken.  Every other software I've used recognizes this field and is able to transfer it when converting files.  Qimage features list claims: "EXIF data carried through to converted images", but apparently this is only for a sub-set of basic fields.

I understand if you choose not to consider this further, but disappointing as there is opportunity here to make Qimage stronger in regards to exif handling.

HI Mike, thanks for checking in on this.
I have attached a .txt file which is a cut/paste from the exif data reported by Irfanview from the original CR2 file as well as the CR2 Qimage converted to .tif.  I saw same results in using several other exif viewers.  This comparison best shows the differences, with explanation below.

In regard to the exif Model name: I also get the same result you show using Qimage Image Info ("Cntl-I) where the 'model' is reported as "EOS 30D" for both the CR2 and the converted TIFF.

However using other exif readers and/raw converters (including: Canon DPP, Irfanview, Fastone, Adobe, Phase One CO) the exif 'model' name is reported and transferred to converted output as "Canon EOS 30D" (note they all, like Qimage also report the 'make' name as 'Canon' in the 'make' field)

Interestingly I've also found that Qimage produces a matched result to these other readers/converters for the 'Canon PowerShot s45' and 'Canon Powershot s90' and 'Canon EOS 5D', so the Qimage difference only seems to be for the 30D of the models I've checked.

It may seem minor and it is, but it does produce a sorting discrepancy when managing many thousands of images and it also affects automated processing (primarily lens correction) that is based on correctly matching the 'model name' field.

Anyway it is curious why Qimage is reading a different value for the model name field than is reported most elsewhere.
---------------------------------------------------------------------------------------

For the date stamp issue: Again the result you show I get the same as well.

As I have best determined using a variety of exif viewers, When converting a RAW, Qimage records the original date in the exif/camera field 'date modified' (aka date/time, tagID 0x0132) it does not save it to any other exif field or transfer other exif date fields.

Here is where there is interesting Qimage function:
When Image Info (Ctrl-I) is used it first reads and reports the exif/camera, 'date modified'.  But, if there is a date recorded in the exif/image, 'date taken' (aka 'date/time original' TagID 0x9003) field it will supersede reporting the exif 'date modified'
(This process can actually occasionally be seen when pressing Cntrl-I on a image that has not been previously read the 'date modified' will first pop up, but in a flash be replaced by the exif 'date shot' if it is recorded in exif.)

So in the example you provided Qimage is writing 'date modified' and reading it back correctly as expected.

However it is the Qimage function of only saving the original date in the 'date modified' field causes problems as other downstream image software will by design update the 'date modified' date when resaving, but not the 'date/time original' (TagID 0x9003) field.
As Qimage does not also transfer and record the 'date/time original' field then that original date when image was taken is lost.

It could be suggested that the issue is not with Qimage, but the other software that changes the 'modified date', however that date by intent/design should be updated whenever image is modified and it is the 'date/time original' field that remains unchanged.
Qimage should ideally not only write the 'date modified' field as it does today, but also write/transfer the exif fields for 'date shot' - this is standard function for other other RAW converters I've used. (I understand Qimage is not primarily intended as a RAW converter)

In general there are several other standard non manufacturer specific exif fields in the CR2 file that are not transferred to converted images. It would be a nice improvement if Qimage exif handling was more thorough.

As a separate, but related note/request in the thumbnail view when sorting by date Qimage sorts by the (non-exif) file modified date, it doesn't use exif dates.  It already appears Qimage can read the image 'date/time original' field, being able to sort by it (and perhaps other exif fields) would be a tremendous help.  

This is a reference to exif fields and associated Tag ID's:  http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html

Thanks for you help and consideration

I have found the details on what is causing me organization and automation problems:
1. The exif model name is saved by Qimage as "30D EOS" when for several other Canon cameras I checked Qimage uses the naming convention (which is also used by several other RAW converters and Canon) of "Canon 30D EOS".
2. Qimage is saving the original date using the exif 'date modified' field.  This field does not by definition always match the 'image date taken' and/or 'image date digitized' exif fields so it can not reliably be used as the date taken.  It would be very helpful if Qimage also saved the date taken in the exif image date taken field.

I have started to explore using Qimage (2014.115) to convert my Canon 30D RAW images to tiff.  I use the convert function available when images are in queue.  I have not done a careful check but it is apparent that much exif data is not written into the .tiff.  Notably what is missing is the date shot field.  I also noticed that the camera model field is not the standard "Canon 30D EOS" but instead "30D EOS".  I can followup later with more specifics, but wanted to know if perhaps I was missing a setting for what is an important capability.

I am also disappointed I don't have the opportunity to upgrade from Pro to Studio anymore.  I did receive emails from DDI offering $40 upgrade, but nothing that said it was limited. I also got the ultimate announcement on 7/24, so not sure if spam filters were the issue.
Anyway the only reasons I wanted it was for ruler and using quad processing.  I don't use RAW.
I was at the few months before Ultimate announcement reviewing threads about the benefits of Studio and talking w/my wife about spending the $40.  Then it just went away when I was on the verge of upgrading.  $90 is over budget for me today - I am not upgrading any SW in the near term, just saving for ink which I have to watch carefully.
Anyway I respect Mike's business and appreciate the support over the years.  Maybe someday I will be able to justify and spend to upgrade to Ultimate (in line lens correction including fish-eye correction would be a selling point for me!) , but until then I will just use what I have.

I think it is pretty clear that you will still get free upgrades and support for LPS.  They just won't be for added new capabilities other than new camera support.  As always bug fixes will be provided as well.

Terry,  I use Capture One for RAW and have for years, so I have a very long back catalog of images that are ready to print.  I also do lens correction  (PTlens) on 50% of them, which I don't see possible in Qimage.
So it will be Studio for me.  Can't justify the higher cost of Ulitmate.

Well, reading this and the discussion on dpreview has inspired me to finally upgrade from Pro to Studio QI.  I had been wanting to the past few months, but holding out as I don't do RAW - just wanted the better interpolation and faster processing w/quad core.  I can see now I won't be interested in the new features of Ultimate and want Studio as it will be seamless transition from Pro.  So I'll put in my $30 support as an upgrade.

Well to be fair Qimage is (in my exposure) not primarily marketed as an image up-sizing software like these other ones are - The Qimage catch phrases include 'Professional Batch Image Printing Software" with feature notes about 'optimization resolution for printers and the print' (only a side-bar talks about interpolation)  While the engine is the best out there the core (or perhaps the roots) of the product is about ease of printing, layouts, multiple images on pages, batching, matching output resolution to printer, accurate color...

Thank you!

I have a potential issue or more likely confusion

When I use the menu Help.... Analyze Current Settings, I get the message (to paraphrase): "You are using a monitor gamma other than 1.0...  You should be using monitor icc profile... to change go to Actions... Slideshow... and change."

But I am using a monitor profile.  In color management set up it shows that my windows monitor profile matches the setting I have for Qimage (yellow = selected olive color) and it is checked as being used.

Not only that when I do start a slideshow I see nowhere to change gamma if I wanted to.

I recall using this 'Analyze settings" before and not seeing that gamma 1.0 message.

Thanks
Alex