Skip to main content
Participant
October 3, 2015
Answered

El Capitan & Adobe Photo Importer

  • October 3, 2015
  • 58 replies
  • 50616 views

The photo importer callable from Bridge no longer recognizes my cameras since I installed El Capitan.  I've disabled Apple's Phottos.app from importing.  Is there a workaround, or is it bye-bye Photo Importer for me?  I am of course NOT using CC, but PS 12.last update on a Mac Pro.

--Gene

    This topic has been closed for replies.
    Correct answer rpandita

    Image Capture does indeed work BUT it is such a pain: no ability to rename files, no auto stacking of RAW and JPEG files and no control over where the files are downloaded to on the computer.


    Hi everyone,

    Also I would request you to keep an eye on this thread - Bridge: Issue using Photo Downloader on Mac OS 10.11 - El Capitan

    We will be updating this thread when we have new information.

    Regards

    Rohit

    58 replies

    Participant
    October 26, 2015

    I created new forum post for same issue using PSE 13.x on El Capitan.

    I hope Adobe can confirm that the fix you are working on will also resolve import issue in PSE 13.x

    https://forums.adobe.com/thread/1969769?sr=inbox&ru=1413589

    Thanks!

    jotapebernal
    Participant
    October 26, 2015

    The problem for me is the name of the archive I got after importing using Apple Image Capture. I used the Organizer's Photo Downloader to rename the pictures showing the capture date and time.

    Years ago I found an app, called ExifRenamer (qdev.de - ExifRenamer) that lets me change the name after the capture. It is still working in El Capitan.

    If anyone has the same problem I hope this can help.

    Regards,

    msandman
    Participating Frequently
    October 26, 2015

    Using ExifRename is partial solution, but you can also import using Apple Image Capture and then change the names in the folder using Bridge.  Once the files are on the hard drive, Bridge will recognize them.

    Ph0t0grapher
    Participating Frequently
    October 26, 2015

    I assume Apple is trying to push everyone to use Photos to import images to the Photos Library as I note importing with other packages such as Google Picasa has also been blocked. I wonder if Adobe will be able to solve the issue.

    Visualbrother
    Known Participant
    October 26, 2015

    If that was true, nothing would work, for me all cards under 64GB work fine. And Capture One recognises 64 / 128 and 256GB cards immediately.

    Visualbrother
    Known Participant
    October 25, 2015

    Having the same problem but ONLY with 64GB / 128GB U1 / Class 10 cards, no problem with 32, 16 or 8 GB cards. SD, or Micro SD both work as long as they are smaller then 64GB.

    Tried Scandisk, Transcend, PNY and Kingston and seems to be related to the size of the disk or perhaps XDHC SDHC?

    Participant
    October 25, 2015

    Having same issues with Adobe Photo Downloader in Bridge CC (2015) after upgrading to El Capitan. Agree with Ari. Probably all of us are paying monthly subscriptions for Creative Cloud. Why should we have to use another app as a 'bridge' to Adobe's Bridge or revert to a previous OS?!?

    This issue is akin to buying a car and then having it NOT recognize your car key to start the engine... It does not matter that you may own other vehicles!

    Please fix this Adobe!!

    Ph0t0grapher
    Participating Frequently
    October 24, 2015

    Very frustrating that this is taking so long to solve. Image Capture is clunky in that it cannot name folders automatically by date. Only options are a slow workaround using Image Capture (about time it was updated!) or allowing Photos app to import photos directly into its library which many of us are reluctant to do as longstanding file structures we use are lost. Poor service both by Apple and Adobe.

    Inspiring
    October 23, 2015

    Personally, I have no intention of letting El Capitan onto my computers yet so I can't test this idea: but has anyone, who is running on El Cap., tried to disable the SIP security in El Cap.?

    I am guessing that it could be SIP which is interfering with the APDL and that it also has something to do with the requirements in El Cap for more complex crypto encoding of Creator Signatures in each part of an App.?

    There are instructions on the Web for disabling the SIP protection.

    Does some courageous soul want to risk doing this?!

    msandman
    Participating Frequently
    October 24, 2015

    Looking at the description of Apple's implementation of SIP it doesn't seem likely that this is the source of the problem.  SIP only protects files in root directories and certain libraries, as far as I can tell. 

    See: https://derflounder.wordpress.com/2015/10/01/system-integrity-protection-adding-another-layer-to-apples-security-model/

    But I'm not an OS X or Unix expert, so perhaps SIP is the problem.  Disabling it does not seem to be a trivial task, however.  I think I'll wait for a fix from Adobe (or Apple). :-)

    dazdesigner
    Participating Frequently
    October 23, 2015

    any news about fixing yet, it had been a while. I really miss bridge as it is useful working with photoshop unlike iPhoto and other software.

    Participant
    October 23, 2015

    I'm stuck with the same problems. Please find a solution now!  PLEASE !!!!!
    annoying to pay for a product that does not work

    Participating Frequently
    October 22, 2015

    22 days and counting ...nothing from Adobe. No word on status ...nothing. Getting more and more frustrated with this. Adobe busy patching Flash or...?

    Ari Ståhlman
    Participating Frequently
    October 22, 2015

    There is one thing: i´m paying for Creative Cloud. I like to have all features from it, including bridge and photo downloader. I  don´t either buy a car with only three wheels! And i´m not going back to yosemite, i simply don't´t have time for that circus.

    Magnus Lewan
    Participating Frequently
    October 22, 2015

    Even though I realise that not everyone is affected by this problem, I am disappointed in the time it has taken Adobe and Apple to release a fix. I had hoped for an emergency patch within a few hours, and I had expected a fix within one day or maximum two.

    It is now almost three weeks since this problem was highlighted, and there is still no fix in sight. In the mean time, I have been to eight countries and taken many hundreds of photos. I suspect other people have taken thousands or even tens of thousands of photos, since this bug was introduced.

    Some rebate on the subscription for affected users would be welcome. As I have one working camera and one where import does not work, I would be content with just half of what other affected people get.