james_nicholls_7485267's profile

3 Messages

 • 

280 Points

Sat, Oct 3, 2015 4:11 AM

Closed

Solved

Bridge: Issue using Photo Downloader on Mac OS 10.11 - El Capitan

I just upgraded to El Capitan and Adobe Bridge camera downloader can no longer detect a Canon 5D Mark III or a 5D Mark II. Apple's Photos wants to do the downloading.

14 Messages

 • 

274 Points

6 y ago

@Matt Allen — You can plug the SD card from your Canon 5D into your computer directly and still use File > Get Photos from Camera and it will import the exact same way :D (provided you have an SD port on your computer, which most Macs do or a $8 USB SD card reader):

http://www.bestbuy.com/site/camera-me...

You just can't plug a USB cable into the Camera directly (or to an iOS device) until Apple fixes the protocol issue with USB devices.

110 Messages

 • 

1.7K Points

I believe it has meanwhile been established that it's not Apple that needs to fix the protocol issue, but rather Adobe that has to edit its Photo Downloader. All other ways, both hardware and software (including Adobe's own Lightroom) work!

5 Messages

 • 

144 Points

Mac Pros don't have card readers.
Hell, doesn't even have an optical drive to burn discs.
But I'm not complaining - I still love this beast!

30 Messages

 • 

360 Points

My Macbook Pro has an SD card reader built in as does my Imac

24 Messages

 • 

392 Points

6 y ago

My 5D mk2 uses compact flash
Sometimes even using Bridge and a card reader I have to restart the Mac :before it picks it up

4 Messages

 • 

100 Points

6 y ago

Many thanks Kelly for your info re reading from card readers for Bridge import - finally able to do a normal import. Checked out Lightroom and that did see my EOS 60D and download into dng's. Good bit with the Bridge load was that it cleaned the card as well, my setting.
Overall both Apple and Adobe have failed us, Apple for not informing Adobe of protocol change, presuming they didn't and then Adobe to sit on this problem for over 4 months. Shame they are being so lacklustre over this issue - just as per!

30 Messages

 • 

360 Points

6 y ago

As I've mentioned before it appears that SD cards larger than 32Gb still fail to be recognised. Tried several cards both CF and SD up to 64Gb and only my 64Gb SD fails in a reader and the SD slot in my iMac and MacBook

110 Messages

 • 

1.7K Points

LOL (sorry, my time now, couldn't resist). Does your Mac (running the latest system version) not recognize >32GB SD-cards, or is it Adobe's Photo Downloader?
Because if it is the first, you should visit the Apple Support Communities. If it is the second, this only adds to a problem that has been going on for >4 months now.

30 Messages

 • 

360 Points

6 y ago

Photo loader I've stated it before. I can easily read the card and move the images to a folder on my hard drive. Photoloader recognises a 64Gb CF card but not a 64 Gb SD card which is why I believe it's a photoshop issue as I use the same dual slot Lexar professional card reader in the same usb 3.0 port. The Mac recognises all and reads and writes to both.

110 Messages

 • 

1.7K Points

6 y ago

Thanks for your reply, Duke. Q.E.D.: it's Adobe, not Apple that needs to make some changes (after Apple made changes, I'll admit that much).

24 Messages

 • 

392 Points

6 y ago

ive just had to restart mine because OSX kept ejecting my CF 

30 Messages

 • 

360 Points

6 y ago

So heres something I hadn't considered, if a 32Gb SD card works in a reader and the SD slot of my iMac / Macbook but the 64Gb doesn't is it still a USB issue, I don't know if the SD slot is connected to a USB bus.  iPhoto will open on both the card reader and the slot when connecting a 64Gb card.  This now makes me feel that it is Adobe's gift to fix not Apple's but what do I know......

14 Messages

 • 

242 Points

6 y ago

Yet, we are still nowhere near to getting this problem fixed. Apple have issued two updates in recent months and whilst at least one of them addressed USB issues, they have not resolved the problem with Downloader and Bridge. I think it's clear that Apple believe the problem is nor down to them to fix.

We have discussed workarounds on this bulletin board and I personally have used at least two of them and had to adjust my workflow to take them into account. However, we could really do with some feedback from Adobe as to whether they are doing something to fix the problem or whether they are just going to ignore it and leave it with their customers and users to get on with life without the problem ever being resolved. At the very least I think it is something we deserve.

24 Messages

 • 

392 Points

Id adjusted my workflow to plugging my CF into a card reader
But for some reason after a few attempts
The Mac will need restarting or the card is ejected every time
It's really disappointing

1 Message

 • 

60 Points

Ive just installed the Bridge update; I'm now on 6.2.0.170. I insert my SD card into the side of my Mac and nothing happens. I open Bridge and select Get Photos from Camera and all is good. But, I want the Photo Downloader to open automatically. And yes, I have the option ticked in Preferences. I thought this release would finally fix this issue??

1 Message

 • 

64 Points

I am using Bridge 6.2.0.179 and it will not recognize any card in a card reader, or my 5D Mark lll.

24 Messages

 • 

392 Points

Restart your Mac and try again using the card reader
I have to do it occasionally

110 Messages

 • 

1.7K Points

Is that the difference between Bridge CC and Bridge CS6? My Bridge (CS6) still is 5.0.2.4.

156 Messages

 • 

4.3K Points

6 y ago

You need to install Bridge CC 6.2 (which was released on 9th February).

Then be sure that you read the attached Release Notes too!

Link to the Release Notes:
https://helpx.adobe.com/bridge/using/whats-new.html

17 Messages

 • 

354 Points

Also read the whole thread:
https://blogs.adobe.com/creativecloud...

Lots of problems reported installing and lock ups running.

From what I read the bridge "fix" just provides a menu choice that opens Mac 10.11 Image Capture. There's no mention of fixes to the built in downloader.

156 Messages

 • 

4.3K Points

Because there is NO fix that has yet been discovered that can be made to let the old Adobe Downloader work in connection with the coding in Apple's El Cap!

So we have two choices:
Either revert to Yosemite;
 or adapt to using the Image Capture method.

9 Messages

 • 

146 Points

Or just use Finder to split up contents of 64+GB cards and put them onto 32Gb cards, which still works fine.

24 Messages

 • 

392 Points

6 y ago

Id love to downgrade the OSX I've found other bugs in El Captain too

156 Messages

 • 

4.3K Points

6 y ago

Fortunately for me, I never drank the El Cap Koolaid and I have yet to hear of a single good reason to do so.
Bridge CC 6.2 is running beautifully for me on Yosemite.

8 Messages

 • 

154 Points

El Capitan fixed a few issues I had with my MacBook Pro but it wasn't worth the trage off unfortunately.

3 Messages

 • 

280 Points

6 y ago

Hi All,

I started this thread 6 months ago and have read with interest to all the comments.  6 months is a long time. Most of us have found a workaround but I think all would like the problem fixed. Some have blamed Apple, some Adobe, and there has been one chortle that I can remember from a PC user. No one has blamed the camera companies, at least not yet.

I upgraded Bridge and Photoshop for CC yesterday. Bridge still cannot find a Canon 5D III or an iPhone. Photoshop can see an iPhone, however. Go figure!

Maybe some day but don't hold your breath.

9 Messages

 • 

146 Points

I don't see how the camera or media card companies can be blamed. All was well with Yosemite, right?

I think it's really pathetic that two leaders in the industry can't get this sorted out by now. It's like they actually don't give a <profanity removed by admin>.

30 Messages

 • 

360 Points

6 y ago

If you're going to use finder then drop all the files from a 64Gb card in to the required folder it's that easy

2 Messages

 • 

82 Points

6 y ago

It's not about workarounds, it's about Adobe and / or Apple getting this fixed.