[sane-devel] Canon MAXIFY MB5300 series

Rolf Bensch rolf at bensch-online.de
Wed Sep 12 18:08:59 BST 2018


Attached you find a possible patch for the 1200dpi issue. Please report
if it's working.

Many thanks for your help.


Am 08.09.2018 um 13:20 schrieb Olaf Meeuwissen:
> Hi,
> innocence.faded at gmx.de writes:
>> Hi All,
>> as it seems that this list is largely unmaintained (the below message
>> has been sitting in quarantine for weeks now without any action), I
> Sorry to hear that.
> @allan> Are you getting notifications about quarantined mail since the
>         mailing list has been moved to the new server?
>> Here goes:
>> I am writing to this list to let you know that the above Canon MFP - a
>> 5350 in my case - works (in general) using the pixma backend.
>> (Documentation says it's untested.)
> Updated the info about this device and mentioned the issue below.
>  https://gitlab.com/sane-project/backends/commit/fd8aedea4c475f1c8c51c3efe28bc81495ece61c
> @rolf> Anything you know about this and/or could fix?
>> It's detected automatically via
>> network, so that's excellent. On top of that, I came across a peculiar
>> issue that involves scanning at 1200 dpi resolution (all other
>> resolutions work just fine):
>> When using xsane frontend, the resulting image looks as though it is
>> cut in half (vertically) and then the two halves are interlaced column
>> by column into the final result. Re-extracting the two halves is
>> actually possible using GIMP, for instance, but they do not quite add
>> up to a complete image. (A couple columns seem to be missing.)
>> When using simple-scan frontend, the resulting image looks like the
>> actual image but interlaced column by column with a white image of the
>> same size, stretching the actual image horizontally by 100 percent.
>> Erasing every other column in this output will actually yield the
>> expected and usable result.
>> This, btw., is the exact same result you get when using scanimage -
>> -resolution 1200 so I assume it's got to do with sane and/or the
>> corresponding pixma backend. I am taking a wild guess here, but could
>> this be explained by an asymmetric resolution of 600*1200 (x*y) that
>> is then inflated to 1200*1200 using white?
>> Perhaps you can look into this issue. It's good enough for me for the
>> time being - I usually scan using the embedded app on the device - but
>> could use some fixing. TIA!
>> Kind Regards,
>> Roland
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Software                        https://my.fsf.org/donate
>  Join the Free Software Foundation              https://my.fsf.org/join
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pixma_mp150.c.patch2.zip
Type: application/zip
Size: 343 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20180912/b3b65c6e/attachment.zip>

More information about the sane-devel mailing list