RSatria

Q: Yosemite Image Capture Does Not Retain Scanner Settings

I scan almost all my paper documents using Image Capture.

I use Epson WF-3520 All-in-One Printer/Scanner.

Downloaded latest Apple software for Epson WF-3520 (Version 9.04) at OS X: Printer and scanner software available for download  - Apple Support

 

Prior to installation of Yosemite, and download of Apple software for Epson WF-3520 (Version 9.04), the scanner settings I entered remained persistent.

(These settings are: Scan Mode: Document Feeder, Kind: Color, Resolution: 300 dpi, Size: US Letter, Orientation: Duplex, Scan To: Documents, Format:PDF)

 

Now, after Yosemite installation, upon opening Image Capture, the settings always revert back to what must be default settings and I have to change them all back to my preferences, which becomes frustrating after repeating the process a number of times. The settings in the Epson Scan software, however, do remain persistent.

 

I have opened the the following files looking for a <key> entry to specify my desired settings to Image Capture, but have not found the setting locations in these files:

~/Library/Preferences/com.apple.Image_Capture.plist

~/Library/Preferences/com.apple.ImageCaptureService.plist

~/Library/Preferences/com.apple.imagent.plist

~/Library/Preferences/ByHost/com.apple.ImageCapture2.908(restofID).plist

~/Library/Preferences/ByHost/com.apple.ImageCaptureExtension2.908(restofID).plis t

~/Library/Preferences/com.apple.Image_Capture.plist.(4 files with various 7 characters here)

/Library/Image Capture/Devices/EPSON Scanner

 

Please provide any information you can to help me resolve this issue. Thanks.

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10), OS X Server Yosemite

Posted on Nov 8, 2014 12:48 PM

Close

Q: Yosemite Image Capture Does Not Retain Scanner Settings

  • All replies
  • Helpful answers

Previous Page 2
  • by mc_ringbearer,

    mc_ringbearer mc_ringbearer May 8, 2015 4:30 PM in response to twooverone
    Level 1 (0 points)
    May 8, 2015 4:30 PM in response to twooverone

    I had reported a month ago that 10.10.3 seemed to fix this problem; I am posting today after using it a month and carefully observing, that 10.10.3 does NOT completely solve the issue; at least for me.  YMMV.  it appears to be intermittent.  I tried to find a pattern, for example, does it save only within the same session, but revert after a reboot, does it matter what model scanner, and so on.   I tried the version of Image Capture from Mavericks 10.9.5 running on 10.10.3 (yes, it works), but surprisingly, the Mavericks version which had no problem remembering settings under Mavericks, also has issues on Yosemite, which tells me there is more going on here than just the app, in fact I'm guessing it is the TWAIN drivers on Yosemite.

     

    (for lay people, TWAIN, is the standard defined for how computer operating systems should communicate with optical scanners.  In theory, if your scanner supports TWAIN and most scanners in the last ten years do, and your operating system, be it Windows, Mac, Unix whatever has TWAIN system drivers, any software that wants to can access and use the scanner.)

     

    Anyway I could not find a pattern,  to when settings were retained and not, either with the Yosemite or Mavericks version of Image Capture.  Finally my frustration reached a level where I wiped my hands clean and went and purchased VueScan.   A bit pricey for $39.99, but as the Mastercard commercial says: "Being able to use your scanner without aggravation and wanting to throw it out the windows?... Priceless."

     

    If you're fed up, do yourself a favor, get VueScan.  I was tempted to try to install the TWAIN kexts drivers from Mavericks into Yosemite, and see if that fixes the problem, but I'm happy with VueScan and don't want to risk fiddling around and messing up my system.  For you developer types out there, might be an interesting experiment

  • by professortiki,

    professortiki professortiki May 26, 2015 6:42 AM in response to RSatria
    Level 1 (5 points)
    May 26, 2015 6:42 AM in response to RSatria

    I am using the Epson scanner software and am having the same issue. No saving of settings whatsoever. Never happened before on older systems.
    Oh... and it's NOT fixed in 10.10.3!

  • by KHarringer,

    KHarringer KHarringer Jul 13, 2015 11:54 AM in response to professortiki
    Level 1 (0 points)
    Jul 13, 2015 11:54 AM in response to professortiki

    Using a Brother AIO, and it seems Image Capture never remembers the path to which I save my scans. Always "Pictures" on the host machine (wrong!). Running OS X 10.10.4, Image Capture 6.6.

     

    I noticed for the first time today that it remembered my mode, kind, and resolution from my last scanning. Possibly there's an improvement that had taken place.

  • by sachama,

    sachama sachama Jul 13, 2015 12:53 PM in response to KHarringer
    Level 1 (4 points)
    Mac OS X
    Jul 13, 2015 12:53 PM in response to KHarringer

    I confirm that 10.10.4 (installed on July 1st, but not tested until now) seems to retrieve the "memory" lost when Yosemite appeared..

  • by Zoual,

    Zoual Zoual Jan 21, 2016 7:04 AM in response to sachama
    Level 1 (0 points)
    Jan 21, 2016 7:04 AM in response to sachama

    Hi !

    I maybe have an answer to the "not retaining default settings in image capture".

     

    - From your printer / system preferences, select the scanner (or device within a multi function printer).

    - Launch the scan app from there.

    - Scan, change your settings as you want them to be as defaults

    - Close the app

     

    Next time you open "image capture", it seems that the default setting are now ... retained as you just set them.

     

    My explanation is that image capture wouldn't "write" in the imagecapturepreference.plist file, but the native printer/scan app does.

     

    Regards, and hope it will help

    Jean

  • by Ganny61,

    Ganny61 Ganny61 Sep 25, 2016 11:23 AM in response to RSatria
    Level 1 (8 points)
    Mac OS X
    Sep 25, 2016 11:23 AM in response to RSatria

    I also have this issue with El Capitan (vs. 10.11.5).  Why hasn't it been fixed?

Previous Page 2