Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #172805 > unrolled thread

Canon printer minor quibble

Back to article view | Back to linux.debian.user

Contents

  Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-26 17:00 +0200
    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-26 18:20 +0200
      Re: Canon printer minor quibble deloptes <deloptes@gmail.com> - 2016-09-26 19:20 +0200
        Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-27 01:20 +0200
      Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-27 01:10 +0200
        Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-28 00:00 +0200
          Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-28 00:50 +0200
            Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-28 12:30 +0200
              Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-29 17:10 +0200
                Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-29 19:10 +0200
                  Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-30 15:40 +0200
                    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 19:20 +0200
                      Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 01:40 +0200
                        Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-01 15:30 +0200
                          Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 16:10 +0200
                            Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-01 16:40 +0200
                Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-29 23:40 +0200
                  Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-30 14:00 +0200
                    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 14:40 +0200
                      Re: Canon printer minor quibble Mark Fletcher <mark27q1@gmail.com> - 2016-09-30 15:10 +0200
                        Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-30 15:30 +0200
                          Re: Canon printer minor quibble Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-30 15:30 +0200
                            Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 16:10 +0200
                          Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 16:00 +0200
                            Re: Canon printer minor quibble Frank <zuiderduin@gmx.com> - 2016-09-30 16:30 +0200
                              Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 16:40 +0200
                                Re: Canon printer minor quibble Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-30 16:50 +0200
                                  Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 17:10 +0200
                                  Re: Canon printer minor quibble rhkramer@gmail.com - 2016-09-30 17:20 +0200
                                    Re: Canon printer minor quibble John Hasler <jhasler@newsguy.com> - 2016-09-30 17:30 +0200
                                    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 20:30 +0200
                                      Re: Canon printer minor quibble Charlie <ariestao1@ipstarmail.com.au> - 2016-09-30 23:50 +0200
                                      Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-01 00:50 +0200
                                        Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-01 21:50 +0200
                                          Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-02 01:00 +0200
                            Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-30 16:30 +0200
                              Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 17:00 +0200
                                Re: Canon printer minor quibble Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-30 17:10 +0200
                                  Re: Canon printer minor quibble John Hasler <jhasler@newsguy.com> - 2016-09-30 17:30 +0200
                                    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 17:40 +0200
                                  Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 17:40 +0200
                                Re: Canon printer minor quibble Reco <recoverym4n@gmail.com> - 2016-09-30 17:20 +0200
                                  Re: Canon printer minor quibble Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-30 17:40 +0200
                                    Re: Canon printer minor quibble Gene Heskett <gheskett@shentel.net> - 2016-09-30 20:00 +0200
                                  Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 19:10 +0200
                        Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 15:50 +0200
                          Re: Canon printer minor quibble David Wright <deblis@lionunicorn.co.uk> - 2016-09-30 23:00 +0200
                            Re: Canon printer minor quibble Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-30 23:10 +0200
                              Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-09-30 23:50 +0200
                                Re: Canon printer minor quibble David Wright <deblis@lionunicorn.co.uk> - 2016-10-01 07:50 +0200
                                  Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-01 10:40 +0200
                                    Re: Canon printer minor quibble Gene Heskett <gheskett@shentel.net> - 2016-10-01 12:20 +0200
                                  Re: Canon printer minor quibble Gene Heskett <gheskett@shentel.net> - 2016-10-01 12:10 +0200
                                    Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-01 21:00 +0200
                          Re: Canon printer minor quibble David Wright <deblis@lionunicorn.co.uk> - 2016-10-05 22:20 +0200
                            Re: Canon printer minor quibble Brian <ad44@cityscape.co.uk> - 2016-10-06 01:30 +0200

Page 1 of 3  [1] 2 3  Next page →

#172805 — Canon printer minor quibble

Finally getting around to raising an issue I have faced for years and 
never made much inroads into...

I have a Canon iX6530 A4 / A3 inkjet printer purchased in Japan. It is 
connected via a USB cable to my Jessie PC. I have the Canon 
iX6500-series driver installed. It seems to work fine.

I have shared the printer via CUPS and, sometime back, also fannied 
around with AirPrint in a way I don't completely remember as well as 
fannying around with samba print sharing in the apparently mistaken 
belief that these were needed to share the printer with Windows.

I am successfully able to print to the printer from the Jessie box it is 
connected to, and also from my iOS devices of various stripes and ages, 
Windows 7 VMs running on the Jessie machine, a stretch box also on my 
network -- in short, anything I try to.

The issue is that, when I print a photo natively from Jessie, the 
colours come out rather dark and the overall resulting picture isn't 
very good. Photos in particular suffer for this but I even notice it 
with coloured text -- for example printing a PDF with a table where a 
cell is shaded in green, it comes out of the printer looking nearer to 
black. It's green, but it's very, very dark.

On the other hand, when I print the same images from the Windows VMs, 
they come out great. Colours are better balanced and the photos look 
much better. The above-mentioned PDF table cell comes out looking green 
not black.

Keep in mind the only route to this printer is through the USB cable 
attached to the Jessie box. I don't know how data from the Windows 
machines is getting to CUPS, exactly (Windows sees a network printer but 
I don't know which of the redundant setups I did is serving it) but once 
it gets there everything from that point, most notably the printer 
driver, is the same.

I can just print from Windows when I want a good quality outcome, but it 
doesn't sit well with me that Windows is doing something better than 
Jessie, so I want to fix it. Any idea what I should be looking at?

Thanks

Mark

[toc] | [next] | [standalone]

#172816

On Mon 26 Sep 2016 at 23:50:39 +0900, Mark Fletcher wrote:

> Finally getting around to raising an issue I have faced for years and 
> never made much inroads into...
> 
> I have a Canon iX6530 A4 / A3 inkjet printer purchased in Japan. It is 
> connected via a USB cable to my Jessie PC. I have the Canon 
> iX6500-series driver installed. It seems to work fine.
> 
> I have shared the printer via CUPS and, sometime back, also fannied 
> around with AirPrint in a way I don't completely remember as well as 
> fannying around with samba print sharing in the apparently mistaken 
> belief that these were needed to share the printer with Windows.
> 
> I am successfully able to print to the printer from the Jessie box it is 
> connected to, and also from my iOS devices of various stripes and ages, 
> Windows 7 VMs running on the Jessie machine, a stretch box also on my 
> network -- in short, anything I try to.
> 
> The issue is that, when I print a photo natively from Jessie, the 
> colours come out rather dark and the overall resulting picture isn't 
> very good. Photos in particular suffer for this but I even notice it 
> with coloured text -- for example printing a PDF with a table where a 
> cell is shaded in green, it comes out of the printer looking nearer to 
> black. It's green, but it's very, very dark.
> 
> On the other hand, when I print the same images from the Windows VMs, 
> they come out great. Colours are better balanced and the photos look 
> much better. The above-mentioned PDF table cell comes out looking green 
> not black.
> 
> Keep in mind the only route to this printer is through the USB cable 
> attached to the Jessie box. I don't know how data from the Windows 
> machines is getting to CUPS, exactly (Windows sees a network printer but 
> I don't know which of the redundant setups I did is serving it) but once 
> it gets there everything from that point, most notably the printer 
> driver, is the same.

I know nothing about Windows 7 or VMs, although I believe the latter
allows an OS to be run in just the same way it would on bare metal.

How the data from Windows gets to CUPS isn't, I think, important,
although with the Stretch box the network would be involved. My
understanding is that the data coming from Windows has already been
processed by Windows, so therein lies one difference between the file
arriving at the CUPS server from Windows and that from Jessie.

The Jessie file will be sent as-is to be filtered and rendered by CUPS.
The Windows file could very well just pass through CUPS and go directly
to the printer. Only an error_log would reveal what is happening.

The colour abnormality could be simply be because the Canon driver is
rubbish at colour management or it needs adjusting. There is a driver in
printer-driver-gutenprint which is for your printer; I'd suggest testing
that with the printer. It comes with the cups-calibrate program.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172819

Brian wrote:

> On Mon 26 Sep 2016 at 23:50:39 +0900, Mark Fletcher wrote:
...
> 
> The colour abnormality could be simply be because the Canon driver is
> rubbish at colour management or it needs adjusting. There is a driver in
> printer-driver-gutenprint which is for your printer; I'd suggest testing
> that with the printer. It comes with the cups-calibrate program.

Not to forget the color profiles delivered by vendor, but usually one could
setup different management profiles also in the cups driver on the
frontend/backend side.
I would check there too. It must be something like RGB, CYMK, native etc.

regards

[toc] | [prev] | [next] | [standalone]

#172830

On Mon, Sep 26, 2016 at 07:14:26PM +0200, deloptes wrote:
> Brian wrote:
> 
> > On Mon 26 Sep 2016 at 23:50:39 +0900, Mark Fletcher wrote:
> ...
> > 
> > The colour abnormality could be simply be because the Canon driver is
> > rubbish at colour management or it needs adjusting. There is a driver in
> > printer-driver-gutenprint which is for your printer; I'd suggest testing
> > that with the printer. It comes with the cups-calibrate program.
> 
> Not to forget the color profiles delivered by vendor, but usually one could
> setup different management profiles also in the cups driver on the
> frontend/backend side.
> I would check there too. It must be something like RGB, CYMK, native etc.
> 

Yes, I have fiddled with that in the past, on printing from say evince 
or gimp, I don't recall getting it to make any difference. Which 
probably means something is overriding it, or "compensating" in some 
way, trying to be clever...

Mark

[toc] | [prev] | [next] | [standalone]

#172829

On Mon, Sep 26, 2016 at 05:17:40PM +0100, Brian wrote:
> 
> The colour abnormality could be simply be because the Canon driver is
> rubbish at colour management or it needs adjusting. There is a driver in
> printer-driver-gutenprint which is for your printer; I'd suggest testing
> that with the printer. It comes with the cups-calibrate program.
> 

Thanks. I am using the Gutenprint driver. I see cups-calibrate in my 
future -- didn't know that existed. I'd been sort of hidebound by the 
assumption that everything from Windows must have been going through the 
same CUPS path as everything from Linux -- but the evidence sort of 
disproves that doesn't it. Thanks, I'll look into cups-calibrate.

Mark

[toc] | [prev] | [next] | [standalone]

#172872

On Tue 27 Sep 2016 at 08:09:07 +0900, Mark Fletcher wrote:

> On Mon, Sep 26, 2016 at 05:17:40PM +0100, Brian wrote:
> > 
> > The colour abnormality could be simply be because the Canon driver is
> > rubbish at colour management or it needs adjusting. There is a driver in
> > printer-driver-gutenprint which is for your printer; I'd suggest testing
> > that with the printer. It comes with the cups-calibrate program.
> > 
> 
> Thanks. I am using the Gutenprint driver. I see cups-calibrate in my 
> future -- didn't know that existed. I'd been sort of hidebound by the 
> assumption that everything from Windows must have been going through the 
> same CUPS path as everything from Linux -- but the evidence sort of 
> disproves that doesn't it. Thanks, I'll look into cups-calibrate.

It wasn't cups-calibrate I was really advocating but the trying out of
printing a file using the Canon and Gutenprint drivers. Do both give the
same outcome?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172874

On Tue, Sep 27, 2016 at 10:53:11PM +0100, Brian wrote:
> 
> It wasn't cups-calibrate I was really advocating but the trying out of
> printing a file using the Canon and Gutenprint drivers. Do both give the
> same outcome?

Sorry Brian, I think some confusion there due to my phrasing in the 
original post. There is, to my knowledge, no Canon-supplied Linux CUPS 
driver for this printer. When I said some variation of "Canon iX6500 
series driver" in my original post, I was referring to the Gutenprint 
driver as that is what the Gutenprint driver is called.

Now I will be honest, I haven't googled this recently, and don't have 
time to even now as I am actually supposed to be in the shower and then 
on my way to work, but I will check later... but at the time I first set 
this printer up I could not find anything from Canon for Linux for this 
printer. Language may have been getting in the way at the time, as this 
particular model number is/was only ever sold in Japan to my knowledge.

In the very early days Gutenprint didn't have a driver either and I was 
using a driver with a very approximately similar name which very 
approximately worked... but in the fullness of time the Gutenprint 
driver I am using appeared (or I finally saw what was in front of my 
face, that is also possible) and I am using it now. The darkness of 
native Linux printing, and the contrast if you will pardon the pun 
between that and printing from Windows, didn't strike me until some time 
later when the driver situation had been stable for some time.

So to the best of my knowledge I'm using the right driver, all functions 
certainly work, and the only issue is how dark the images come out, 
compared to the high quality results I get when I print from Windows.

Incidentally, the printer _does_ come with a driver (and a ton of 
bloatware) for Windows. On one Windows printer I installed the driver 
and the bloatware, on the other VM I installed the absolute minimum to 
get the network printer to install. (and when I say network printer, I 
mean from Windows' perspective -- this printer is not a network printer 
as far as it is concerned, there is no ethernet port on it, the only way 
in is USB). So the bloatware isn't the reason the printer is looking 
better under Windows, since both VMs can print with better results (and 
the same as each other).

So I am being drawn to the conclusion that your comments about the 
non-existent Canon driver (it being rubbish at colour management) can be 
applied instead to the Gutenprint driver, hence the way I perked up when 
you mentioned cups-calibrate. Which I will try the second I get longer 
than 5 mins in front of my PC.

Thanks

Mark

[toc] | [prev] | [next] | [standalone]

#172885

On Wed 28 Sep 2016 at 07:43:54 +0900, Mark Fletcher wrote:

> On Tue, Sep 27, 2016 at 10:53:11PM +0100, Brian wrote:
> > 
> > It wasn't cups-calibrate I was really advocating but the trying out of
> > printing a file using the Canon and Gutenprint drivers. Do both give the
> > same outcome?
> 
> Sorry Brian, I think some confusion there due to my phrasing in the 
> original post. There is, to my knowledge, no Canon-supplied Linux CUPS 
> driver for this printer. When I said some variation of "Canon iX6500 
> series driver" in my original post, I was referring to the Gutenprint 
> driver as that is what the Gutenprint driver is called.

https://www.canondrivers.org/canon-pixma-ix6500-series-driver-download/
 
> Now I will be honest, I haven't googled this recently, and don't have 
> time to even now as I am actually supposed to be in the shower and then 
> on my way to work, but I will check later... but at the time I first set 
> this printer up I could not find anything from Canon for Linux for this 
> printer. Language may have been getting in the way at the time, as this 
> particular model number is/was only ever sold in Japan to my knowledge.
> 
> In the very early days Gutenprint didn't have a driver either and I was 
> using a driver with a very approximately similar name which very 
> approximately worked... but in the fullness of time the Gutenprint 
> driver I am using appeared (or I finally saw what was in front of my 
> face, that is also possible) and I am using it now. The darkness of 
> native Linux printing, and the contrast if you will pardon the pun 
> between that and printing from Windows, didn't strike me until some time 
> later when the driver situation had been stable for some time.

A driver came in Gutenprint 5.2.10 (May 2014)

> So to the best of my knowledge I'm using the right driver, all functions 
> certainly work, and the only issue is how dark the images come out, 
> compared to the high quality results I get when I print from Windows.

The driver is marked EXPERIMENTAL, which could be because it hasn't been
extensively tested.

> Incidentally, the printer _does_ come with a driver (and a ton of 
> bloatware) for Windows. On one Windows printer I installed the driver 
> and the bloatware, on the other VM I installed the absolute minimum to 
> get the network printer to install. (and when I say network printer, I 
> mean from Windows' perspective -- this printer is not a network printer 
> as far as it is concerned, there is no ethernet port on it, the only way 
> in is USB). So the bloatware isn't the reason the printer is looking 
> better under Windows, since both VMs can print with better results (and 
> the same as each other).
> 
> So I am being drawn to the conclusion that your comments about the 
> non-existent Canon driver (it being rubbish at colour management) can be 
> applied instead to the Gutenprint driver, hence the way I perked up when 
> you mentioned cups-calibrate. Which I will try the second I get longer 
> than 5 mins in front of my PC.

You should now be able to compare the outputs of the Gutenprint and
Canon drivers. Color management support is done by cups-filters
(completed in Aug 2014) so it will be common to both drivers.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172939

On Wed, Sep 28, 2016 at 11:25:19AM +0100, Brian wrote:
> On Wed 28 Sep 2016 at 07:43:54 +0900, Mark Fletcher wrote:
> 
> > Sorry Brian, I think some confusion there due to my phrasing in the 
> > original post. There is, to my knowledge, no Canon-supplied Linux CUPS 
> > driver for this printer. When I said some variation of "Canon iX6500 
> > series driver" in my original post, I was referring to the Gutenprint 
> > driver as that is what the Gutenprint driver is called.
> 
> https://www.canondrivers.org/canon-pixma-ix6500-series-driver-download/
>  
<snip>
> 
> You should now be able to compare the outputs of the Gutenprint and
> Canon drivers. Color management support is done by cups-filters
> (completed in Aug 2014) so it will be common to both drivers.
> 

Just to say I have downloaded the Canon driver, and also did an 
independent search for the specific model, which indeed only seems to be 
specifically mentioned on Japanese sites. But searches there take me to 
the same driver, so that is good. I'll install this and try test 
printing as soon as I have enough time in front of this machine, may be 
the weekend the way this week is going.

Didn't want you to think I had wandered off. Appreciate your help.

One thing I noticed -- the site mentions CUPS drivers, but only in 
connection with the Mac version of the driver, which I find ironic 
considering what the U of CUPS stands for. On the other hand the Linux 
driver doesn't mention CUPS. However, on downloading the Linux driver 
and pawing through the files that come with it, the install shell script 
is looking for a working CUPS installation which is somewhat reassuring.

Anyway will finish trying to understand that shell script later -- it 
wants me to run it as root, no way I am doing that until I have 
satisfied myself I know roughly what it is going to do -- and then will 
install the driver and compare the output.

More to follow...

Mark

[toc] | [prev] | [next] | [standalone]

#172942

On Fri 30 Sep 2016 at 00:03:38 +0900, Mark Fletcher wrote:

> On Wed, Sep 28, 2016 at 11:25:19AM +0100, Brian wrote:
> > You should now be able to compare the outputs of the Gutenprint and
> > Canon drivers. Color management support is done by cups-filters
> > (completed in Aug 2014) so it will be common to both drivers.
> 
> Just to say I have downloaded the Canon driver, and also did an 
> independent search for the specific model, which indeed only seems to be 
> specifically mentioned on Japanese sites. But searches there take me to 
> the same driver, so that is good. I'll install this and try test 
> printing as soon as I have enough time in front of this machine, may be 
> the weekend the way this week is going.
> 
> Didn't want you to think I had wandered off. Appreciate your help.

Appreciated.

> One thing I noticed -- the site mentions CUPS drivers, but only in 
> connection with the Mac version of the driver, which I find ironic 
> considering what the U of CUPS stands for. On the other hand the Linux 
> driver doesn't mention CUPS. However, on downloading the Linux driver 
> and pawing through the files that come with it, the install shell script 
> is looking for a working CUPS installation which is somewhat reassuring.

The Mac only has CUPS printing system whereas Linux additionally has
lprng. That might not be the significance, of course. Note that if you
asked upstream what CUPS stood for they would probably say "nothing".

> Anyway will finish trying to understand that shell script later -- it 
> wants me to run it as root, no way I am doing that until I have 
> satisfied myself I know roughly what it is going to do -- and then will 
> install the driver and compare the output.

Be a Debian man; dispense with that script and install the two provided
debs with 'dpkg -i'. I don't want to spoil the fun but will mention that
'apt-get -f install' and Wheezy are your friends.

> More to follow...

It gets boring after the package install. A print queue is easily set up
and printing to file gives no trouble.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172968

On Thu, Sep 29, 2016 at 06:05:27PM +0100, Brian wrote:
> On Fri 30 Sep 2016 at 00:03:38 +0900, Mark Fletcher wrote:
> 
> > Anyway will finish trying to understand that shell script later -- it 
> > wants me to run it as root, no way I am doing that until I have 
> > satisfied myself I know roughly what it is going to do -- and then will 
> > install the driver and compare the output.
> 
> Be a Debian man; dispense with that script and install the two provided
> debs with 'dpkg -i'. I don't want to spoil the fun but will mention that
> 'apt-get -f install' and Wheezy are your friends.
> 

This is what I did although in practice neither apt-get -f install nor 
Wheezy were needed.

> It gets boring after the package install. A print queue is easily set up
> and printing to file gives no trouble.
> 

Indeed -- 2 dpkg -i invokations, and a setup of the printer in the CUPS 
web admin tool, and I was done. I set up the "new" printer with a 
slightly different name, so both can co-exist on the system. Looking at 
the test page I could immediately see the colours were less dark with 
the Canon driver. I then tried printing a couple of photos I had lying 
around and they come out much better with the Canon driver. Windows 
cannot print to the new CUPS printer, so clearly some of my fannying 
around with AirPrint and/or samba did actually do something useful after 
all. But Windows can still print, using the old printer, which has 
always been good quality, and direct Linux printing can now get better 
quality than before, so I am happy.

Thanks a lot Brian for your advice with this.

Mark

[toc] | [prev] | [next] | [standalone]

#172993

On Fri 30 Sep 2016 at 22:31:24 +0900, Mark Fletcher wrote:

> On Thu, Sep 29, 2016 at 06:05:27PM +0100, Brian wrote:
> > On Fri 30 Sep 2016 at 00:03:38 +0900, Mark Fletcher wrote:
> > 
> > > Anyway will finish trying to understand that shell script later -- it 
> > > wants me to run it as root, no way I am doing that until I have 
> > > satisfied myself I know roughly what it is going to do -- and then will 
> > > install the driver and compare the output.
> > 
> > Be a Debian man; dispense with that script and install the two provided
> > debs with 'dpkg -i'. I don't want to spoil the fun but will mention that
> > 'apt-get -f install' and Wheezy are your friends.
> > 
> 
> This is what I did although in practice neither apt-get -f install nor 
> Wheezy were needed.

Strange. cnijfilter-ix6500series_3.50-1_amd64.deb depends on libtiff4,
which in turn depends on libjeg8. Nether of these is in Jessie. Could it
be you already had them on your system?

> > It gets boring after the package install. A print queue is easily set up
> > and printing to file gives no trouble.
> 
> Indeed -- 2 dpkg -i invokations, and a setup of the printer in the CUPS 
> web admin tool, and I was done. I set up the "new" printer with a 
> slightly different name, so both can co-exist on the system. Looking at 
> the test page I could immediately see the colours were less dark with 
> the Canon driver. I then tried printing a couple of photos I had lying 
> around and they come out much better with the Canon driver. Windows 
> cannot print to the new CUPS printer, so clearly some of my fannying 
> around with AirPrint and/or samba did actually do something useful after 
> all. But Windows can still print, using the old printer, which has 
> always been good quality, and direct Linux printing can now get better 
> quality than before, so I am happy.
> 
> Thanks a lot Brian for your advice with this.

You're welcome.

-- 
Brian.
Who is beginning to wish Apple had renamed its printing software to SPUC.

[toc] | [prev] | [next] | [standalone]

#173008

On Fri, Sep 30, 2016 at 06:10:43PM +0100, Brian wrote:
> On Fri 30 Sep 2016 at 22:31:24 +0900, Mark Fletcher wrote:
> 
> > This is what I did although in practice neither apt-get -f install nor 
> > Wheezy were needed.
> 
> Strange. cnijfilter-ix6500series_3.50-1_amd64.deb depends on libtiff4,
> which in turn depends on libjeg8. Nether of these is in Jessie. Could it
> be you already had them on your system?
> 

Yep, both are present here -- I can only assume that is because this 
system, as I've mentioned in past threads but did not in this one, was 
originally installed when etch was testing, and has been steadily 
upgraded since then as each new distribution became testing, until 
Jessie became stable at which point I didn't upgrade to stretch because 
by that time this machine was doing important enough things for me that 
I didn't want downtime for breakages.

Interestingly, both show as "Automatically Installed" according to aptitude. And yet if nothing depends on them in Jessie, I would have expected them to be removed... 

"aptitude why" answers the question for one of them. libjpeg8 is 
depended on by libgphoto2-2. I assume that's also an old package but it 
is installed on my machine and not automatically, I must have asked for 
it at some point. That library is about digital cameras so I assume I 
was wrestling with getting a digital camera to work with the PC at some 
point in the past. I don't remember that but it's entirely possible. 
Presumably nothing in Jessie actually conflicts with either libgphoto2-2 
or libjpeg8.

Libtiff4 is a little bit more interesting. "aptitude why" says that it 
is installed because the Canon printer driver needs it (by the way 
libjpeg8 did *not* say that the Canon printer driver needed it) and 
nothing else. So I'm less sure about what it was doing on my system 
before this. But, happily, it was there.

Mark

[toc] | [prev] | [next] | [standalone]

#173045

On Sat 01 Oct 2016 at 08:34:34 +0900, Mark Fletcher wrote:

> Libtiff4 is a little bit more interesting. "aptitude why" says that it 
> is installed because the Canon printer driver needs it (by the way 
> libjpeg8 did *not* say that the Canon printer driver needed it) and 
> nothing else. So I'm less sure about what it was doing on my system 
> before this. But, happily, it was there.

The Canon printer driver does not depend on libjpeg8. It is libtiff4
which does.

Regarding the darker colors with the Gutenprint driver: does setting
Color Model to CMYK make any difference?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173051

On Sat, Oct 01, 2016 at 02:28:30PM +0100, Brian wrote:
> On Sat 01 Oct 2016 at 08:34:34 +0900, Mark Fletcher wrote:
> 
> > Libtiff4 is a little bit more interesting. "aptitude why" says that it 
> > is installed because the Canon printer driver needs it (by the way 
> > libjpeg8 did *not* say that the Canon printer driver needed it) and 
> > nothing else. So I'm less sure about what it was doing on my system 
> > before this. But, happily, it was there.
> 
> The Canon printer driver does not depend on libjpeg8. It is libtiff4
> which does.

Right, I get that (although I see why my reply might imply I didn't), 
but "aptitude why" is not acknowledging that dependency, which 
interested me... I guess it omits dependencies from things that are 
themselves automatically installed, perhaps?

> 
> Regarding the darker colors with the Gutenprint driver: does setting
> Color Model to CMYK make any difference?
> 

Out of curiosity I tried that last night. Actually more accurately I 
tried CMY, not CMYK. It made no difference. What is the K of CMYK? Cyan, 
Magenta, Yellow, Kick-Ass??? Is there any reason I should expect CMYK to 
do better than CMY or RGB?

Mark

[toc] | [prev] | [next] | [standalone]

#173057

On Sat 01 Oct 2016 at 23:05:58 +0900, Mark Fletcher wrote:

> On Sat, Oct 01, 2016 at 02:28:30PM +0100, Brian wrote:
> > 
> > Regarding the darker colors with the Gutenprint driver: does setting
> > Color Model to CMYK make any difference?
> > 
> Out of curiosity I tried that last night. Actually more accurately I 
> tried CMY, not CMYK. It made no difference. What is the K of CMYK? Cyan, 
> Magenta, Yellow, Kick-Ass??? Is there any reason I should expect CMYK to 
> do better than CMY or RGB?

K is black. It stands for "key". The three other colours are keyed
to it.

You shouldn't expect anything but CMYK sometimes produces an improvement.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172946

On Thursday 29 September 2016 16:03:38 Mark Fletcher wrote:
> which I find ironic
> considering what the U of CUPS stands for

Why?  MacOSX is Unix based (via BSD) and CUPS is supposed to be common to all 
Unices (though I have only used it on Linux and MacOSX).

Lisi

[toc] | [prev] | [next] | [standalone]

#172959

On Thu, Sep 29, 2016 at 10:31:45PM +0100, Lisi Reisz wrote:
> On Thursday 29 September 2016 16:03:38 Mark Fletcher wrote:
> > which I find ironic
> > considering what the U of CUPS stands for
> 
> Why?  MacOSX is Unix based (via BSD) and CUPS is supposed to be common to all 
> Unices (though I have only used it on Linux and MacOSX).
> 
Precisely, Lisi. Precisely.

[toc] | [prev] | [next] | [standalone]

#172960

On Fri 30 Sep 2016 at 20:54:32 +0900, Mark Fletcher wrote:

> On Thu, Sep 29, 2016 at 10:31:45PM +0100, Lisi Reisz wrote:
> > On Thursday 29 September 2016 16:03:38 Mark Fletcher wrote:
> > > which I find ironic
> > > considering what the U of CUPS stands for
> > 
> > Why?  MacOSX is Unix based (via BSD) and CUPS is supposed to be common to all 
> > Unices (though I have only used it on Linux and MacOSX).
> > 
> Precisely, Lisi. Precisely.

The "U" in CUPS officially doesn't stand for anything. The same applies
to the "C", "P" and "S".

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172962

On Fri, Sep 30, 2016 at 01:31:03PM +0100, Brian wrote:
> On Fri 30 Sep 2016 at 20:54:32 +0900, Mark Fletcher wrote:
> 
> > On Thu, Sep 29, 2016 at 10:31:45PM +0100, Lisi Reisz wrote:
> > > On Thursday 29 September 2016 16:03:38 Mark Fletcher wrote:
> > > > which I find ironic
> > > > considering what the U of CUPS stands for
> > > 
> > > Why?  MacOSX is Unix based (via BSD) and CUPS is supposed to be common to all 
> > > Unices (though I have only used it on Linux and MacOSX).
> > > 
> > Precisely, Lisi. Precisely.
> 
> The "U" in CUPS officially doesn't stand for anything. The same applies
> to the "C", "P" and "S".
> 
According to whom, Brian? (Apart from you, obviously :) ). According to 
the Internet (so it _must_ be true) it stands for Common Unix Printing 
System. Are they, and the Gutenprint driver which prints that on its 
test pages, just making sh*t up then? (To be fair I don't know which 
component creates the test page, but I do know, because I am sitting 
here with one about an inch away from my left hand, that when you ask 
CUPS to print a test page, it prints that on the test page.)

Mark (who is trying to figure out how Wheezy is going to figure in this 
driver install...)

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web