Mike Chaney's Tech Corner
December 26, 2024, 04:27:53 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Qimage registration expired? New lifetime licenses are only $59.99!
 
   Home   Help Login Register  
Pages: 1 [2] 3
  Print  
Author Topic: Canon imagePROGRAF PRO-1000 red/pink tint  (Read 26948 times)
Fred A
Forum Superhero
*****
Posts: 5644



WWW Email
« Reply #15 on: January 11, 2018, 05:49:18 PM »

Quote
I just did another (and my final) test print. First Qimage, then LR. The Qimage print came out identical to the LR print. The only thing I changed was reselecting the Pro 1000 from the Printer/Media panel in Qimage and check that everything was set correctly. Whereas yesterday, with the exact same settings, the Qimage output was bad.
You reselected the printer from the list in Qimage and that fixed it? That tells me one was the XPS Driver and the other was plain 1000.
Good Luck
Logged
damonlynch
Newbie
*
Posts: 8


Email
« Reply #16 on: January 11, 2018, 06:07:04 PM »

Your conclusion is that this problem is caused by user error, i.e. me choosing the incorrect settings in the configuration.

As I pointed out in my initial post, I had no problems printing with Qimage until recently. 

I have also pointed out that even with the exact same print settings, switching between Lightroom and Qimage, only Qimage has produced incorrect results. I have also pointed out that it does this inconsistently, i.e. not every time. But it surely does it, on multiple prints at multiple sizes across different driver versions and media configurations.

Does this level of diagnosis sound like someone who cannot tell the difference between selecting an XPS and non-XPS driver?

Logged
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« Reply #17 on: January 11, 2018, 06:07:51 PM »

What I'm suggesting is that Qimage alert the user when the printer driver that is installed on the system has been updated since Qimage was last run. Do a version check at start up, and if the version changed alert the user to re-setup their save print templates. To me that seems a better solution than expecting the user to have seen a bullet point on a discussion forum posting from 2011.

Qimage already does that: has for years.  Whenever it recalls settings, it compares the version number in the saved settings to the version number of the driver.  If they don't match, you get the attached warning.

The problem is, most manufacturers don't bother (or forget) to update the dmDriverVersion element in the DevMode area of the driver, so even when the driver is updated, it carries the same Windows-reported version number as the previous driver.

Nothing I can do about that, other than do what other software does: don't even allow the capability to save/restore driver settings!  If you don't offer the feature, you can't have a problem with it.

Edit: I should also mention that I've identified some significant bugs in the last three Windows 10 updates related to printer driver operation.  The one that I reported to MS was for a Pro-2000 driver but I know it affects other drivers as well.  It is not limited to Qimage (not even Word prints properly) as the problem is at the OS level.  But it's easier to notice in Qimage because Qimage comminucates with the driver in more detail than many programs.  Last I heard back from MS, they were aware of the problem and said their target for fixing it was by the end of January.

Mike
« Last Edit: January 11, 2018, 06:19:54 PM by admin » Logged
loganross
Newbie
*
Posts: 43


« Reply #18 on: February 14, 2018, 05:05:11 AM »

Hi Guys,

New user with the Canon Pro 1000.  I am getting the pink alien skin problem with Qimage.  The issue seems to be random.  Out of twenty tries, including for Canon and Ilford papers (using the correct paper manufacturer profiles), only one print did not have the problem.  The color was off on that print anyway. No problems printing via PS, ImagePrint 10, or via the Canon Print Studio Pro plug-in (including using the same profiles).

The image looks fine in qimage itself.  Fortunately, Qimage lets me preview, so I see the problem before it actually prints...I learned that after the first problem print.   I am trying to use the XPS driver (which I select for 16-bit printing path).  However, the failure has occurred with the regular driver as well.  I have tried it all, including triple checking the settings, rebooting my PC, and changing the rendering intent.    Any ideas?


Canon Pro Platinum, Canon Semi-Gloss, Canon Pro Luster, and Ilford Smooth Gloss papers
16-bit PSD file; ProphotoRGB


Win10 PC ; AMD Processor; ATI workstation graphics card; Photoshop CC
Printer Driver 1.03; XPS Driver 5.98; Firmware 2.60



Windows 10 Configuration below:
OS Name   Microsoft Windows 10 Pro
Version   10.0.16299 Build 16299
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name   xxxxxxxxxxx
System Manufacturer   System manufacturer
System Model   System Product Name
System Type   x64-based PC
System SKU   SKU
Processor   AMD Ryzen 7 1700 Eight-Core Processor, 3693 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. 1701, 9/22/2017
SMBIOS Version   3.0
Embedded Controller Version   255.255
BIOS Mode   UEFI
BaseBoard Manufacturer   ASUSTeK COMPUTER INC.
BaseBoard Model   Not Available
BaseBoard Name   Base Board
Platform Role   Desktop
Secure Boot State   Off
PCR7 Configuration   Binding Not Possible
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume2
Locale   United States
Hardware Abstraction Layer   Version = "10.0.16299.98"
User Name    xxxxxxxxxxxx
Time Zone   Pacific Standard Time
Installed Physical Memory (RAM)   16.0 GB
Total Physical Memory   15.9 GB
Available Physical Memory   9.65 GB
Total Virtual Memory   46.9 GB
Available Virtual Memory   38.5 GB
Page File Space   31.0 GB
Page File   C:\pagefile.sys
Virtualization-based security   Not enabled
Device Encryption Support   Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions   Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualization Enabled in Firmware   No
Hyper-V - Data Execution Protection   Yes

« Last Edit: February 14, 2018, 05:50:46 AM by loganross » Logged
Fred A
Forum Superhero
*****
Posts: 5644



WWW Email
« Reply #19 on: February 14, 2018, 11:37:15 AM »

Quote
Canon Pro Platinum, Canon Semi-Gloss, Canon Pro Luster, and Ilford Smooth Gloss papers
16-bit PSD file; ProphotoRGB

Hi Logan,
Where do you see or use Prophoto.icm in your setup.?
It is not a printer profile. Please use the proper printer profile to match the paper you are using.
See two screen snaps attached.
One shows selecting the profile and the second one shows the profile sitting in its place in the Qimage properties and settings.
« Last Edit: February 14, 2018, 11:40:36 AM by Fred A » Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3251



WWW
« Reply #20 on: February 14, 2018, 12:10:05 PM »

Quote
Fortunately, Qimage lets me preview, so I see the problem before it actually prints.
Do you mean Print Preview as set in the driver? If so that never gives an accurate rendition of colour.
Or, were you using QU full screen view by hovering mouse over the thumb and pressing the space bar? Using CTRL C at the same time does a soft proof but I find that can be misleading even with top qulity printer profiles and a high grade calibrated monitor.
Have you actually made a print?
Terry
Logged
loganross
Newbie
*
Posts: 43


« Reply #21 on: February 14, 2018, 03:28:19 PM »

Thanks for the info. To be clear, prophotorgb is for the file, not the printer. I select the appropriate manufacturer profile for each paper. I have been printing, and working with profiles for over 10 years, including having custom printer profiles made, calibrating my monitor, and making my own custom camera profiles.  I am confident that I have set things up properly


Quote
Canon Pro Platinum, Canon Semi-Gloss, Canon Pro Luster, and Ilford Smooth Gloss papers
16-bit PSD file; ProphotoRGB

Hi Logan,
Where do you see or use Prophoto.icm in your setup.?
It is not a printer profile. Please use the proper printer profile to match the paper you are using.
See two screen snaps attached.
One shows selecting the profile and the second one shows the profile sitting in its place in the Qimage properties and settings.

Logged
loganross
Newbie
*
Posts: 43


« Reply #22 on: February 14, 2018, 03:30:33 PM »

Hi,
In the printer driver, I select preview before printing. In terms of the pink alien skin, that preview is accurate. If it shows there, it shows in the print.  If it does not, then it doesn't show in the print.  In all other areas of the software, the picture shows exactly how it should look.


Quote
Fortunately, Qimage lets me preview, so I see the problem before it actually prints.
Do you mean Print Preview as set in the driver? If so that never gives an accurate rendition of colour.
Or, were you using QU full screen view by hovering mouse over the thumb and pressing the space bar? Using CTRL C at the same time does a soft proof but I find that can be misleading even with top qulity printer profiles and a high grade calibrated monitor.
Have you actually made a print?
Terry
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« Reply #23 on: February 14, 2018, 04:18:41 PM »

Hi,
In the printer driver, I select preview before printing. In terms of the pink alien skin, that preview is accurate. If it shows there, it shows in the print.  If it does not, then it doesn't show in the print.  In all other areas of the software, the picture shows exactly how it should look.

There are three possibilities here:

(1) The image: the PSD format is not a standard but rather is proprietary so you can't always depend on non-Photoshop software being able to read them properly.  Hold your mouse over the thumbnail and make sure the status bar on the bottom of the main window shows ProPhoto as the color space (since you said your image was in ProPhoto RGB).  If a problem is suspected, try re-saving the same image in 16 bit TIFF format instead of PSD to make sure we don't have a PSD compatibility issue.

(2) The profile: I've seen my share of "broken" printer profiles.  Where did you get the profile you are using?  Is it a Canon profile or a custom profile?  Some software such as Photoshop will actually ignore a profile if they see something about the profile that they don't "like", such as a bad look up table, etc.  If you are using a custom profile, try using a standard Canon profile for the paper you are using or at least use the Canon profile closest to the paper type you are using: just to see if you get the same look/problem with another profile.

(3) The driver: incorrect driver settings is probably the most common issue affecting color output.  If you are convinced you have made all the correct settings in the driver, let's reset the driver and start over: select your printer and then click the "Reset preferences to printer defaults" button to the right of the "Properties" button on the Printers and Settings Tab.  Then choose "Printer" to reset all preferences for your printer.  After that, click "Properties" and set up the driver settings from scratch (be sure to not load any saved setups because they could be incompatible).  Driver settings can sometimes get corrupted when the manufacturer updates the driver and doesn't specify a new driver version, forcing QU to load settings from an older driver version which may not be compatible a recently updated driver.

I listed the most common possibilities although if the image shows correctly when you do a full screen view, we can probably rule out #1 and the problem would seem to like somewhere in items 2 and/or 3.

Regards,
Mike
Logged
loganross
Newbie
*
Posts: 43


« Reply #24 on: February 14, 2018, 04:43:13 PM »

Thank you for the reply. The profiles are the profiles made by Canon and ilford respectively.  I will try you suggestions below and report back.


Hi,
In the printer driver, I select preview before printing. In terms of the pink alien skin, that preview is accurate. If it shows there, it shows in the print.  If it does not, then it doesn't show in the print.  In all other areas of the software, the picture shows exactly how it should look.

There are three possibilities here:

(1) The image: the PSD format is not a standard but rather is proprietary so you can't always depend on non-Photoshop software being able to read them properly.  Hold your mouse over the thumbnail and make sure the status bar on the bottom of the main window shows ProPhoto as the color space (since you said your image was in ProPhoto RGB).  If a problem is suspected, try re-saving the same image in 16 bit TIFF format instead of PSD to make sure we don't have a PSD compatibility issue.

(2) The profile: I've seen my share of "broken" printer profiles.  Where did you get the profile you are using?  Is it a Canon profile or a custom profile?  Some software such as Photoshop will actually ignore a profile if they see something about the profile that they don't "like", such as a bad look up table, etc.  If you are using a custom profile, try using a standard Canon profile for the paper you are using or at least use the Canon profile closest to the paper type you are using: just to see if you get the same look/problem with another profile.

(3) The driver: incorrect driver settings is probably the most common issue affecting color output.  If you are convinced you have made all the correct settings in the driver, let's reset the driver and start over: select your printer and then click the "Reset preferences to printer defaults" button to the right of the "Properties" button on the Printers and Settings Tab.  Then choose "Printer" to reset all preferences for your printer.  After that, click "Properties" and set up the driver settings from scratch (be sure to not load any saved setups because they could be incompatible).  Driver settings can sometimes get corrupted when the manufacturer updates the driver and doesn't specify a new driver version, forcing QU to load settings from an older driver version which may not be compatible a recently updated driver.

I listed the most common possibilities although if the image shows correctly when you do a full screen view, we can probably rule out #1 and the problem would seem to like somewhere in items 2 and/or 3.

Regards,
Mike
Logged
loganross
Newbie
*
Posts: 43


« Reply #25 on: February 14, 2018, 04:53:35 PM »

Hi,
Just a quick follow-up to make sure I get this correct. Should I be using the XPS driver to ensure a 16 bit pipeline to the printer?  Thanks.
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« Reply #26 on: February 14, 2018, 09:40:38 PM »

Hi,
Just a quick follow-up to make sure I get this correct. Should I be using the XPS driver to ensure a 16 bit pipeline to the printer?  Thanks.

You can use either the normal driver or the XPS driver because QU's dithering (sub-sampling) will send the same data to both and will produce 16 bit gradients on both drivers.  In my experience with Canon drivers, the XPS drivers can be a bit buggy so in all honesty, I think I'd stick with the regular (non-XPS) driver.

Mike
Logged
loganross
Newbie
*
Posts: 43


« Reply #27 on: February 16, 2018, 05:28:18 AM »

Thank you.  I seem to have overcome the pink alien skin issue.  Out of about 15 prints, I did have two come out with a greenish cast, but it may just be learning curve on my part.  You mentioned sub-sampling.  Does that mean you change the data?  The reason I ask is I would like to understand whether there are any special steps I need to take if I need to print targets for custom icc profiles?  Specifically, I am using the Chromix service, which prints the targets directly from their Maxwell client application.  Does that create any issue?  My understanding is that for ImagePrint (by colorbyte SW), you have to print the targets from within imageprint as their interaction with the printer via the driver goes beyond what other applications can do.


PS, I have a question about Imageprint, but I will save it for another thread.

Thank you.

Hi,
Just a quick follow-up to make sure I get this correct. Should I be using the XPS driver to ensure a 16 bit pipeline to the printer?  Thanks.

You can use either the normal driver or the XPS driver because QU's dithering (sub-sampling) will send the same data to both and will produce 16 bit gradients on both drivers.  In my experience with Canon drivers, the XPS drivers can be a bit buggy so in all honesty, I think I'd stick with the regular (non-XPS) driver.

Mike
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3251



WWW
« Reply #28 on: February 16, 2018, 07:45:31 AM »

Quote
The reason I ask is I would like to understand whether there are any special steps I need to take if I need to print targets for custom icc profiles?  
Yes there is and QU has a special JOB included which sets up QU for target printing.
See attached screen shot.
Click the Recall icon, select "J" for job and scroll down to {Q} printer target setup.job.
Edit:
I've added a screen shot of QU settings for a target I printed in January
Terry
« Last Edit: February 16, 2018, 07:54:16 AM by Terry-M » Logged
loganross
Newbie
*
Posts: 43


« Reply #29 on: February 18, 2018, 08:06:19 PM »









Thank you.


Quote
The reason I ask is I would like to understand whether there are any special steps I need to take if I need to print targets for custom icc profiles?  
Yes there is and QU has a special JOB included which sets up QU for target printing.
See attached screen shot.
Click the Recall icon, select "J" for job and scroll down to {Q} printer target setup.job.
Edit:
I've added a screen shot of QU settings for a target I printed in January
Terry
Logged
Pages: 1 [2] 3
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Security updates 2022 by ddisoftware, Inc.